HTTP status codes

We use HTTP status codes to indicate the result of a request.

HTTP status codes can be categorized in following groups:


200 OK

Request was successfully completed. Synchronous operations.

201 Created

Request was successfully accepted. Asynchronous operations.

204 No Content

It has the same meaning as 200 OK but no content is sent in response body.

Authentication, Authorization Errors

401 Unauthorized

Request was not authenticated. The authorization token used probably invalid or expired.

403 Forbidden

Request was not authorized. The authorization token used probably does not have appropriate endpoints included or wrong entity (payin, payout) ID is used.

Request errors

400 Bad Request

Invalid request, in most cases mandatory fields are missing or some other aspects of the API contract was not fulfilled. This is an integration error, and cannot be solved programmatically in runtime.

404 Not Found

Wrong endpoint (URL or method) or missing API version header, see Versioning for more info.

406 Not Acceptable

Business error, varies to every API endpoint. This type of error is meant to be handled programmatically in runtime. Each 406 response description in endpoint documentation contains a list of possible error codes.

409 Conflict

Performed request was already accepted, see Request IDs for more info.

410 Gone

The entity specified via the endpoint URL was not found. This means the wrong entity ID was used in the URL or the entity was deleted.

429 Too Many Requests

Too many requests have been sent by the merchant. The limit is 5 requests per second.

Platform errors

5XX - Internal Server Error

Our platform is having a bad time, but we are working on it. Contact our support for more details.