Rate limits
How many requests an API key can make.
Each API key can make up to 600 requests a minute. The count starts again at the start of each minute.
Every answer says where you stand:
| Header | Value |
|---|---|
X-RateLimit-Limit | Requests allowed each minute: 600 |
X-RateLimit-Remaining | Requests left this minute |
X-RateLimit-Reset | Seconds until the count starts again |
The same is also given in the IETF's standard fields, which some HTTP clients read on their own:
RateLimit-Policy: "default";q=600;w=60
RateLimit: "default";r=598;t=42r is what's left and t the seconds until the count starts again.
Past the limit, a request answers 429 with the code rate_limited, and a Retry-After header with the number
of seconds to wait. Wait that long, then try again.
The token endpoint, POST /v1/oauth/token, has no API key yet, so it counts by address instead: 60 requests a
minute from each.
Stay under the limit
- Send in bulk. Use import to add many customers in one request, and a broadcast to send the same message to up to 10,000 numbers.
- Use webhooks instead of checking. Rather than asking whether each message was delivered, let webhooks tell you.
- Ask for bigger pages. Lists take a
limitof up to 200. - One key per system. Each API key has its own limit, so give each system its own.
Last updated