Get Access Token
POST/
Use this endpoint to retrieve an access token for accessing the REST APIs.
Request
Responses
- 200
- 400
- 401
Get Access Token - 200
Response Headers
Alt-Svc
Via
content-length
date
x-request-id
Get Access Token - 400 (invalid body value)
Response Headers
Alt-Svc
Via
content-length
date
x-request-id
Get Access Token - 401 (wrong client id / client secret)
Response Headers
Alt-Svc
Via
content-length
date
x-request-id
Response Details
Success Response (200)
When the token request is successful, you'll receive a JSON response containing the access token and related metadata:
Response Fields
Field | Type | Description | Example |
---|---|---|---|
access_token | string | The JWT access token to use in API requests | "eyJhbGciOiJSUzI1NiIsInR5..." |
expires_in | number | Token expiration time in seconds | 1800 |
refresh_expires_in | number | Refresh token expiration time (always 0 for client credentials) | 0 |
token_type | string | The type of token (always "Bearer") | "Bearer" |
not-before-policy | number | Token validity start time (always 0) | 0 |
scope | string | Token scope (typically "profile" for client credentials) | "profile" |
Error Responses
400 Bad Request - Invalid Request Format
Occurs when the request format is incorrect:
{
"Error": "Unsupported grant type : client_credentials1",
"ErrorCode": "invalid_request"
}
Common causes:
- Incorrect
grant_type
value - Missing required parameters
- Invalid request body format
401 Unauthorized - Invalid Credentials
Occurs when client credentials are invalid:
{
"Error": "ClientId is Invalid",
"ErrorCode": "invalid_client"
}
Common causes:
- Incorrect
client_id
orclient_secret
- Expired or revoked credentials
- Malformed Basic Authentication header