Circuit Members API

Endpoints to operate on Members resources.

Operations 4

POST /members Create a new member #
PATCH /members/{memberId} Update a member #
DELETE /members/{memberId} Remove a member #
POST /members:import Import multiple members #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/getcircuit-com:getcircuit-com-members-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

getcircuit-com-members-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Spoke Members API
  description: 'This is the documentation of the Spoke Public API HTTP endpoints. The Spoke

    Public API is a way for you to interact with Spoke products programmatically. # Introduction


    The API has a set of HTTP methods to operate on Spoke resources for a specific

    team. Currently, Spoke offers no programming SDKs for interacting with the Public

    API, but you can implement your own interface by calling the methods documented

    on this page. # v1 Migration Guide


    If migrating from version 0.2b to v1, please note the following changes. ### General


    1. Only `api.spoke.com` should be used for the `v1` API. 2. Webhooks requests will now only contain the `spoke-signature` header. ### Stops


    Removals:


    | Operation | 0.2b Property | v1 Property | Notes |

    | ---------- | ------------------------------- | -------------------------------- | ---------------------------------------------------------------------------- |

    | WRITE | `stop.driver` | `stop.allowedDrivers` | Drivers should now be provided as an array of `DriverIds`. |

    | READ | `stop.driverIdentifier` | `stop.allowedDrivers` | Drivers will now be returned as an array of `DriverIds`. |

    | READ | `stop.allowedDriverIdentifiers` | `stop.allowedDrivers` | Drivers will now be returned as an array of `DriverIds`. |

    | READ | `stop.etaNullReason` | `stop.eta.status` | `eta` now has a status property with the same information. |

    | READ | `stop.timeAtStopInfoNullReason` | `stop.timeAtStopInfo.status` | `timeAtStopInfo` now has a status property with the same information. |

    | READ/WRITE | `stop.circuitClientId` | `stop.clientId` | When creating or reading stops, `circuitClientId` will now be `clientId` |

    | READ | `stop.deliveryInfo.arrivedAt` | `timeAtStopInfo.value.arrivedAt` | This property is only available when `timeAtStopInfo.status === ''available''` |


    Changes:


    1. READ: `stop.eta` is now an object containing both the eta value, and additional metadata about the value. 2. READ: `stop.timeAtStopInfo` structure has changed so that the original properties are now under `timeAtStopInfo.value.*`,

    and an additional field `timeAtStopInfo.status` has been added to indicate why the info is not set. ### Plans


    Changes:


    1. Previously we would allow `Drivers` to be added even if their `Depot` did not match the plan''s `Depot`. This is no longer allowed. Non-matching `Drivers` must now have their `Depot` changed to match the target `Plan`,

    or vice versa. 2. `Driver` objects are no longer returned as part of `Plan` endpoint responses. Instead, `DriverIds` are returned and

    the associated drivers must be fetched separately (if needed). # Using the API


    This section describes how the Spoke API should be used, if you wish to see

    example implementations take a look at the API Usage

    Examples page. ## Address


    The base API address for this version of the API to be used before every

    endpoint listed here is: `https://api.spoke.com/public/v1`


    Notice the `https://` prefix, Spoke API will **not** accept plain HTTP

    requests. ## Authentication


    To use Spoke Public API endpoints you will first need to generate an API key

    for authenticating with our servers. To do this you need to go to your Spoke Dispatch settings page > Integrations

    \> API, and generate a new key there. Once you have the API key you can use it in the `Authorization` header

    either using the Basic scheme, or as a Bearer token. ### Basic Auth


    Basic Authentication is the primary authentication scheme used

    by Spoke''s API. Basic authentication typically uses a base64 encoded `username:password`

    pair, but since we only require an API key we instead structure the payload as `[yourApiKey]:[empty]`. This

    value is then base64 encoded as usual. Example with `curl`:


    ```bash

    curl "https://api.spoke.com/public/v1/plans" -u yourApiKey:

    ```


    If you did everything correctly you should see a list of your team''s plans in response

    to this request.'
  version: v1
servers:
- url: https://api.spoke.com/public/v1
security:
- BasicAuth: []
tags:


# --- truncated at 32 KB (35 KB total) ---
# Full source: https://artifacts.apis.io/getcircuit-com/openapi/getcircuit-com-members-api-openapi.yml