Error Reference

Every error follows the RFC 9457 Problem Details format, carrying a type URL, status, title, detail and request_id.

Format

{
  "type": "https://api.revolixgaming.com/errors/unauthorized",
  "title": "Unauthorized",
  "status": 401,
  "detail": "Missing or invalid API key.",
  "request_id": "req_01JABCDEFGH"
}

Error catalogue

Status	Type	Title	Detail
401	`/errors/unauthorized`	Unauthorized	The API key is missing, invalid, or the account has been disabled.
403	`/errors/forbidden`	API access disabled	The key is valid but API access has been disabled for this account.
402	`/errors/insufficient_wallet`	Insufficient RX Points	Your wallet balance is insufficient for this order.
404	`/errors/not_found`	Resource not found	The resource does not exist or does not belong to your account.
422	`/errors/missing_idempotency_key`	Missing Idempotency-Key	The Idempotency-Key header (UUID v4) is required on every POST request.
422	`/errors/order_rejected`	Order rejected	The order was rejected due to validation, product availability or payment failure.
409	`/errors/idempotency_in_progress`	Idempotency in progress	A request with the same key is still processing. Wait before retrying.
409	`/errors/idempotency_conflict`	Idempotency conflict	This Idempotency-Key has already been used with a different payload.
429	`/errors/too_many_requests`	Rate limit exceeded	The request limit has been reached. See the Retry-After header.
500	`/errors/internal_error`	Internal server error	A server error occurred. Include the request_id when contacting support.

Handling guidelines

401/403: check your key and API access status before retrying.
402: top up RX Points before retrying.
409: use a new Idempotency-Key for a new request.
422: inspect the failed fields in the errors object.
429: respect the Retry-After header and slow down.
5xx: retry with exponential backoff and keep the request_id for support.