Connect an account
Connects the account, either outright or by returning a URL to authorise in a browser — connected says which happened. API-key apps are connected in this one call; OAuth apps need the round trip. A 400 with code INTEGRATION_SETUP_REQUIRED names the fields still missing (see GET /integrations/:app/auth). Once connected, call POST /integrations/:app/servers to build the tool server.
Authorizations
Use JWT token for authentication
Path Parameters
App slug
Body
Which scheme to connect through, from GET /integrations/:app/auth. Defaults to the one asking for least setup
"API_KEY"
Credentials of your own application with the provider, keyed by the scheme's appFields. Needed once per workspace for apps the integration provider holds no credentials for; ignored afterwards
What this account supplies, keyed by the scheme's accountFields — an API key, the subdomain of your instance