Skip to main content

Limits

Rate limit headers

Every authenticated response includes these headers: Example:

Handling 429 responses

When you exceed the rate limit, the API returns 429 with a retry_after_seconds field:

Best practices

  • Check headers proactively — Slow down when X-RateLimit-Remaining drops below 10
  • Use pagination wisely — Larger page_size (up to 200) means fewer requests
  • Cache responses — Portfolio summary and residual reports don’t change frequently
  • Use updated_since — Incremental sync avoids re-fetching unchanged records
  • Spread requests — Avoid bursting 120 requests in the first second of a window