Skip to main content
The Orbscan API applies rate limits per account, based on your plan. All API keys on your account share the same limits. The daily request count resets at 00:00 UTC. To track your usage against these limits, open the Usage tab of the API Dashboard. For current plans and pricing, see orbscan.com/pricing. If you need higher limits, contact Orbscan.
A rate-limited request returns HTTP 429 with message: "Rate limit exceeded", status_code: "0", and data: null.

Handling 429 responses

When you receive a 429 response, wait before trying again. Use exponential backoff and cap the number of retries. If repeated retries still return 429, stop and wait longer rather than continuing to send requests.

Best practices

These practices reduce unnecessary requests:
  • Cache infrequently changing data. Market names, descriptions, and outcomes rarely change. Cache them locally and reserve requests for time-sensitive data.
  • Paginate, don’t dump. Use the limit query parameter and the nextCursor cursor to fetch data in manageable pages rather than requesting the largest possible payload in a single call. This keeps individual responses fast and reduces the chance of timeouts.
  • Poll responsibly. Choose a polling interval that matches your plan’s limits and freshness requirements.