Authenticating to Jumio's API

Authorization for the Jumio REST APIs has changed. Basic authentication is deprecated. Oauth2 bearer tokens are required to authorize API calls. See Authorization for detailed information.

In V2 you can authenticate each API call with basic credentials (token + secret). The Jumio Platform supports OAuth2 bearer tokens for authentication. You can generate a bearer token by calling a dedicated API endpoint.

While the Jumio Platform continues to support basic authentication, you are strongly encouraged to use the more secure bearer tokens. Support for basic authentication will be discontinued at some point in the future.

Netverify API Authentication

All Document Verification API calls are protected using HTTP Basic Authentication. Your Basic Auth credentials are constructed using your API token as the user-id and your API secret as the password. You can view and manage your API token and secret in the Customer Portal under Settings > API credentials.

⚠️ Never share your API token, API secret, or Basic Auth credentials with anyone — not even Jumio Support.

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.

Jumio Platform API Authentication

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 Customer Portal under:

Settings > Identity Verification > API credentials > OAuth2 Clients

See Authorization.