The type of getting the JWT. Can be:

• authorization_code to exchange the code received in the authentication call to the JWT. The value of the code parameter must be specified.
• refresh_token to get the refreshed JWT when the previous value is expired. The value of the refresh_token parameter must be specified.
• client_credentials to get the server JWT. The values of the client_id and client_secret parameters must be specified.
• urn:ietf:params:oauth:grant-type:token_exchange to exchange existing user JWT with different scope.

Your application ID. The value for this parameter depends on the value of the grant_type parameter:

• If it’s authorization_code, create an OAuth 2.0 client and use its client ID.
• If it’s client_credentials, contact your Customer Success Manager to create a server OAuth 2.0 client and get its client ID.

Note that values for client_secret and client_id parameters should be used from the same client.

Value of this parameter received in the response to the last request of this call with authorization_code or refresh_token values in the grant_type parameter. Required if grant_type=refresh_token.

Your secret key. The value for this parameter depends on the value of the grant_type parameter:

• If it’s authorization_code, create an OAuth 2.0 client and use its secret key. Required if you created an OAuth 2.0 client with confidential authentication type.
• If it’s client_credentials, contact your Customer Success Manager to create a server OAuth 2.0 client and get its secret key. Required for this client type.

Note that values for client_secret and client_id parameters should be used from the same client.

Authentication code that is exchanged to a JWT. Required if grant_type=authorization_code.

The code verifier for the PKCE request, that the app originally generated before the authorization request.

List of domains for which token can be applied

A list of space-delimited, case-sensitive strings, as defined in Section 3.3 of [RFC6749], that allow the client to specify the desired scope of the requested security token in the context of the service or resource where the token will be used. The values and associated semantics of scope are service specific and expected to be described in the relevant service documentation

A security token that represents the identity of the party on behalf of whom the request is being made. Typically, the subject of this token will be the subject of the security token issued in response to the request.

A security token that represents the identity of the party on behalf of whom the request is being made. Typically, the subject of this token will be the subject of the security token issued in response to the request.

A security token that represents the identity of the acting party. Typically, this will be the party that is authorized to use the requested security token and act on behalf of the subject.