Documentation menu
Request limits
Each token is on a plan with a number of requests per billing cycle.
Checking where you stand
Every response tells you how many requests you have left:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Requests included in your plan per cycle |
X-RateLimit-Remaining | Requests you have left in this cycle |
X-RateLimit-Reset | When the cycle resets (Unix timestamp, in seconds) |
When you reach the limit
Requests get a 429 Too Many Requests until the cycle resets:
{
"error": "Request limit reached for your plan in the current billing cycle",
"limit": 10000
}The Retry-After header says how many seconds are left until the reset. Rejected requests don't
count against your quota.
Making requests go further
- Ask for bigger pages.
per_pagegoes up to 100, so you need fewer requests to walk through results. - Filter on our side. One request with the right filters beats fetching everything and filtering yourself.
- Cache what doesn't change often. Tag and category names, and most game details, are stable for days.