GETTING STARTED

Rate limits

Some endpoints may enforce throttles, abuse protections, or quota-style limits to protect the platform. When that happens, the server may respond with 429 Too Many Requests and may include retry guidance in response headers.

Possible response headers

Retry-Afterinteger
Some throttled responses may include the number of seconds to wait before retrying.
X-RateLimit-*varies
Some endpoints may expose additional rate-limit metadata such as a limit, remaining budget, or reset timestamp.

Handling 429s

  • If a response includes Retry-After, honor it before retrying.
  • On sustained throttling, back off exponentially and add jitter so your workers don't all retry at once.
  • Batch and cache where possible instead of polling aggressively.
  • Use the endpoint reference as the source of truth for any route-specific quota or throttle behavior.