Connectors

Disconnect account

Disconnect your own private account on an OAuth connector. Remote MCP deregistration lives on its own path.

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

Removes the caller's own unambiguous private account on an OAuth connector: the upstream grant is revoked best-effort, then the stored credential is deleted regardless of the revoke outcome.

This path no longer doubles as remote-MCP deregistration. An org-registered remote MCP connector is deleted with DELETE /connectors/org/:slug (admin-only, 403 admin_required otherwise) — whole-sale: the registration, its snapshots, its stored credentials, and the KV hot copies all go, with no undo. The split means a remote slug can never collide with a connector id on this route again.

Authorizationstringheaderrequired

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

idstringpathrequired

An OAuth connector id, whose private account is removed.

  • 204 — removed, or a no-op because only a shared credential exists. This route never deletes a shared account.
  • 409 — more than one account matches, so the target is ambiguous. Address one account directly instead.
  • 404 — unknown connector id. Unknown ids never reveal anything, credentialed or not.

Shared accounts are removed over HTTP only through DELETE /connectors/:id/accounts/:accountId, which returns 204 and enforces the same per-scope authorization: private → owning member only; shared → creator or organization admin. The manage__accounts_remove MCP tool performs the same removal addressed by alias.

Authorizing a connector is not an HTTP operation — the OAuth dance runs in the dashboard over an internal binding, so there is no public route to initiate a connect.

curl -X DELETE https://api.corespeed.io/connectors/notion \
  -H "Authorization: Bearer $CORESPEED_API_KEY" \
  -i
Removed, or a no-op on a shared credential

No body.