Begin a connector connect flow
Connectors
Begin a connector connect flow
Begin connecting a provider and return the URL to send the user to.
POST
Begin a connector connect flow
For GitHub this returns the App install URL carrying a signed, short-lived
state token that binds the install back to the authenticated caller. The
caller redirects the user there; GitHub completes the install with a
callback to a route this contract does not publish, since it is invoked by
GitHub’s own installation flow rather than by your client. An unsupported
provider is rejected with 422, naming the supported providers.
Authorization
This route requires thewrite 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
- This returns a URL to send the user to. The install is finalized by the provider’s callback, not by this call.
Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Path Parameters
The connector provider to connect. Supported in v1: github.