API requests are rate limited per team, per minute. If you need a higher limit, contact support.
The limit is shared across the v2 and v3 API endpoints and the MCP server, so requests from all of them count towards the same total.
Exceeding the limit
Requests over the limit get 429 Too Many Requests. Responses carry headers showing where you stand:
| Header | Meaning |
|---|---|
X-RateLimit-Limit |
Requests allowed per minute. |
X-RateLimit-Remaining |
Requests left in the current window. |
Retry-After |
On a 429, seconds to wait before retrying. |
Staying under the limit
- Batch sends. One Send SMS request can carry up to 1000 messages, so you rarely need more than a few requests per minute to send.
- Use webhooks instead of polling. Webhooks deliver replies and delivery receipts as they happen, so you don’t need to poll List inbound messages.
- Back off on
429. Wait forRetry-Afterbefore retrying, rather than retrying straight away.