Twilio APIBehavior changehigh
Twilio adds Content API rate limits and drops Verify DLR events Sep 22
- Detected
- Oct 2, 2026
- Effective
- Sep 22, 2026
- Confidence
- 82%
What changed
Twilio is introducing multiple significant API changes including: rate limits on Content API endpoints (effective immediately upon rollout), a default filter change on the Conference list endpoint to return only in-progress conferences (September 30, 2026), discontinuation of the Verify Attempt DLR event type (after September 22, 2026), and Provider Failover being auto-enabled for Real-Time Transcriptions (October 22, 2026).
What to do
1) Implement exponential backoff/retry for HTTP 429 on Content API calls. 2) Update any Conference list queries that rely on non-in-progress conferences to explicitly pass a status filter before Sept 30, 2026. 3) Remove subscriptions to Verify Attempt DLR event type. 4) Review Real-Time Transcription configs if failover behavior is undesired—opt out per sub-account in Console before Oct 22, 2026.
Affected
endpoint: GET /v1/Content/{Sid}endpoint: GET /v1/Approval/{Sid}endpoint: GET /v1/Contentendpoint: GET /v1/ContentAndApprovalsendpoint: GET /v1/LegacyContentendpoint: POST /v1/Contentendpoint: POST /v1/Approvalendpoint: POST /v1/Content/{Sid}endpoint: DELETE /v1/Content/{Sid}endpoint: POST /v1/Approval/{Sid}endpoint: GET /2010-04-01/Accounts/{AccountSid}/Conferences.jsonmodel: Verify Attempt DLR event typeparam: Real-Time Transcriptions provider failoverSource: twilio.com (Twilio's own page, checked by Breakwatch)
Is your code affected?
Search your repositories for the Twilio SDK and the names above:
Or let Breakwatch do it: connect a repo and see which files call Twilio, then get the next change as an alert pointing at those files. Check a repo free