rate_limit_exceeded — key request rate exceeded

The request was not performed. The body has reason: "rate_limit_exceeded" (the same code in error_code) and retry_after in seconds; the headers carry Retry-After and X-RateLimit-*.

The key exceeded one of its request-rate windows limits.requests.per_minute / per_hour / per_day. Requests are counted, not work volume: a light and a heavy request weigh the same. By default a key has no request-rate limit — the windows are set in the key settings.

Wait retry_after seconds and retry. If you hit it constantly, lower the rate: replace order status polling with realtime events, and pause between catalog pages.

The same request after retry_after seconds. The key's active windows are visible in the developer dashboard.

• Guide: limits and the 429 code
• Guide: realtime instead of polling
• Dashboard: key windows