Account Rate Limits on Content API
Twilio is introducing standardized rate limits for Content API requests enforced at the account level, with varying limits per endpoint ranging from 20 to 100 requests per second. Applications must implement exponential backoff and handle HTTP 429 responses to comply with these new limits.
What is Changing?
To improve platform stability, endpoint reliability, and system performance, Twilio is introducing standardized rate limits for Content API requests.
Rate limits will be enforced at the account level. Requests exceeding these limits will receive an HTTP 429 Too Many Requests status code.
Rate Limits by Endpoint
Read Operations
Fetch Content (GET /v1/Content/{Sid}): 100 RPS
Fetch Approval (GET /v1/Approval/{Sid}): 100 RPS
List Content (v1 & v2) (GET /v1/Content): 20 RPS
List Content & Approvals (v1 & v2) (GET /v1/ContentAndApprovals): 20 RPS
List Legacy Content (GET /v1/LegacyContent): 20 RPS
Write Operations
Create Content (POST /v1/Content): 100 RPS
Create Content Approval Request (POST /v1/Approval): 100 RPS
Update Content (POST /v1/Content/{Sid}): 20 RPS
Delete Content (DELETE /v1/Content/{Sid}): 100 RPS
Update Content Approval Request (POST /v1/Approval/{Sid}): 20 RPS
What You Need to Do
Implement Exponential Backoff: Ensure your application can handle HTTP 429 status codes by incorporating backoffs and retries.
Audit High-Volume Pipelines: If your service executes bulk script operations (such as creating or deleting content templates in high-concurrency bursts), adjust your client throttling to remain within these thresholds.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
TaskRouter and Studio Public Beta in Ireland Region
TaskRouter and Studio are now available in public beta in Twilio's Ireland (IE1) region, providing EU data residency and control over where contact center routing and workflow automation data is stored.
Short Codes now supported in Data Residency for SMS (EU)
Short Code numbers can now be used as SMS senders in Twilio's Ireland region for EU data residency, with SMS message data stored and processed in the EU. The IE1 region now supports Short Code senders, Region Configuration API, Short Codes API, and Messaging Services API for short code management.
Segment Conversation Memory Integration now in GA
The Segment Conversation Memory Integration is now generally available, allowing real-time syncing of customer profile data from Segment into Conversation Memory for instant unified context access by AI and human agents during interactions. This eliminates cold starts and enables highly personalized customer experiences across channels.