Skip to main content

HTTP status codes

Error response format

Common error messages

Validation errors

Validation errors list the problem per field:

Handling rate limits

The limit is 60 requests per minute per API key. When you receive 429:
  1. Wait before retrying (exponential back-off).
  2. Reduce the request frequency.
  3. Cache responses where you can (the catalog in particular).
Back-off schedule: 1 s, 2 s, 4 s, 8 s… doubling up to a maximum (for example 60 s).

Refunds

If an order fails, your balance is refunded automatically. No action is required.

Best practices

1. Always check status codes

2. Validate before you submit

  • Game top-ups: POST /api/catalog/{id}/verify checks the player ID before you pay.

3. Handle timeouts safely

Orders are processed asynchronously. If a request times out:
  • Do not retry immediately. The first request may have gone through.
  • Look at GET /api/orders to see whether the order exists.
  • Save any order or transaction ID you did receive, and poll its status endpoint.

4. Monitor your balance

5. Log what you send

Getting help

If an error persists:
  1. Check your API key and IP allow-list.
  2. Check your balance.
  3. Contact support with the timestamp, the request (without secrets), the message you received and the order ID if you have one.