Circuit Plans API
Endpoints to operate on [Plans](/docs/models/plan) resources.
OpenAPI Specification
openapi: 3.1.0
info:
title: Spoke Depots Plans API
description: "This is the documentation of the Spoke Public API HTTP endpoints. The Spoke\nPublic API is a way for you to interact with Spoke products programmatically.\n\n# Introduction\n\nThe API has a set of HTTP methods to operate on Spoke resources for a specific\nteam.\n\nCurrently, Spoke offers no programming SDKs for interacting with the Public\nAPI, but you can implement your own interface by calling the methods documented\non this page.\n\n# Using the API\n\nThis section describes how the Spoke API should be used, if you wish to see\nexample implementations take a look at the [API Usage\nExamples](/docs/api-examples) page.\n\n## Address\n\nThe base API address for this version of the API to be used before every\nendpoint listed here is: `https://api.spoke.com/public/v0.2b`\n\nNotice the `https://` prefix, Spoke API will **not** accept plain HTTP\nrequests.\n\n## Authentication\n\nTo use Spoke Public API endpoints you will first need to generate an API key\nfor authenticating with our servers.\n\nTo do this you need to go to your Spoke Dispatch settings page > Integrations\n\\> API, and generate a new key there.\n\nOnce you have the API key you can use it in the `Authorization` header\neither using the Basic scheme, or as a Bearer token.\n\n### Basic Auth\n\n[Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is the primary authentication scheme used\nby Spoke's API.\n\nBasic authentication typically uses a base64 encoded `username:password`\npair, but since we only require an API key we instead structure the payload as `[yourApiKey]:[empty]`. This\nvalue is then base64 encoded as usual.\n\nExample with `curl`:\n\n```bash\ncurl \"https://api.spoke.com/public/v0.2b/plans\" -u yourApiKey:\n```\n\nIf you did everything correctly you should see a list of your team's plans in response\nto this request.\n\nThe `-u` flag adds a header to the request in the following format:\n\n```http\nAuthorization: Basic eW91ckFwaUtleToK\n```\n\nNote that curl automatically base64 encoded the data. Other clients will do the same e.g. if using Postman you would\nconfigure the request's Authorization option instead of adding a header directly.\n\n### Bearer Token\n\nAlternatively you can pass the API key as a Bearer token without any special encoding.\ni.e. `Authorization: Bearer [yourApiKey]`.\n\nExample with `curl`:\n\n```bash\ncurl \"https://api.spoke.com/public/v0.2b/plans\" -H \"Authorization: Bearer yourApiKey\"\n```\n\n## On resource types\n\nEvery response from the Spoke Public API will be as JSON Objects, and every\nrequest that has a body also needs to be in that type, and the header\n`Content-type: application/json` needs to present, so the server knows that the\nbody you are sending is valid JSON. Spoke will reject requests without that\nheader, so be sure to use it.\n\n## On resource IDs\n\nEvery resource in the Spoke Public API has a unique ID. This ID is generated\nby Spoke and is unique for every resource per collection.\n\nEvery resource representation returned by the API will show the ID in the\nfollowing format:\n\n```json\n{\n \"id\": \"collectionName/resourceId\"\n}\n```\n\nAnd if the resource is on a sub-collection, it will be in the following format:\n\n```json\n{\n \"id\": \"collectionName/resourceId/subcollectionName/subResourceId\"\n}\n```\n\nFor example, a stop with ID `stop1` under a plan with ID `plan1` will have the\nfollowing representation on its serialized ID field:\n\n```json\n{\n \"id\": \"plans/plan1/stops/stop1\"\n}\n```\n\nThis means that if you wish to directly retrieve this stop by using a GET\nendpoint you can simply use this ID as follows:\n\n```bash\ncurl \"https://api.spoke.com/public/v0.2b/`serializedId`\" -u yourApiKey:\n```\n\nFor the example above this would be:\n\n```bash\ncurl \"https://api.spoke.com/public/v0.2b/plans/plan1/stops/stop1\" -u yourApiKey:\n```\n\n## On List endpoints\n\nWhen using list endpoints, you have the ability to combine various query options\nto locate the desired results. Some endpoints even offer specific filter options\nto aid in this search.\n\nAll the list endpoints employ pagination. This means that a single request might\nonly return a part of the entire set of resources you're aiming to retrieve. To\nmove through the subsequent pages, the Spoke API provides a `nextPageToken`\nfield in the response of every list endpoint query.\n\nIt's crucial to understand that when a `nextPageToken` is returned, it indicates\nthat more data is available. For every subsequent request, this token should be\nadded as the `pageToken` query parameter. And, importantly, **all the original\nquery parameters** used in the first request must also be included.\n\nHere's a step-by-step example to elucidate this:\n\n1. Suppose you initiate a request to list your plans:\n\n```bash\ncurl \"https://api.spoke.com/public/v0.2b/plans?filter.startsGte=2023-05-01\" -u yourApiKey:\n```\n\n2. The Spoke API might return a response like:\n\n```json\n{\n // other attributes\n \"nextPageToken\": \"I53Jr5Eu2qK9omh0iA8q\"\n}\n```\n\n3. To retrieve the next page of data, use the returned `nextPageToken` as the\n `pageToken` query parameter, and ensure all initial query parameters remain\n the same:\n\n```bash\ncurl \"https://api.spoke.com/public/v0.2b/plans?filter.startsGte=2023-05-01&pageToken=I53Jr5Eu2qK9omh0iA8q\" -u yourApiKey:\n```\n\n4. Repeat step 3 for all subsequent pages, updating the `pageToken` parameter\n with the latest `nextPageToken` value returned until `nextPageToken` is\n `null` in the response.\n\nSpoke also accepts limiting the maximum number of results per page by using\nthe `maxPageSize` query parameter, but notice that each individual endpoint has\na maximum value you can set this to.\n\n## On Update endpoints (HTTP PATCH verb)\n\nUpdate methods differ from the other methods in the API in the sense that\nmissing values in the JSON representation will **not** act upon the\nrepresentation of the resource.\n\nExplaining this by example: Suppose you have a Plan with the ID `plan1` in your\nplans' collection, and you wanted to merely update its title to `My API Plan`\nwithout changing other information, such as assigned drivers or the start date.\nTo do this you would issue the following request:\n\n```bash\ncurl -X PATCH http://localhost:5005/public/v0.2b/plans/plan1 -H 'Content-type: application/json' -d '{\"title\": \"My API Plan\"}' -u yourApiKey:\n```\n\nNotice how we don't pass any other information in the JSON, only the title. This\nensures that the `PATCH` request will only operate on the provided parameters\nand keep the other parameters as-is.\n\nIt is important to also notice that when updating an array the whole array will\nbe replaced, Spoke API does not support partial updates on arrays.\n\n## On Rate-Limiting\n\nAll the endpoints in the Spoke Public API are rate-limited, which means we\nwill reject requests that come in too fast.\n\nTo know if your request was rate-limited, check if the response has the HTTP\nstatus code 429.\n\nEach endpoint has a different rate limit, and Spoke can change this rate\nlimit at any moment.\n\nThe rate limits are as follows:\n\n- **Rate Limits for Write Endpoints**: All write endpoints have a limit of 5\n requests per second, which includes Creation (POST), Update (PATCH), and\n Deletion (DELETE) operations for all models.\n - An exception to this rule is the Driver Creation endpoint, which is limited to\n 1 request per second. Thus, we recommend using the Batch Import Drivers\n when adding multiple drivers.\n- **Rate Limits for Read Endpoints**: All read endpoints, including list\n endpoints, are limited to 10 requests per second.\n- **Rate Limits for Batch Import**:\n - The _Batch Import_ endpoints for Stops and Unassigned Stops models are\n limited to 100 requests per _10 minutes_ (with a maximum rate of 30 per _minute_).\n However, these endpoints can handle the import of up to 1,000 stops per minute.\n The Creation, Update, and Deletion endpoints for these models still maintain\n a rate limit of 5 requests per second.\n - The _Batch Import_ endpoint for Drivers is limited to 2 requests per\n _minute_. This allows for the import of up to 100 drivers per minute.\n- **Rate Limits for Optimization Endpoints**: The Plan _optimization_ and\n _re-optimization_ endpoints are limited to 100 requests per _10 minutes_\n (with a maximum rate of 30 per _minute_), due to the long running nature of these operations.\n\nSpoke API will occasionally support bursts of requests, but they cannot be\nsustained and will be rejected if they last too long.\n\nIf Spoke rejects your request because it exceeds the rate limit, you must\nwait before retrying it. We suggest you use an [exponential\nbackoff](https://en.wikipedia.org/wiki/Exponential_backoff) approach for this.\n\nWe also recommend, besides the exponential backoff algorithm, that you add a\nrandom delay to each attempt to prevent a [thundering herd\nproblem](https://en.wikipedia.org/wiki/Thundering_herd_problem).\n\nIf the client keeps retrying rate-limited requests while being rejected with a\n429 at a high rate, Spoke will keep rejecting the requests until you turn\ndown the request rate.\n\nSpoke will also limit requests if it keeps receiving them at a high frequency\nat or close to the requests limit for an extended period, so while we support\nan occasional burst of requests, if this is sustained for a long period, we\nwill rate-limit the client making them.\n\nWhile we feel these rate-limits will work for the vast majority of use cases we\nunderstand every team is different. So please reach out to us and describe your\nuse case if these limits are not enough for you, and we will evaluate\nincreasing them for your team.\n\n## On the models\n\nAfter this section you will find all the Spoke Public API endpoints available.\n\nEvery representation of resources that these endpoints create and return are\ndocumented in the [Models](/docs/category/models) page of the docs.\n"
version: v0.2b
servers:
- url: https://api.spoke.com/public/v0.2b
security:
- BasicAuth: []
tags:
- name: Plans
description: 'Endpoints to operate on [Plans](/docs/models/plan) resources.
'
paths:
/plans:
post:
operationId: createPlan
summary: Create a new plan
tags:
- Plans
requestBody:
content:
application/json:
schema:
description: The request body for creating a plan.
type: object
properties:
title:
type: string
minLength: 1
maxLength: 255
starts:
description: The date the plan starts. Does not accept dates that are too far in the future or past.
type: object
properties:
day:
description: The day of the date.
type: integer
minimum: 1
maximum: 31
month:
description: The month of the date.
type: integer
minimum: 1
maximum: 12
year:
description: The year of the date.
type: integer
minimum: -9007199254740991
maximum: 9007199254740991
required:
- day
- month
- year
additionalProperties: false
drivers:
default: []
description: The drivers IDs of the plan, in the format `drivers/<id>`, duplicates will be ignored
maxItems: 50
type: array
items:
description: The driver id, in the format `drivers/<id>`
type: string
pattern: ^drivers\/[a-zA-Z0-9---_]{1,50}$
depot:
description: The depot id, in the format `depots/<id>`. If not provided, the team's Main Depot will be used.
anyOf:
- type: string
pattern: ^depots\/[a-zA-Z0-9---_]{1,50}$
- type: 'null'
required:
- title
- starts
additionalProperties: false
required: true
description: The request body for creating a plan.
responses:
'200':
description: The created plan
content:
application/json:
schema:
$ref: '#/components/schemas/planSchema'
description: The created plan
'400':
description: The request is invalid, or a driver is not active.
content:
application/json:
schema:
oneOf:
- type: object
properties:
message:
type: string
description: The error message.
code:
type: string
description: The error code.
param:
type: string
description: The parameter that caused the error.
url:
type: string
description: The URL with more information about the error.
required:
- message
description: Failed to validate the request
- type: object
properties:
message:
type: string
enum:
- Driver is not active
code:
type: string
enum:
- driver_not_active
param:
type: string
description: The parameter that caused the error.
required:
- message
- code
description: The driver is not active
title: Driver is not active
description: The request is invalid, or a driver is not active.
'401':
description: Unauthorized
content:
application/json:
schema:
type: object
properties:
message:
type: string
description: The error message.
url:
type: string
description: The URL with more information about the error.
required:
- message
description: Unauthorized
'403':
description: Plan is no longer accessible due to data access restrictions. Upgrade to a plan that supports a longer delivery history period to access it.
content:
application/json:
schema:
type: object
properties:
message:
type: string
enum:
- Plan is no longer accessible due to data access restrictions. Upgrade to a plan that supports a longer delivery history period to access it.
code:
type: string
enum:
- plan_inaccessible
url:
type: string
enum:
- https://dispatch.spoke.com/paywall
required:
- message
- code
- url
description: Plan is no longer accessible due to data access restrictions. Upgrade to a plan that supports a longer delivery history period to access it.
'404':
description: The depot or driver could not be found.
content:
application/json:
schema:
oneOf:
- type: object
properties:
message:
type: string
enum:
- Depot not found
required:
- message
description: The provided depot id does not exist
title: Depot not found
- type: object
properties:
message:
anyOf:
- type: string
enum:
- Driver not found
- type: string
required:
- message
description: The provided driver id does not exist
title: Driver not found
description: The depot or driver could not be found.
'409':
description: Depot not found
content:
application/json:
schema:
type: object
properties:
message:
type: string
enum:
- Depot not found
code:
type: string
enum:
- depot_not_found
required:
- message
- code
description: Depot not found
title: Depot not found
'500':
description: An internal server error occurred
content:
application/json:
schema:
type: object
properties:
message:
type: string
description: The error message.
code:
type: string
description: The error code.
param:
type: string
description: The parameter that caused the error.
url:
type: string
description: The URL with more information about the error.
required:
- message
description: An internal server error occurred
default:
description: The default error model
content:
application/json:
schema:
type: object
properties:
message:
type: string
description: The error message.
code:
type: string
description: The error code.
param:
type: string
description: The parameter that caused the error.
url:
type: string
description: The URL with more information about the error.
required:
- message
description: The default error model
get:
operationId: listPlans
summary: List plans
tags:
- Plans
parameters:
- schema:
type: string
minLength: 1
maxLength: 255
in: query
name: pageToken
required: false
description: The page token, if any.
- schema:
default: 10
type: number
minimum: 1
maximum: 20
in: query
name: maxPageSize
required: false
description: The max page size.
- schema:
type: object
properties:
title:
description: Filter by title, exact match
type: string
minLength: 1
maxLength: 255
startsGte:
description: Search for plans that start after this date, inclusive. The date must be in the format YYYY-MM-DD.
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$
startsLte:
description: Search for plans that start before this date,inclusive. The date must be in the format YYYY-MM-DD.
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$
additionalProperties: false
in: query
name: filter
required: false
description: 'The filter to apply to the list of plans. The filter params are passed like this: `?filter[title]=foo` or like this: `?filter.title=foo`'
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
plans:
type: array
items:
$ref: '#/components/schemas/planSchema'
description: The plans list.
nextPageToken:
anyOf:
- type: string
- type: 'null'
description: The next page token.
required:
- plans
- nextPageToken
definitions:
planSchema:
type: object
properties:
id:
type: string
pattern: ^plans\/[a-zA-Z0-9---_]{1,50}$
description: The unique identifier of the plan.
title:
type: string
description: The title of the plan.
starts:
type: object
properties:
day:
type: integer
minimum: 1
maximum: 31
description: The day of the date.
month:
type: integer
minimum: 1
maximum: 12
description: The month of the date.
year:
type: integer
minimum: -9007199254740991
maximum: 9007199254740991
description: The year of the date.
required:
- day
- month
- year
additionalProperties: false
description: A date.
depot:
anyOf:
- type: string
pattern: ^depots\/[a-zA-Z0-9---_]{1,50}$
- type: 'null'
description: The depot ID of the plan, in the format depots/<id>
distributed:
type: boolean
description: Whether the plan has been distributed.
writable:
type: boolean
description: Whether the plan is writable using the normal Plan APIs. If this is false, you will need to use the [Live Plan APIs](/api/v0.2b#tag/Live-Plans) to edit the plan. Any plan created before 2023-04-01 is not writable.
optimization:
anyOf:
- type: string
enum:
- creating
- editing
- preview
- optimized
- optimizing
- type: 'null'
description: The optimization state of the plan.
drivers:
type: array
items:
type: object
properties:
id:
type: string
pattern: ^drivers\/[a-zA-Z0-9---_]{1,50}$
description: The driver id, in the format `drivers/<id>`
name:
anyOf:
- type: string
- type: 'null'
description: The name of the driver.
email:
anyOf:
- type: string
- type: 'null'
description: The email of the driver.
phone:
anyOf:
- type: string
- type: 'null'
description: The phone number of the driver.
displayName:
anyOf:
- type: string
- type: 'null'
description: The display name of the driver.
active:
type: boolean
description: Whether the driver membership is active or paused. Paused drivers will not be assigned to any routes.
depots:
type: array
items:
type: string
pattern: ^depots\/[a-zA-Z0-9---_]{1,50}$
description: Depots associated with the driver.
routeOverrides:
type: object
properties:
startTime:
anyOf:
- type: object
properties:
hour:
type: integer
minimum: -9007199254740991
maximum: 9007199254740991
description: Hour of the day
minute:
type: integer
minimum: -9007199254740991
maximum: 9007199254740991
description: Minute of the hour
required:
- hour
- minute
additionalProperties: false
description: Time of day in hours and minutes. Uses a 24 hour clock.
- type: 'null'
description: Driver's start time.
endTime:
anyOf:
- type: object
properties:
hour:
type: integer
minimum: -9007199254740991
maximum: 9007199254740991
description: Hour of the day
minute:
type: integer
minimum: -9007199254740991
maximum: 9007199254740991
description: Minute of the hour
required:
- hour
- minute
additionalProperties: false
description: Time of day in hours and minutes. Uses a 24 hour clock.
- type: 'null'
description: Driver's end time.
startAddress:
anyOf:
- type: object
properties:
address:
type: string
description: The address of the stop.
addressLineOne:
type: string
description: The first line of the address.
addressLineTwo:
type: string
description: The second line of the address.
latitude:
anyOf:
- type: number
minimum: -90
maximum: 90
- type: 'null'
description: The latitude of the address in decimal degrees.
longitude:
anyOf:
- type: number
minimum: -180
maximum: 180
- type: 'null'
description: The longitude of the address in decimal degrees.
placeId:
anyOf:
- type: string
- type: 'null'
description: The identifier of the place corresponding to this stop on Google Places
placeTypes:
type: array
items:
type: string
description: Array of strings that is provided by the Google AutoCompleteAPI
required:
- address
- addressLineOne
- addressLineTwo
- latitude
- longitude
- placeId
- placeTypes
additionalProperties: false
description: The address of the stop.
- type: 'null'
description: Driver's start location.
endAddress:
anyOf:
- type: object
properties:
address:
type: string
description: The address of the stop.
addressLineOne:
type: string
description: The first line of the address.
addressLineTwo:
type: string
description: The second line of the address.
latitude:
anyOf:
- type: number
minimum: -90
maximum: 90
- type: 'null'
description: The latitude of the address in decimal degrees.
longitude:
anyOf:
- type: number
minimum: -180
maximum: 180
# --- truncated at 32 KB (166 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/circuit/refs/heads/main/openapi/circuit-plans-api-openapi.yml