SAsazabi
Integrations

Get a connect attempt

Changed on

Poll a browser connect attempt started with integrations.beginConnect. Visible only to the user who began it.

get/integrations/connect/attempts/{attemptId}

Request

Path parameters

attemptIdstring uuid required

Connect attempt ID to poll.

Query parameters

organizationIdstring

Organization the attempt belongs to. Auto-filled from CLI and SDK context when omitted. User tokens must supply it unless the credential's fixed scope resolves it; secret keys may omit it (the key's organization applies).

Response

OK

status'pending' | 'completed' | 'not_connected' | 'failed' | 'expired' required

Attempt state. not_connected means the flow finished but the connection is not live yet (most commonly awaiting a third-party admin's approval). expired means the browser flow did not complete in time — begin a new connect.

conflictPendingboolean

True while a connection-conflict decision is awaiting the user in the browser (the attempt stays pending — and its expiry extends — until they choose). Mirrors the connected-account attempt's field.

errorCodestring nullable required

Reason code when status is failed (the shared OAuth callback vocabulary, e.g. vendor_denied, not_authorized) or not_connected (e.g. installation_requested for GitHub installs awaiting org-admin approval).

Changes

  • e7741f78d15aRevision changes
    • warning

      added the new tembo enum value to the / response property for the response status

  • 33821f7c6f4aRevision changes
    • warning

      added the new discord_bot enum value to the / response property for the response status