Authentication
Last updated
Last updated
For certain cases we support a server to server authentication process. This will allow a tenant to receive an access token that can be used for accessing our APIs. This access token is not tied to any particular user and must be used for appropriate use cases. The access token must be stored securely and never exposed outside of your system except to call our APIs.
Note - this endpoint conforms to . Please be aware that the body is sent form encoded with the content type application/x-www-form-urlencoded
.
Please note our server to server authentication environment is different than our SSO one. See Environments for more details.
/v1/oauth2/token
For the token exchange you will send the following fields.
grant_type
client_credentials
scope
A space-delimited list of permissions that the application requires.
client_id
The same client_id
value you sent in to the authorization step.
client_secret
This is your client secret that was generated when the client was configured.
access_token
This token can be used to call any of our APIs that you have the right permissions and scopes to call.
expires_in
The number of seconds the access token is good for.
token_type
Bearer
Token Endpoint as described in https://openid.net/specs/openid-connect-core-1_0.html#TokenEndpoint. A user access token can be passed as a scope to associate the account to create user specific, 'client_credentials', server tokens as described in https://datatracker.ietf.org/doc/html/rfc6749#section-4.4.
Your OAuth2 client id
Your OAuth2 client secret
The OAuth code used for retrieving a bearer token
Grant type
Any session ids you want us to persist on the session
Any session ids you want us to persist on the session
The OAuth2 redirect URI
The OAuth refresh token.
A space separated list of scopes. To extend a user token for a token with broader scopes the original access token should be before the scope list followed by a space.
The JWT assertion to exchange for an access token when grant_type is jwt_bearer.