Skip to main content

Authorization

caution

Basic authentication is currently deprecated for the Jumio REST APIs.

All calls to Jumio REST APIs should be authorized using OAuth2 Bearer Tokens. You obtain the bearer token by calling the Access Token URL (OAuth2) for your region with your API token and secret values, which you can find in the Jumio Portal under:

Settings > Identity Verification > API credentials > OAuth2 Clients

info

A transaction-specific token is generated when you create or update an account. This token, used for uploading credentials and finalizing the workflow, is included in the response of the account creation or update call.

As a security best practice, requests for bearer tokens should be server-to-server, to avoid making your Client ID and Client secret values available to an end-user’s device. Regardless of the integration channel, the end-user’s device should notify your server when a token is required. Your server should make the call to the Jumio OAuth server, and then pass the token to the end-user device.

Client ID and Client secret are used to generate an OAuth2 access token. OAuth2 has to be activated for your account. Contact your Jumio Account Manager for activation. Access your Client ID and Client secret from the Portal. See API Credentials.

important
  • OAuth 2.0 access tokens are valid for 60 minutes (3600 seconds) by default.
  • To avoid unnecessary authentication requests, access tokens are cached internally, and consecutive calls may return the same token. To prevent 401 Unauthorized errors, refresh the token a few minutes before it expires. You can check the token’s expiration by decoding it and examining the exp (expiration) and iat (issued at) claims.
  • For testing purposes, you can use Postman’s built-in OAuth 2.0 authorization type (under the Authorization tab), which can automatically retrieve and manage tokens across your requests or collections.

The TLS Protocol is required to securely transmit your data, and we strongly recommend using the latest version. For information on cipher suites supported by Jumio during the TLS handshake see Supported Cipher Suites.

Access Token URLs (OAuth2):

  • US: https://auth.amer-1.jumio.ai/oauth2/token
  • EU: https://auth.emea-1.jumio.ai/oauth2/token
  • SG: https://auth.apac-1.jumio.ai/oauth2/token
note

Calls with missing, incorrect, or suspicious headers or parameter values will result in HTTP status code 400 Bad Request Error or 403 Forbidden. oauth2/token requests are subject to Rate Limits. The default rate limit is 10 per second. If the rate limit is reached, a HTTP 429 Too many requests status code is returned.

Example: Request Access Token

curl --location 'https://auth.amer-1.jumio.ai/oauth2/token'\
-u CLIENT_ID:CLIENT_SECRET \
--header 'Accept: application/json'\
--data-urlencode 'grant_type=client_credentials'