Complete a connected account request
Complete a previously started authorization flow to link the authenticated user’s account with an external identity provider.
Authorizations
Bearer and DPoP tokens are supported depending on the API configuration
Headers
A client-provided unique identifier for a single operation, used to correlate the request across Auth0 systems. The value is surfaced under references.correlation_id in tenant logs and echoed back on the response's x-correlation-id header. Invalid or oversized values are silently dropped and replaced by a generated UUID v4. Avoid including personally identifiable information (PII).
A W3C Trace Context header used to correlate the request across distributed traces. When supplied, the inbound trace is continued and a fresh child span is echoed back on the response's traceparent header; the trace ID is also surfaced under references.trace_id in tenant logs. Malformed values are ignored.
Specifies the language used for localized content generated while handling the request (such as OTP email or SMS messages), using one of the tenant's configured Supported Languages.
Body
The authentication session identifier
64The authorization code returned from the connect flow
1 - 46The redirect URI used in the original request
2048The PKCE code verifier
43 - 128Response
Connected account request completed successfully
The unique identifier of the connected account
The connection name
The access type, always 'offline'
offline ISO date string of when the connected account was created
Array of scopes granted
ISO date string of when the refresh token expires (optional)