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

RU-2003: API write rate limit exceeded

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

On the wire

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

Common causes

  • Bulk-creating or bulk-updating resources in a fast loop.
  • A sync job replaying its whole state on every run instead of diffing.

How to fix it

  1. Honor the Retry-After header and spread bulk operations out.
  2. Only write what changed: diff before you sync.

Related codes

  • RU-2002: API read rate limit exceeded

Still stuck?

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