Rate Limits

How limits apply

Write-heavy endpoints are rate limited per organization on a rolling 60-second window. The ceiling depends on your plan, so read it from the response rather than hard-coding a number.

Currently rate limited: sending messages, creating broadcasts, triggering flows, managing sessions, and escalating a chat. Read endpoints are not limited today — do not rely on that staying true.

Headers

X-RateLimit-Limit:     100
X-RateLimit-Remaining: 42
X-RateLimit-Reset:     1788456000

X-RateLimit-Reset is a Unix timestamp in seconds, not milliseconds.

Handling 429

On 429, wait until the reset time before retrying. Retrying immediately consumes the next window and can keep you locked out indefinitely.

The limit is per organization, not per token, so issuing a second token does not buy more headroom — two integrations under one organization share the same budget. If you are pushing volume, batch where an endpoint supports it (broadcasts rather than a loop of individual sends) and spread work across the window rather than bursting at the top of the minute.