Error Codes

This page lists all error status codes used across the API.

Security Errors

Status	Description
`INVALID_SIGNATURE`	Request signature validation failed. Check your signing implementation.

Status	Description
`EXTERNAL_SERVICE_TIMEOUT_ERROR`	Request to external service timed out. Retry the request.

Errors returned by our endpoints.

Status	HTTP Code	Description
`UNKNOWN_OPERATOR`	404	No operator exists for the provided `operatorId`

Errors you should return from your endpoints.

Status	HTTP Code	Description
`INSUFFICIENT_BALANCE_ERROR`	200	Player does not have enough balance for this bet
`DUPLICATE_TRANSACTION_ERROR`	200	Transaction ID already exists with a different payload
`BONUS_ERROR`	200	Bet does not pass bonus rules
`BET_LIMIT_REACHED_ERROR`	200	Player has reached their betting limit
`UNKNOWN_ERROR`	200	Bet could not be registered

Status	HTTP Code	Description
`DUPLICATE_TRANSACTION_ERROR`	200	Transaction ID already exists with a different payload
`UNKNOWN_ERROR`	200	Rollback could not be processed

Status	HTTP Code	Description
`DUPLICATE_TRANSACTION_ERROR`	200	Transaction ID already exists with a different payload
`UNKNOWN_ERROR`	200	Win could not be registered

All error responses should include the status field and echo back the requestId and clientPlayerId:

{
  "status": "ERROR_CODE_HERE",
  "requestId": "original-request-id",
  "clientPlayerId": "player-id"
}

All responses must be signed with the X-Marbles-Signature header, including error responses.