Rate Limits
Rate limits protect service availability and keep the API fast and reliable for every reseller.
Rate limit tiers
| Tier | Limit | Burst | Notes |
|---|---|---|---|
| Public (no key) | 30/min/IP | · | Health, products and regions endpoints |
| Authenticated | 120/min/key | · | Default allowance for every reseller |
| check-player | 10/min/key | · | Stricter allowance that protects upstream availability |
Response headers
Every response carries your current allowance as headers:
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 119
X-RateLimit-Reset: 1724774400When the limit is reached, the API returns 429 with a Retry-After header in seconds:
HTTP/1.1 429 Too Many Requests
Retry-After: 37
{
"type": "https://api.revolixgaming.com/errors/too_many_requests",
"title": "Rate limit exceeded",
"status": 429,
"detail": "Too many requests. Retry after 37 seconds.",
"request_id": "req_01J..."
}Best practices
- Monitor
X-RateLimit-Remainingand pace your client accordingly. - Apply exponential backoff when you receive a 429.
- Respect
Retry-Afterand avoid hammering the API. - Cache product responses for 60 seconds to reduce call volume.