X-RateLimit-Limit for your effective limit.
Domain-scoped keys each have their own separate 1,000-request hourly allowance. Filtering a request by domain does not give an unscoped key a separate allowance. Windows reset at the start of each UTC hour, and rejected requests also increment the counter.
Response headers
Every response includes rate limit information:When you hit the limit
When you exceed the rate limit, the API returns a429 Too Many Requests response:
Retry-After header tells you how many seconds to wait before retrying.
A 429 is an unsuccessful request, not an empty result set. Keep previously loaded visitors visible, show a temporary refresh error, and retry after the specified delay. Do not replace cached visitor data with an empty list on an API error.
Best practices
- Implement exponential backoff — when you receive a 429, wait the
Retry-Afterduration before retrying - Cache responses — if you’re making the same request frequently, cache the result
- Use pagination efficiently — fetch larger pages (up to 100 items) to reduce total requests
- Sync incrementally — use the
?sinceparameter to only fetch new data since your last sync