Guides/Integration
Rate limits
Control request volume and recover cleanly from HTTP 429 responses.
Rate limits protect the platform and are applied per credential and route profile.
When you receive 429
Pause requests, respect any retry guidance returned by the API and use exponential backoff with random jitter. Queue write operations instead of retrying them in parallel.
Recommended strategy
Cache read-only data where appropriate, paginate list endpoints, avoid polling resources that already emit webhook events and cap concurrent requests in background jobs.
Tip
Monitor 429 rates separately from other 4xx responses. A rising rate usually indicates a concurrency or polling problem, not invalid user input.