Skip to main content
Requests are rate-limited per API key. When you exceed the limit the API responds 429 rate_limited with headers telling you the policy and when to retry:
  • Retry-After is the number of seconds to wait before retrying.
  • RateLimit-Policy describes the budget (here, 600 requests per 60-second window).

Backing off

Respect Retry-After, and add jitter when you retry so many clients do not retry in lockstep. A simple, safe strategy:
Separately, revealing the codes of a single order is bounded on its own with reveal_rate_limited, to prevent enumeration; poll the order rather than hammering the codes endpoint.