Skip to main content
These events tell your app when access changes. Each event identifies the user’s approval with authorizationId and the linked account with linkedAccountId. When a change affects the whole authorization, linkedAccountId is null. See Webhooks for the full event fields and signature checks. Use authorization.* events when access changes for the accounts in one authorization. Use linked_account.* events to pause, resume, or stop work for one account. If an account expires, ask the user to reconnect it. If an authorization is revoked, ask the user to approve your app again.

Lifecycle events

One action sends one event. Changes to the whole authorization are authorization.*. Changes to one account are linked_account.*, sent to every authorization that includes that account. authorization.revoked reasons: linked_account.disconnected reasons:

Payloads

Event data contains IDs only. Get names, status, and scopes from GET /v3/linked-accounts.
An event lists up to 100 account IDs. If there are more, it replaces the ID lists with linked_account_ids_truncated: true and linked_account_count. If access is still active, it also includes linked_accounts_url: "/v3/linked-accounts". Get the full list with that authorization’s access token. A revoked authorization cannot read the list, so authorization.revoked events omit linked_accounts_url.
Individual credential refresh, expiry, or revocation does not end durable consent and does not send authorization.revoked. Each destination can enable lifecycle deliveries with lifecycleEventsEnabled; lifecycle deliveries are not billed.