Connectors

Get connector

One connector entry; 404 distinguishes an unknown id from a disconnected one.

GEThttps://api.corespeed.io/connectors/:id

Returns the same entry shape as the index, for one connector.

Authorizationstringheaderrequired

Bearer <sk-cs-…> — a CoreSpeed API key, or a user session JWT. x-api-key: <sk-cs-…> is accepted in its place.

idstringpathrequired

Any connector id present in the authenticated index.

A 404 means the id does not exist. A connector that exists but has no connected account returns 200 with status: "disconnected" and an empty accounts array — the distinction matters when you are deciding whether to send a user to the dashboard or to fix a typo.

A connector withheld from the index (upstream approval still in progress) keeps its own route, so this endpoint can answer 200 for an id the index never listed. The index is the availability authority; this route is not.

Connector-route business errors use a flat envelope ({ "error": "<code>", "message": "…" }), unlike the nested { "error": { type, message, code } } envelope that identity, billing, and unknown-endpoint failures use. Handle both shapes when you parse errors from this surface.

curl https://api.corespeed.io/connectors/notion \
  -H "Authorization: Bearer $CORESPEED_API_KEY"
Exists but not connected
{
  "id": "linear",
  "category": "connector",
  "name": "Linear",
  "mcp_url": "https://api.corespeed.io/mcp",
  "status": "disconnected",
  "accounts": []
}