Understand your allowance.
All keys on an account share a request allowance. Check your plan and usage in the dashboard.
Request limits
Rate limits use fixed minute windows. Monthly allowances reset at 00:00 UTC on the first day of each month. Requests admitted to the upstream service count towards usage, including provider failures.
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 59
X-MonthlyLimit-Remaining: 49999
# On a rate-limited response:
Retry-After: 30Read Retry-After before retrying a rate-limited request. See pricing if you need a larger allowance.
Handle errors
400Check parameter names, ID values, and dates.
401Your key is missing, invalid, expired, or revoked.
403The request origin or key scope is not allowed.
404The endpoint or requested record does not exist, or the market is unsupported.
422Check the endpoint’s parameter types and allowed combinations.
429Read Retry-After before retrying.
503Retry with exponential backoff and respect Retry-After when present.
Gateway errors use {"error":"message"}. Upstream validation errors may use a detail field. Check the endpoint reference for response schemas.
Keep responses manageable
V1 collections are unpaginated; use filters to narrow your requests. V2 uses cursors—see the global contract guide for pagination and date-range rules.