Two limits protect every plan.
A short burst window keeps the service responsive while a monthly quota controls total plan usage. Every authenticated response tells you where both stand.
Two limits
BURST
Short request window
Controls sudden concurrency and resets automatically after a short interval.
MONTHLY
Plan allowance
Tracks the total authenticated requests available in the current quota period.
Invalid authenticated requests can consume quota. Validate parameters before repeatedly sending a request that returns 400.
Quota headers
httpAuthenticated response headers
RateLimit-Limit: 60
RateLimit-Remaining: 54
RateLimit-Reset: 42
RateLimit-Policy: 60;w=60
X-Monthly-Quota-Limit: 10000
X-Monthly-Quota-Remaining: 9842
X-Monthly-Quota-Reset: 2026-09-01T00:00:00.000ZWhen a limit is reached
httpBurst limit response
HTTP/1.1 429 Too Many Requests
Retry-After: 42
RateLimit-Remaining: 0
X-Request-Id: req_01J6EXDZ...
{
"error": {
"code": "rate_limit_exceeded",
"message": "This access grant has reached its per-minute request limit.",
"requestId": "req_01J6EXDZ...",
"docsUrl": "https://api.exchangedz.com/docs/errors#rate_limit_exceeded"
}
}Use quota efficiently
- Request multiple asset codes together with the latest-rates endpoint.
- Cache latest results for the freshness your interface requires.
- Use cursor pagination rather than repeatedly requesting overlapping historical pages.
- Monitor the headers or /v1/me before batch work.
- Back off on 429 responses instead of creating parallel retries.