Account credentialing and OAuth 2.0 client credentials token issuance (POST /accounts/token). See Authentication for the end-to-end flow. Account creation and environment setup are done with a Checkr Account Executive.
Exchange your client_id and client_secret for a Bearer access token (OAuth 2.0 client credentials).
grant_typeis optional; when sent it must beclient_credentials. Any other value returns400.scopein the request body is optional and ignored; scopes on the token come from your Auth0 client configuration.- Successful Auth0 responses are returned as
200with the standard token fields (access_token,token_type,expires_in,scope). - Invalid credentials or Auth0 rejections are passed through (typically
401) with Auth0's OAuth error body. - If the authentication provider returns an unexpected or unparsable response, a
500is returned with the standard API error array.
Step-by-step guide: Authentication.
OAuth 2.0 grant type. If omitted, client_credentials is assumed. Any other value is rejected.
Value:"client_credentials"
Example:"client_credentials"
- Checkr Trust APIhttps://api.checkrtrust.com/v1/accounts/token
curl -i -X POST \
https://api.checkrtrust.com/v1/accounts/token \
-H 'Content-Type: application/json' \
-d '{
"client_id": "your-client-id",
"client_secret": "your-client-secret",
"grant_type": "client_credentials",
"scope": "read:account create:account"
}'OK — Auth0 issued an access token. Use access_token as Authorization: Bearer <token> on subsequent API calls.
The JWT access token to use for API requests.
Example:"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
Seconds until the token expires. Typically 86400 (24 hours). Request a new token when this elapses — this endpoint does not issue refresh tokens.
Example:86400
Response
{ "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...", "token_type": "Bearer", "expires_in": 86400, "scope": "read:account create:account delete:account" }