Limits
Requests per minute#
Each API key may make 60 requests per minute (a sliding one-minute window). Request 61 gets HTTP 429 with a Retry-After header in seconds:
{
"error": {
"code": "rate_limited",
"message": "Too many requests. Wait and try again."
}
}Each key has its own budget. Waiting for Retry-After and retrying is always safe.
Messages per month#
Each plan includes a number of messages per calendar month (UTC), counted from the 1st. Messages sent with POST /v1/messages and codes sent with POST /v1/otp/send both count; test messages sent from the dashboard don't. When the month's messages are used up, new messages are refused:
{
"error": {
"code": "limit_reached",
"message": "This workspace has used all messages included in its plan this month."
}
}Your plan, its limits and this month's usage are on the dashboard's Usage & billing page. A request repeated with the same requestId still returns the original message, even after the limit is reached.
OTP codes per number#
To protect your users, at most these codes go to the same number (across all purposes):
| Window | Codes |
|---|---|
| 60 seconds | 1 |
| 1 hour | 5 |
| 24 hours | 10 |
Over the limit you get HTTP 429 otp_rate_limited with Retry-After: the seconds until the next code is allowed.
SMS parts#
A long SMS is split into parts, and each part costs like one SMS on your SIM. The rules are the same as the phone's:
| Text | One part | Each part when split |
|---|---|---|
| Only GSM-7 characters (Latin letters, digits, common symbols) | 160 characters | 153 characters |
| Any other character (Arabic, emoji, …) | 70 characters | 67 characters |
One Arabic letter or emoji switches the whole message to Unicode. The characters ^ { } \ [ ] ~ | € count as two in GSM-7.
A message may have at most 6 parts (918 GSM-7 or 402 Unicode characters) and at most 2,000 characters. Longer texts are refused:
{
"error": {
"code": "text_too_long",
"message": "The message text is longer than 6 SMS parts."
}
}