Skip to main content

​
rate_limited

The response includes:
Retry-After is in seconds. Sleep at least that long, then retry. Limits are per workspace, not per key — adding more keys for the same workspace doesn’t increase your budget. See conventions.md §rate-limits for the bucket sizes. To avoid 429s in steady-state traffic:
  • Pre-throttle. Watch X-RateLimit-Remaining and slow yourself down before you hit zero.
  • Batch where possible. Use the largest reasonable limit (up to 200) on list endpoints to halve the number of requests.
  • Cache aggressively for read-heavy paths. Most /v1/projects responses are stable enough to cache for a few minutes in your client.
If you’re seeing 429s in normal traffic and need a higher limit, email support with your typical request rate and use case — we’ll discuss plan-specific quotas.