Twilio: Content API rate limits now return 429s, WhatsApp Embedded Signup moves to v4, and transcription failover switches on 22 October 2026

Twilio: Content API rate limits now return 429s, WhatsApp Embedded Signup moves to v4, and transcription failover switches on 22 October 2026

2 October 2026 — Twilio, the communications API provider, has posted three changes to its changelog that developers and contact-centre teams need to act on. Two were posted on 30 September 2026; the third takes effect on 22 October.

Not yet independently verified. This rests on Twilio’s own changelog; no independent report was found. The Content API post gives no separate start date, so we treat the limits as applying from its date, 30 September 2026. We will update this when it can be confirmed, and remove this note.

Content API: per-account rate limits

The Content API stores the message templates used for WhatsApp, RCS and other rich messages. Twilio now applies these limits per account:

• Fetch a template: 100 requests a second.
• List templates: 20 requests a second.
• Create and delete: 100 requests a second.
• Update: 20 requests a second.

Requests over a limit receive HTTP 429 Too Many Requests. Twilio recommends exponential backoff and an audit of high-volume pipelines. A nightly script that lists or updates thousands of templates in a tight loop is the kind of job that will now fail part-way through.

WhatsApp Embedded Signup version 4

Version 4 of Embedded Signup, the flow through which businesses connect their WhatsApp Business accounts to a Twilio-based product, became generally available on 30 September. Twilio says the move is required because WhatsApp is deprecating older versions; it gives no end date for them. Software vendors who onboard their own customers onto WhatsApp through Twilio should schedule the upgrade.

Real-Time Transcriptions: failover on by default from 22 October

From 22 October 2026, if Real-Time Transcriptions cannot connect to the primary speech provider, Twilio starts the session on a second provider. Failover is switched on for all existing accounts on that date, stays within the account's region, and can be turned off per sub-account in the Console. A new "Auto" mode, in which Twilio picks the provider per session, becomes the default for new customers only; existing configurations do not change unless a customer opts in.

What to do

• Add backoff and retry to any code that calls the Content API in bulk, and spread large template jobs out.
• Plan the Embedded Signup v4 upgrade before WhatsApp sets a cut-off.
• Decide on failover by 22 October: if your contracts or data-processing terms name a single speech provider, check whether a second one is allowed, and opt the affected sub-accounts out if it is not. Transcripts may also differ slightly between providers, which matters for analytics and compliance recording.

Sources

• Twilio changelog: Content API rate limits — 30 September 2026
• Twilio changelog: WhatsApp Embedded Signup v4 — 30 September 2026
• Twilio changelog: Provider failover and Auto mode provider selection for Real-Time Transcriptions — 22 September 2026