Rate limits

How the gateway signals rate limiting and how to back off.

If you send requests too quickly, you may receive a 429 with a Retry-After header.

What you get back

HTTP/1.1 429 Too Many Requests
Retry-After: 2
Content-Type: application/problem+json

{
  "type": "https://errors.zeam.app/rate-limited",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "Rate limit exceeded.",
  "requestId": "01J…"
}

How to handle it

• Read the Retry-After header (seconds) and wait that long before retrying.
• Use exponential backoff with jitter for repeated 429s.
• Cache your access token and reuse it until close to expiry rather than re-issuing on every call.

Specific rate limits are not yet published. Build your integration to handle a 429 gracefully rather than assuming a fixed ceiling.