DocsPlatform & Reliability
API Rate Limiting
API request limits, token bucket burst behavior, Retry-After headers, and how they differ from daily messaging quotas.
4 min read•API v1
API Rate Limits vs. Daily Messaging Quotas
* **API Request Rate Limits** (this section): Technical throughput limits preventing network congestion and server overload (measured in requests/second).
* **Plan Messaging Quotas** (separate): Daily business allowances of template messages per plan (e.g. Starter: 100/day, Growth: 500/day, Pro: 2000/day).
Throughput Tiers by Plan
| Plan | Messages / Second | Read Requests / Minute | Burst Capacity |
|---|---|---|---|
| Starter | 2 / sec | 60 / min | 10 tokens |
| Growth | 5 / sec | 180 / min | 25 tokens |
| Pro | 10 / sec | 600 / min | 50 tokens |
Rate Limit Response Headers
* `X-RateLimit-Limit`: Request capacity in current window.
* `X-RateLimit-Remaining`: Remaining requests available.
* `Retry-After`: Number of seconds your client must wait before retrying (sent on `HTTP 429`).