429 Rate limit exceeded

The key exceeded 60 requests per 60 seconds. The limit applies to every endpoint.

Safe to retry after a backoff

What causes it

• One key shared across several automations, so their traffic adds up against a single ceiling.
• An unbounded loop paginating without pause.

How to fix it

• Honour the `Retry-After` header rather than retrying immediately. Every response also carries `X-RateLimit-*` headers you can steer by.
• Mint one key per integration. The ceiling is per key, so splitting keys splits the budget.

Example response

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

{
  "type": "https://sealdeal.ai/errors/rate-limit-exceeded",
  "title": "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.