Rate limits & quotas

Limits may vary by plan and endpoint class. Size integrations with your account team for sustained high QPS.

Expected client behavior

• On 429 Too Many Requests, read Retry-After when present and sleep before retrying.
• Without Retry-After, use exponential backoff with jitter (e.g. base 500ms, cap 60s).
• Avoid unbounded parallel creates; queue writes and smooth bursts.

Headers you may see

When rate limiting is active, responses may include standard rate-limit headers depending on gateway configuration. Treat any 429 as a signal to slow down.

Burst vs steady load

Batch CRM backfills or report generation in chunks with sleeps between chunks. Combine with idempotency on agent calls to make retries safe.

Next: Monitoring & logs →