Finish connecting provider accounts after the authorization redirect
Finishes an authorization begun by managedAgentsStartIntegrationInstall. It returns either connected accounts or provider-neutral account/action options that continue through managedAgentsStartIntegrationInstall. The provider and organization come from the authenticated caller and single-use state nonce, never from callback parameters or browser-local storage. An expected provider failure after state consumption returns 409 integration_install_restart_required with details.provider; begin a new install. Resource and permission selection happens later when granting a vault. Do not automatically retry an ambiguous transport failure: list connections to determine whether completion committed; if it did not, begin a new install because the state is single-use.
Authorizations
A Recursion API key, created in the console under API keys.
Headers
Optional tenant consistency check. When present, it must name the tenant bound to the API key, including when x-organization-id is default.
1Organization in which to act. Required for a tenant-scoped API key. Optional for an organization-scoped key, where it must name that same organization. The value may be an organization id or default.
1Body
Request body completing integration authorization after the provider redirects the user back. Sent from an authenticated session so the provider and organization come from the single-use state record rather than from callback parameters or browser-local storage.
The nonce returned when authorization was started. Single-use and short-lived.
Provider authorization code, proving which user authorized this connection. Required by OAuth providers (GitHub, Jira, Confluence, Loom), which refuse a completion without one. A built-in integration's sign-in page also returns a single-use code, verified before the connection activates, so a completion without it fails.
Which account the operator chose on the provider's own page, in the opaque form that provider returned. Providers with an account chooser may require it; GitHub returns an installation id. A selector only: the server verifies the choice against the accounts the authorizing user can reach and refuses one they cannot.
Response
The completed integration authorization. Connections contains the accounts established by this callback; when the provider needs the operator to choose an account or action first, connections is empty and options contains those provider-defined continuations.
The completed integration authorization. Connections contains the accounts established by this callback; when the provider needs the operator to choose an account or action first, connections is empty and options contains those provider-defined continuations.