Skip to main content
DELETE
Disconnect a connector
For GitHub this marks the installation disconnected (a tombstone status, not a physical delete); repositories stop syncing. Org-scoped and idempotent: a connector this org does not own returns 404, and a second disconnect of an owned connector still succeeds. Reconnect by beginning the connect flow again.

Authorization

This route requires the write scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

connector
integer
required

The connector id (a GitHub installation id) returned by GET /v1/connectors.

Response

Successful Response

DELETE /v1/connectors/{id}: the disconnected connector.

id
string
required
provider
string
required
revoked
boolean
required
status
string
required