Skip to main content

Authenticated limits

Each row is your account’s budget for that route. Every API key on the account shares it.

Orders

Order book

Positions & trades

Account

Proxy wallet

Multisig

Partner API

Partner keys only. Each partner key has its own budget. See Partner API.

Public limits

Public read endpoints sit outside the account budgets above. 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 account 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 HTTP 429 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.

Real-time data

Setting up a channel, and what it sends.

API key permissions

Scopes you can grant a key, and the routes each one allows.
Last modified on November 12, 2026