Rate Limits

Operational guidance for managing request volume and handling temporary failures gracefully.

The limits

• 100 requests per minute per company across all endpoints.
• Exceeding the limit returns 429 RATE_LIMIT_EXCEEDED.
• Rate limits are independent of monthly API credit quotas, see Quotas & Credits.

Operational guidance

• Avoid unnecessary requests: only call the API when your integration genuinely needs fresh data.
• Cache stable data: templates and categories don't change constantly; cache them and refresh periodically instead of requesting them on every operation.
• Avoid aggressive polling: poll status with reasonable intervals, or better, use webhooks to be notified when something changes.
• Prefer webhooks for event-driven workflows: notifications replace repeated status checks.
• Retry temporary failures with increasing delays: back off progressively rather than hammering the API.
• Do not infinite-loop retries: cap the number of attempts and surface the failure to your application.

When you're limited

Treat a rate-limit response as a temporary failure: stop issuing requests, wait, and resume. Respect the guidance above so your integration stays well within normal usage.

Related