Skip to main content

rate-limited

HTTP status: 429 Too Many Requests Type URI: https://docs.evinor.ai/problems/rate-limited

You exceeded a request budget: either the per-key budget for the current one-minute window, or a per-account limit on an individual operation (for example concurrent event searches). Both carry Retry-After.

A rate-limited request was refused before it ran, so nothing was charged. If you supplied an Idempotency-Key, retry under the same key once the wait has passed.

Response headers​

  • Retry-After — seconds to wait before retrying.
  • RateLimit-Limit / RateLimit-Remaining / RateLimit-Reset — the budget, what's left, and the Unix-seconds reset time.

How to resolve​

  • Wait the number of seconds in Retry-After, then retry.
  • Watch RateLimit-Remaining and slow down before you hit zero.
  • Add randomized backoff across concurrent workers so they don't retry in lockstep.
  • Prefer webhooks over tight polling loops.

See Rate limits for the full budget and header semantics.