Account Rate Limits on Content API

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.