Authorization

All services share a single authorization and authentication mechanism — by token (Bearer Authentication), which must be passed with every request.

A unique login-password pair is created for each user account. It is required to obtain a token via the Account API.

To get an account, please contact our technical support team.

danger

When a user password is changed, all previously created tokens become invalid.

Headers

A service method call is accompanied by the following headers (unless the method description states otherwise):

• Passing the token

Authorization: Bearer <token>

• Specifying the type of the data being sent

Content-Type: application/json

• Specifying that the client can accept compressed data

Accept-Encoding: gzip,deflate