Skip to main content
This authentication scheme allows an application to obtain an access token by exchanging its application credentials, such as client ID and client secret. This flow is particularly suitable for Machine-to-Machine (M2M) applications, including your application or backend services, as it enables the authentication and authorization of the application itself, rather than that of a user. To obtain the access token, use the following:
  1. A POST request.
  2. The https://vantage-us.abbyy.com/auth2/connect/token resource.
  3. A Content-Type header with the application/x-www-form-urlencoded encoding.
  4. A request body with the following parameters:
ParameterDescription
client_idApplication identifier.
client_secretSecure application key.
grant_type=client_credentialsSpecifies that the client credentials grant type is used.
scope=openid permissions global.wildcardSpecifies the permission scope.
Sample request (Windows): 
curl --location --request POST "https://vantage-eu.abbyy.com/auth2/connect/token" \
  --data-urlencode "client_id=client_id" \
  --data-urlencode "client_secret=client_secret" \
  --data-urlencode "grant_type=client_credentials" \
  --data-urlencode "scope=openid permissions global.wildcard"
Also available for other regions and Linux with equivalent commands. The server’s response to your request will contain the access token: 
{
  "access_token": "<redacted>",
  "expires_in": 2592000,
  "token_type": "Bearer",
  "scope": "openid permissions global.wildcard"
}
For more information about Client Credentials, visit this link.