Rate limits

Requests are rate limited per organization. When you exceed the limit, the API responds with 429 and the RATE_LIMIT_EXCEEDED error code.

{
  "code": "RATE_LIMIT_EXCEEDED",
  "message": "Too many requests. Retry after a short delay.",
  "request_id": "b3f1c8d2-2b9e-4c5e-8a1f-2c7d6a9e4b1a"
}

Handling 429

A 429 is safe to retry. Back off and try again:

• Use exponential back-off with jitter, as shown in errors and retries.
• Pair any retried POST with an Idempotency-Key so the eventual success is not applied twice.
• Smooth out large batches (for example a nightly sales-event export) instead of sending them in one burst.

Designing for the limit

Because limits are per organization, concurrent workers share the same budget. Add client-side throttling for high-volume pipelines so steady traffic stays under the limit rather than hitting it and retrying. If your integration consistently needs a higher ceiling, contact support.