api.telnyx.com endpoints. These limits are typically static, but are subject to change based on usage and may be adjusted to align with changes in capacity.
For this reason, we include headers in our API responses that should be parsed and respected by your application. These headers aim to help you understand your current consumption rate and self-diagnose or prevent potential throttling issues.
Rate Limit Headers
When the rate limit is exceeded, responses with status code 429 will be returned,
indicating that you have exhausted the number of requests allowed in the current
window.
Rate Limit Response
HTTP Status Code
The status code of rate limit responses is 429.Response Body
Handling Rate Limits
Best Practices
- Monitor Headers: Always check the rate limit headers in API responses
- Implement Backoff: Use exponential backoff when receiving 429 responses
- Cache Results: Cache API responses when possible to reduce request frequency
- Distribute Load: Spread requests across multiple time windows
Over Your Rate Limit?
Contact support@telnyx.com if you find you are exceeding the rate limit.Product-Specific Rate Limits
Different Telnyx services may have different rate limiting strategies:- Messaging: See Rate Limiting and Message Encoding for messaging-specific limits
- 10DLC: See 10DLC rate limits for campaign-specific limits
- Voice API: Standard API rate limits apply to call control endpoints
- Cloud Storage: Rate limits apply to S3-compatible operations