Skip to main content
Rate limits protect API availability and enforce fair usage per plan. Limits apply per API key on the hosted API. See Pricing & plans for tier details.

Monitor usage

Response fields

The dashboard also shows daily usage and plan details.

Throttled responses

When you exceed per-minute or daily quotas, the API returns HTTP 429:
or, for daily caps:
The response includes a Retry-After header (seconds). Honor it before retrying.

Plan limits on historical queries

Historical endpoints also enforce resolution and lookback. Violations return HTTP 403:
On 429, read the Retry-After header and sleep at least that many seconds before retrying.
If Retry-After is absent, use increasing delays (e.g. 1s → 2s → 4s) with a maximum retry cap.
Reuse HTTP connections with requests.Session (Python) or httpx.Client to reduce TLS overhead.
Paginate with cursors instead of unbounded parallel fan-out. Pace sequential history calls (~200ms) when backfilling many markets.
Use the coarsest resolution that meets your analysis needs — fewer buckets, fewer pages, lower quota usage.

Retry example

Need higher throughput? See Enterprise on the pricing page or email contact@polyorderbooks.com.