Updated May 4th, 2026
Rate limits are enforced on a per-interval basis of 250 requests every 10 seconds. Two independent limits apply:
Per IP address: 250 requests / 10 seconds
Per API token: 250 requests / 10 seconds
Both limits are evaluated independently. A request that exceeds either limit will be throttled.
If your application distributes requests across multiple IP addresses using a single API token, the per-token limit still applies to the total volume of requests made with that token.
You can determine when to retry by checking the response headers:
Access Token Headers
RateLimit-Limit — the maximum number of requests allowed in the current interval
RateLimit-Remaining — the number of requests remaining in the current interval
RateLimit-Reset — the timestamp indicating when the current rate limit window resets
These headers are included on every API response. When a request is rate limited (429 response), an additional header is included:
Retry-After — the number of total seconds in an interval to wait before retrying
Example
Successful request:
RateLimit-Limit: 250
RateLimit-Remaining: 220
RateLimit-Reset: 1744654730
Rate-limited request (429 response):
RateLimit-Limit: 250
RateLimit-Remaining: 0
RateLimit-Reset: 1744654730
Retry-After: 10