API Error codes

Here, you can find examples of error codes and their full description, please, notify us, if they occur.

Code	Status	Message	Balance	Description of the response
400	false	Unknown error occurred	The balance doesn’t need to be sent	Used when no other code fits the error type
404	false	User not found	The balance doesn’t need to be sent	Used when user doesn’t exist
405	false	User blocked	The balance doesn’t need to be sent	Used when the user is blocked or has reached its limit
406	false	Debit transaction not found in this event	Include the current balance amount to the error response	Used when transaction doesn’t exist
417	false	Token not found	The balance doesn’t need to be sent	Used when token does not match
410	false	Token expired	The balance doesn’t need to be sent	Used when player authentication process fails, for example player's session ended
409	false	Duplicate. Transaction already exist	Include the current balance amount in the error response	Used when transaction was already processed
402	false	Insufficient funds to place current wager	Include the current balance amount in the error response	Used when there is not enough balance to place a bet
456	false	Limit exceeded	The balance doesn’t need to be sent	Betting limit has been reached

The request is executed using the GET method.

The following info is an example of the default supported error response format:

Example of error

{
    "status": false,
    "balance": 125000,
    "errors": {
        "code": 404,
        "error": "Description"
    }
}