Rate limits
Quotas, backoff, and per-tenant concurrency.
The API enforces rate limits per workspace to keep the platform responsive for everyone.
Reading the headers
Every response includes the current limit, the remaining quota, and when the window resets. When you exceed a limit you'll get a 429 with a Retry-After header telling you how long to wait.
Backoff
On a 429 or a 5xx, retry with exponential backoff and jitter rather than retrying immediately in a tight loop. Respect Retry-After when it's present — it's the authoritative wait time.
Concurrency
Long-running work (catalog syncs, recommendation runs) is governed by per-tenant concurrency rather than a simple request rate, so one heavy job can't starve your other calls. Connector syncs additionally respect the provider's own limits — for NetSuite, its account-wide and per-integration concurrency governance.