Skip to content
Error codes · Rate limits, quotas & billing

RU-2002: API read rate limit exceeded

This API key made more read requests per minute than the read budget allows. The Retry-After header says how long to back off.

On the wire

Ships with HTTP status 429, carrying "code": "RU-2002" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • Polling in a tight loop instead of respecting Retry-After.
  • Many workers sharing one API key.

How to fix it

  1. Honor the Retry-After header before retrying.
  2. Cache reads that don't need to be fresh every second.
  3. Give independent systems their own API keys so one noisy consumer doesn't starve the rest.

Related codes

  • RU-2003: API write rate limit exceeded

Still stuck?

Ask support and mention RU-2002: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.