Exchange OIDC authorization code
Exchanges an OpenID Connect authorization-code response for an Extole access token. Pair the body’s code and state with the X-CSRF-TOKEN and X-NONCE headers - all four are required by the OIDC validator. Marked as expert: most integrators authenticate via POST /v4/tokens instead.
Authorizations
Body
Body of POST /v4/tokens/openid-connect/authorization-code-flow. Pair with the X-CSRF-TOKEN and X-NONCE headers minted alongside the authorization-code response.
Authorization code received from the OpenID Connect provider. Validated alongside the X-CSRF-TOKEN and X-NONCE headers; missing or expired codes return 403 authorization_code_response_invalid.
Opaque state value the relying party round-tripped through the authorization-code flow. Must match the value the relying party generated when starting the flow; mismatches return 403 authorization_code_missing_state.
Response
Successful response
Access-token metadata returned by POST /v4/tokens, POST /v4/tokens/openid-connect/authorization-code-flow, GET /v4/tokens, GET /v4/tokens/{token}, and PUT /v4/tokens/exchange/{token}. Pass access_token in the Authorization header (Bearer ...) on subsequent requests.
Token string. Send as Authorization: Bearer <access_token> on subsequent requests, or as the access_token query parameter / extole_token cookie.
Stable Extole identifier for the client (tenant) this token authenticates against.
Seconds until this token expires. Once expired, requests using it return 401 invalid_access_token; rotate via PUT /v4/tokens/exchange/{token} before expiry to keep long-lived integrations alive.
Stable Extole identifier for the identity (user, managed identity, or resource) that this token represents.
Deprecated alias for identity_id. New integrations should use identity_id.
Authorization scopes granted to this token. Determines which API operations the token may invoke.
Authorization scopes granted to this token. Determines which API operations the token may invoke.
BACKEND, CLIENT_ADMIN, CLIENT_REPORT_DOWNLOAD, CLIENT_SUPERUSER, ONE_TIME, PASSWORD_RESET, UPDATE_PROFILE, USER_SUPPORT, VERIFIED_CONSUMER Authentication shape backing the token. USER represents a human dashboard user, MANAGED an OAuth-style managed identity, and RESOURCE a scoped per-resource token.
MANAGED, RESOURCE, USER 