Rate Limits
How request limits work across plans.
Request rate limits
Requests are rate-limited per plan, in a fixed 15-second window that starts with your first request. When the window expires, your counter resets. If you exceed the limit, the API returns HTTP 429 and you must wait for the window to reset before retrying.
| Plan | Requests per 15 s |
|---|---|
| Free | 1 |
| Basic | 5 |
| Pro | 30 |
| Expert | 75 |
Bulk requests and construct limits
A POST /bulk request counts as one request against this limit, however many indicators it contains. It can contain multiple constructs, up to a per-plan limit. See Bulk / Multiple Assets for the plan-by-plan construct limits and an example of the 429 response when you exceed them.
Handling 429 responses
When rate-limited, the API returns:
{ "error": "Too Many Requests", "retryAfter": 9 }retryAfter is the number of seconds until the window resets. Wait that long, then retry. Do not retry immediately in a tight loop — that will keep triggering 429s.
Rate limit headers
Every authenticated response includes headers you can use to stay under the limit:
| Header | Description |
|---|---|
X-RateLimit-Limit | Requests your plan allows per window. |
X-RateLimit-Remaining | Requests left in the current window. |
X-RateLimit-Reset | Seconds until the current window resets. |
For long-running applications, consider using WebSocket streaming, which maintains one persistent connection and pushes updates without counting per-poll requests.
See the full list of indicators, or start for free.