Request

Once you have obtained credentials from the customer or Elite, use the credentials as shown in the following POST request to the authentication endpoint to test if access tokens are generated successfully:

curl --location 'https://login.microsoftonline.com/<tenant_id>/oauth2/v2.0/token' \

--header 'Content-Type: application/x-www-form-urlencoded' \

--data-urlencode 'grant_type=client_credentials' \

--data-urlencode 'client_id=<application_(client)_id>' \

--data-urlencode 'client_secret=<client_secret>' \

--data-urlencode 'scope=https://elite.com/prod/preview/3e/.default'

Note: OAuth2 Token URL is the URL to which the request is posted to.  The URL has the following format, where <tenant_id> is the customer’s Azure tenant id associated with the customer’s Entra ID

https://login.microsoftonline.com/<tenant_id>/oauth2/v2.0/token

Note: The scope for 3E instances is as shown in the following table:

Note: It is important not to pass client credentials through the Params section of Postman. This action will revoke client credentials due to security concerns with them being passed unencrypted over the public internet.

Request Response

A successful request response will return a status of 200 OK, with the following body:

{

    "token_type": "Bearer",

    "expires_in": 3599,

    "ext_expires_in": 3599,

    "access_token": "<access_token>"

}

Note Bearer access token has been redacted in the request response shown above

Note As shown above, the access token will be valid for 3599 seconds or 1 hour.  In other words, the same token can be used in subsequent API requests until it expires.