REST
Each client IP address gets a budget of 20 requests per second, with bursts of up to 40. Every response tells you where you stand:
Over the limit, you get HTTP
429 with code RATE_LIMITED. Wait Retry-After seconds, then continue.
New orders have their own budget per API key: 10 per second, bursts of 20. A batch counts one per item it places; an item past the budget is answered RATE_LIMITED in its own result while the rest of the batch stands. Cancels are never limited — alone or in a batch, you can always pull your orders.
API tiers
Trade more and your keys get a higher order budget. Your tier is set once a day (UTC) from every contract your account traded in the last 30 days, maker or taker.
Each key has its own budget at your tier. Your tier and how far you are from the next one are on your Portfolio page, under API tier. If we’ve set a custom limit for your account, it applies instead of the table, shared by all your keys.
Failed API-key attempts have their own, much smaller budget. An address that keeps sending invalid keys is locked out for at least a minute and gets
429 until then.
Websocket
Staying under the limits
- Use the websocket for anything live. One connection with a series subscription replaces polling every market, and updates arrive as they happen.
- Use REST for a one-off read or to seed state, then follow changes on the websocket.
- Back off on
429; don’t retry in a tight loop.