429 Organization rate limit exceeded

The organization's combined limit was reached across its API keys: all its keys together get twice the per-key limit per 60 seconds (Growth: 300 per key, 600 across every key). Every key in the organization is refused until the window resets, even one that has made no requests.

Safe to retry after a backoff

What causes it

• Several keys (or integrations) busy at the same time, each within its own limit but together over the organization ceiling.
• Minting extra keys to multiply the per-key limit: the organization ceiling caps the total.

How to fix it

• Honour the `Retry-After` header. `X-RateLimit-Scope: organization` on a response means the organization ceiling is the one closer to running out, and the `X-RateLimit-*` headers then describe it.
• Spread scheduled jobs across windows, or batch writes (a batch request counts one unit per 10 rows).

Example response

HTTP/1.1 429
Content-Type: application/problem+json

{
  "type": "https://sealdeal.ai/errors/organization-rate-limit-exceeded",
  "title": "Organization rate limit exceeded",
  "status": 429,
  "detail": "..."
}

`type` is stable and safe to branch on in code. `detail` is specific to your request and is the field to read for the particulars; its wording may change.