Token endpoint
The endpoint of the OpenID Provider of a sandbox organisation. It works like the endpoint of the main organisation; the path holds the ID of the sandbox organisation after the ID of the organisation.
Exchanges the authorisation code for an ID token and an access token. Your identity and access management system calls it from its server after the redirect.
Authenticate the client with HTTP Basic (client_secret_basic): the client ID as user name and the client secret as password. Send code and the same redirect_uri as in the authorisation request, and code_verifier when the request had a code_challenge.
The provider resolves the sub here, with the identity matching attributes or the callback of the client. Both tokens are ES256 JWTs that expire after 5 minutes. Check the ID token with the JWKS of the provider.
Authorizations
AuthorizationstringheaderrequiredThe client ID and secret of your client:
Basic <base64 of client-id:client-secret>.
Path parameters
organisationId stringrequiredThe ID of the organisation
sandboxOrg Id stringrequiredUnique identifier of the sandbox organisation.
Body
grant_type enum<string>requiredOnly
authorization_code.Available options:
authorization_codeDefault:
authorization_codecodestringrequiredThe authorisation code from the redirect to your redirect URI.
redirect_uri stringrequiredThe
redirect_uriof the authorisation request, exactly the same.code_verifier stringThe PKCE code verifier. Mandatory when the authorisation request had a
code_challenge.
Response
The tokens.
Headers
Cache-Control stringThe answer holds tokens. Do not cache it.
Example:
"no-store"
access_token stringA signed JWT (ES256) for the UserInfo endpoint. It holds
iss,sub,aud(the client ID),scope(openid),stateandnonce(when the authorisation request had one). It expires after 5 minutes.token_type stringAlways
Bearer.expires_in integerThe seconds until the login session ends. The session ends 15 minutes after the authorisation request; after that the UserInfo endpoint refuses the access token.
id_token stringA signed JWT (ES256) with
iss,sub,aud(the client ID),presentation(the presented claims),iat,expandnonce(when the authorisation request had one). It expires after 5 minutes. Check its signature with the JWKS of the provider.