Skip to main content
Rate limiting on the Orgo API is per endpoint, and the key differs by endpoint: some limits count per account, some per IP address, some per email address or per OAuth client. There is no single global bucket, and most endpoints have no application-layer limit at all; they are only protected by platform-level throttles. Limits exist where an endpoint sends email, is expensive, or can be used to guess secrets.

How a limit looks

When you hit a limit the API answers 429 Too Many Requests, normally with a Retry-After header in seconds:
The body is a framework error (see Errors) whose detail names the cause, for example Too many ticket holds. Please try again shortly. Read the status and the header, not the exact text. Read-heavy endpoints (GET /api/v1/users, GET /api/v1/events, and so on) are not application-rate-limited under normal circumstances, so you can paginate freely.

Limits you can hit

Newsletter sends go through a managed outbound queue rather than a visible limit: the platform sends at a steady rate, so a large campaign takes minutes to flush, not a 429. Where an endpoint’s reference page does not mention a limit, assume none beyond platform protections.

Designing for the limits

Many endpoints have explicit bulk variants: POST /api/v1/contacts/bulk-delete, POST /api/v1/waitlist_entries/bulk-approve, POST /api/v1/events/{uuid}/attendees-bulk and others. Each bulk call is one request and is far cheaper than N individual calls.
itemsPerPage=100 is the cap. A smaller page size means more requests for the same data. Use 100 unless you have a reason not to.
If you find yourself polling GET /api/v1/product_payments?status=open every few seconds, subscribe to the product_payment.updated webhook instead. See Webhooks.
Do not sign in before every request. Keep the session JWT (about 11 days by default) and sign in again only when a request returns 401. Cache OAuth access tokens and refresh on demand, never on every call. An Api-Token does not expire unless you set an expiry.
For nightly syncs, schedule them in your tenant’s off-hours. A thousand sequential requests at noon still adds latency on top of normal member traffic.

Retry pattern

A safe pattern that handles both 429 and transient 5xx:
The same pattern in JavaScript or TypeScript:

Per-plan limits

There is no per-plan rate limit at the application layer. Higher-volume plans get more generous platform-level concurrency, but the endpoint limits above are the same for every plan. If you need a limit raised for a specific tenant and endpoint, such as a high-volume webhook sender or a large nightly export, contact support.
  • Errors: the 429 envelope and the full retry strategy
  • Webhooks: the cure for polling