Authentication
To access our API, your application must authenticate. We use the OAuth2 client credentials flow.
Don’t have API credentials?
If you don’t have a client_id
and client_secret
yet, you’ll need them to proceed. Please book a meeting to get set up.
Steps
Obtain an access token
First, your application needs to request an access token. This token identifies and authorizes your application.
POST /oauth2/token
Must be application/x-www-form-urlencoded
for this endpoint.
Request parameters:
Must be client_credentials
.
Your unique client ID.
Your client secret.
Response fields:
The bearer token to use for authenticating API requests.
Always returns “Bearer” for this authentication flow.
Token lifetime in seconds (e.g., 3600 = 1 hour).
Use the token in API calls
Include the obtained access_token
in the Authorization
header of your API requests:
Bearer token in the format: Bearer YOUR_ACCESS_TOKEN
If the access token is missing, invalid, or expired, the API will return a 401 Unauthorized
error. Your application should handle this by requesting a new token.
Request a new token before the current one expires to avoid service interruptions. Consider implementing automatic token refresh in your application.