Authenticated limits
Each row is the per-API-key budget for that route.Orders
Positions & trades
Account
Proxy wallet
Multisig
Public limits
Public read endpoints are not metered against your API-key budget. They are limited per client IP at the edge.Order book
Summary & metadata
Trades
Markets & sports data
These endpoint families share a single combined budget of 500 requests per 60s per client IP. A burst on any one of them draws down the budget for all of them.Response headers
Every authenticated response carries the state of your budget for that route, so read the limit in force from the headers rather than hardcoding a value.Global limit
Beyond the per-key budgets above, all unauthenticated traffic shares a single global bucket at the edge of 35,000 requests per 10 min window.When limits are exceeded
A request over the limit returns HTTP429 Too Many Requests. On a 429, X-RateLimit-Remaining
is 0 and the Retry-After header gives the seconds to wait before retrying — back off until then
rather than retrying immediately.
Use realtime instead of polling
Subscriptions do not use your request budget.Related
Real-time data
Setting up a channel, and what it sends.