Skip to main content
GET
List connectors
In v1 the only manageable provider is GitHub. Each active or previously connected installation is returned as one connector (id is its installation id). When the org has never connected GitHub, a single provider stub with status not_connected and no id is returned so callers can still discover the provider and how to connect it. More providers arrive later.

Authorization

This route requires the read 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.

Notes

  • GitHub is the only provider in v1. An organization that has never connected it gets a single provider stub with status: "not_connected" and no id, so the provider is still discoverable.

Authorizations

X-Exo-API-Key
string
header
required

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

Response

Successful Response

GET /v1/connectors: the org's connectors (one provider, GitHub, in v1).

data
Connector · object[]
required