Quick answer
Twilio documents rest request concurrency as Account and endpoint dependent. Twilio reports 429 when concurrent request capacity is exceeded.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| REST request concurrencyTwilio reports 429 when concurrent request capacity is exceeded. | Account and endpoint dependent | Twilio REST APIs | TwilioAug 22, 2026 |
Why does this limit matter?
Parallel workers can overload concurrency even when average requests per second appear modest.
This value is scoped to Twilio REST APIs; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Track in-flight requests, response headers, status 429, and account/subaccount scope.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Messaging channel throughput and REST API concurrency are separate limiters.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related