Rate limits
Three sliding windows per short code: hourly, daily, and monthly. All three run simultaneously.
How the windows work
Each window is a sliding count. The hourly window counts requests in the last 60 minutes; the daily window counts the last 24 hours; the monthly window counts the last 30 days. Hitting any one of the three limits blocks further requests until that window clears.
Your key mode limits
Limits are set by your subscription tier. PAYG-only (no active subscription, PAYG enabled) runs at the lowest level: 10/hour, 50/day, 30/month.
| Tier | Hourly | Daily | Monthly |
|---|---|---|---|
| Basic | 100 | 2,000 | 10,000 |
| Pro | 500 | 10,000 | 100,000 |
| PAYG only | 10 | 50 | 30 |
Hosted mode limits
Hosted mode runs at Pro-equivalent limits: 500 req/h, 10,000 req/d, 100,000 req/mo. There is no subscription quota — only the rate-limit windows apply.
What a 429 means
A 429 (rate limit exceeded) response means one of your three windows is full. The response includes a Retry-After header indicating when the blocking window clears. Your client may surface this as a generic error — check the response body for the reAPI error message.
Common questions
When does my monthly quota reset?
The monthly window is a rolling 30-day count, not a calendar-month reset. It clears 30 days after the oldest request in the window.
What does the 429 error message say?
The response body includes a JSON error with a message field describing which window was hit (hourly, daily, or monthly) and a link to your dashboard.
Can I see my current usage?
The Overview page shows your current-period request-unit usage against your quota. Detailed per-request logs are on the Activity page.