Appearance
Error codes
In order to inform our system about particular error, you should respond with HTTP status code 400 and the following body:
json
{
"code": 7,
"message": "Not enough money"
}The message field contains arbitrary error description. Our backend logic relies only on the code field value.
General errors
| Code | Description |
|---|---|
1 | Request signature is invalid |
3 | An invalid token The user will be requested to re-login |
4 | The token is out of date The user will be requested to re-login |
5 | A request data validation error |
100 | System error. This error triggers the Rollback |
Place bet errors
This error codes will be respected only for place bet requests.
| Code | Description |
|---|---|
7 | Not enough money |
8 | The bet has already been processed |
9 | The user is blocked |
10 | Request timeout on partner system. |
If you respond with error code 100 the Rollback will be triggered. All other HTTP status codes except 200 and 400 will also trigger the Rollback.
Self-exclusion errors
This error codes will be respected only for place bet requests.
If your product offers self-exclusion program, you can use the following error codes:
| Code | Description |
|---|---|
11 | The user’s stake limit has been reached |
12 | The user loss limit has been reached |
13 | The bet count limit has been reached |
14 | The user is self-excluded |
15 | The user is not verified |
16 | The user is not old enough |
Settle errors
This error codes will be respected only for settle requests.
| Code | Description |
|---|---|
20 | The transaction recalculation is blocked This error will forbid us to change the result of previously settled bet |
21 | Recalculation is blocked due to insufficient amount of money on the balance Error, with which the partner will respond to the recalculation if the balance goes negative |