Error Codes

When a callback cannot be processed, the wallet responds with status: "ERROR" and one of the codes below instead of the documented success payload.

Code	Description	Typical cause
1001	incorrect or missing parameters sent	a required parameter is absent or malformed
1002	invalid hash	the `X-API-KEY` header is missing or holds the wrong API key
1003	invalid currency	the requested currency does not match the player’s wallet
1004	unknown error	any failure that does not map to another code
1005	session expired	the game session token is no longer valid
1006	insufficient funds	the player’s balance does not cover the bet
1007	duplicate transactions	the `transaction_id` has already been processed
1008	not existing cancel request	the `aborted_transaction_id` of a cancel is unknown
1009	invalid player id	no player exists for the given `user_id`
1010	transaction not found	the referenced transaction does not exist
1011	freespins expired	the Gift Spin is past its `valid_until`

Error response example


{
    "status": "ERROR",
    "error_code": 1001,
    "error_message": "incorrect or missing parameters sent",
    "balance": 100.05
}

Parameter	Type	Required	Description
status	string	yes	always `ERROR`
error_code	integer	yes	one of the codes above
error_message	string	yes	human readable description, for logging
balance	float	no	player’s current balance, when it can be determined

A rejected API key is answered with HTTP 403 Forbidden at the transport level, as described in the Introduction — the error codes above apply to requests that were authenticated successfully but could not be processed.