Breakwatch

behavioralmedium85% confidence

Twilio is introducing standardized rate limits on the Content API at the account level, enforcing specific requests-per-second (RPS) thresholds per endpoint. Requests exceeding these limits will receive HTTP 429 Too Many Requests responses.

Migration: Implement exponential backoff and retry logic to handle HTTP 429 responses, and audit any high-volume pipelines (e.g., bulk content template creation/deletion) to ensure they stay within the new per-endpoint RPS limits.

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}

10/9/2026

behavioralmedium88% confidence

Twilio is introducing standardized account-level rate limits on the Content API, with specific RPS limits per endpoint. Requests exceeding these limits will receive HTTP 429 responses.

Migration: Implement exponential backoff with retry logic to handle HTTP 429 responses, and audit high-volume pipelines (e.g., bulk content template creation/deletion) to ensure they stay within the new per-endpoint RPS thresholds.

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}

10/7/2026

behavioralhigh92% confidence

Twilio is introducing standardized rate limits on the Content API at the account level, enforcing HTTP 429 responses when exceeded. Additionally, the Conference list endpoint will change its default behavior on September 30, 2026 to return only in-progress conferences instead of all conferences.

Migration: Implement exponential backoff and retry logic to handle HTTP 429 responses from Content API. For the Conference list endpoint, explicitly pass a status filter if you need conferences in states other than 'in-progress' before the September 30, 2026 deadline.

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.json

10/6/2026

Effective: 9/30/2026

behavioralmedium82% confidence

Twilio is introducing multiple platform changes including: rate limits on the Content API (HTTP 429 enforcement), a default filter change on the Conference list endpoint to return only in-progress conferences starting September 30 2026, and automatic provider failover for Real-Time Transcriptions starting October 22 2026. Several new GA and Beta features are also being released.

Migration: Implement exponential backoff to handle HTTP 429 responses from the Content API; audit code that calls GET /Conferences.json without a Status filter to avoid missing non-in-progress conferences after Sep 30 2026; review Real-Time Transcriptions failover behavior and opt out per sub-account in Console if needed.

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.jsonendpoint:Real-Time Transcriptions

10/6/2026

Effective: 9/30/2026

behavioralmedium82% confidence

Twilio is introducing multiple platform changes including: rate limits on the Content API (HTTP 429 enforcement), a default filter change on the Conference list endpoint to return only in-progress conferences starting September 30 2026, and automatic Provider Failover for Real-Time Transcriptions starting October 22 2026. Several new GA and Beta features are also being released.

Migration: 1) Implement exponential backoff/retry logic for HTTP 429 responses on Content API endpoints. 2) Update any code relying on the Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) to explicitly filter by status if you need non-in-progress conferences. 3) Review Real-Time Transcriptions sub-account settings in Console if you wish to opt out of automatic provider failover.

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.json

10/3/2026

Effective: 9/30/2026

behavioralhigh88% confidence

Twilio is introducing multiple significant API changes: (1) Content API rate limits enforced at account level with HTTP 429 responses, (2) Conference list endpoint will default to in-progress conferences only starting September 30 2026, (3) Verify Event Streams 'Attempt DLR' event type discontinued after September 22 2026, and (4) Real-Time Transcriptions provider failover enabled automatically on October 22 2026.

Migration: Implement exponential backoff for HTTP 429 on Content API; update Conference list queries to explicitly filter by status if needed; remove subscriptions to Verify 'Attempt DLR' event type; optionally opt out of transcription provider failover per sub-account in Console if not desired.

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 failover

10/2/2026

Effective: 9/22/2026

breakinghigh90% confidence

The Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will change its default filter to return only in-progress conferences starting September 30, 2026. Additionally, the Verify Event Streams 'Attempt DLR' event type is being discontinued after September 22, 2026.

Migration: For the Conference list endpoint, explicitly pass the Status parameter if you need conferences in other states (e.g., Status=completed). For Verify Event Streams, remove any subscriptions or handlers relying on the 'Attempt DLR' event type and migrate to supported event types.

endpoint:GET /2010-04-01/Accounts/{AccountSid}/Conferences.jsonparam:Status (Conferences list default behavior)model:Verify Event Streams - Attempt DLR event type

10/1/2026

Effective: 9/30/2026

breakinghigh92% confidence

Starting September 30, 2026, the Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will change its default behavior to return only in-progress conferences instead of all conferences. Additionally, the Verify Event Streams 'Attempt DLR' event type is being discontinued after September 22, 2026.

Migration: For the Conference list endpoint, explicitly pass a 'Status' filter parameter if you need conferences in states other than 'in-progress'. For Verify Event Streams, remove any subscriptions to the 'Attempt DLR' event type and migrate to alternative event types before September 22, 2026.

endpoint:GET /2010-04-01/Accounts/{AccountSid}/Conferences.jsonparam:Status (Conference list default filter)model:Verify Event Streams - Attempt DLR event type

10/1/2026

Effective: 9/30/2026

breakinghigh92% confidence

Starting September 30, 2026, the Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will change its default behavior to return only in-progress conferences instead of all conferences. Additionally, the Verify Event Streams 'Attempt DLR' event type is being discontinued effective September 22, 2026.

Migration: For the Conference list endpoint, explicitly pass a status filter parameter if you need to retrieve conferences in states other than 'in-progress'. For Verify Event Streams, remove any subscriptions to the 'Attempt DLR' event type and migrate to supported event types before September 22, 2026.

endpoint:GET /2010-04-01/Accounts/{AccountSid}/Conferences.jsonparam:status (default behavior change on Conferences list)model:Verify Event Streams - Attempt DLR event type

9/30/2026

Effective: 9/30/2026

breakinghigh92% confidence

Starting September 30, 2026, the Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will change its default behavior to return only in-progress conferences instead of all conferences. Additionally, the Verify Event Streams 'Attempt DLR' event type is being discontinued after September 22, 2026.

Migration: For the Conference list endpoint, explicitly pass a Status filter parameter if you need conferences in states other than 'in-progress'. For Verify Event Streams, remove any subscriptions to the 'Attempt DLR' event type and update downstream logic that depends on it.

endpoint:GET /2010-04-01/Accounts/{AccountSid}/Conferences.jsonparam:Status (Conference list default filter)model:Verify Event Streams - Attempt DLR event type

9/30/2026

Effective: 9/30/2026

breakinghigh92% confidence

Starting September 30, 2026, the Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will change its default behavior to return only in-progress conferences instead of all conferences. Additionally, the Verify Event Streams 'Attempt DLR' event type is being discontinued after September 22, 2026.

Migration: For the Conference list endpoint, explicitly pass a status filter parameter if you need conferences in states other than 'in-progress'. For Verify Event Streams, remove any subscriptions to the 'Attempt DLR' event type and update downstream consumers accordingly.

endpoint:GET /2010-04-01/Accounts/{AccountSid}/Conferences.jsonparam:Conferences.status (default behavior change)model:Verify Event Streams - Attempt DLR event type

9/26/2026

Effective: 9/30/2026

behavioralhigh85% confidence

Starting September 30, 2026, the Voice API Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will change its default behavior to return only in-progress conferences instead of all conferences. Additionally, the Verify 'Attempt DLR' Event Streams event type will be discontinued after September 22, 2026.

Migration: For the Conference list endpoint, explicitly pass a Status filter parameter if you need conferences in states other than 'in-progress'. For Verify Event Streams, remove any subscriptions to the 'Attempt DLR' event type and update integrations that depend on it.

endpoint:GET /2010-04-01/Accounts/{AccountSid}/Conferences.jsonparam:Status (Conference list default filter)model:Verify Attempt DLR Event Type

9/25/2026

Effective: 9/30/2026

new_featuremedium72% confidence

Multiple Twilio changelog updates detected, with the most impactful being: (1) Java Helper Library 13.0.0 critical fix for unknown field deserialization crashes in nested API responses, (2) new Webhook Configuration API in Public Beta supporting OAuth 2.0 and Shared Key auth, and (3) SendGrid Link Branding gaining a new `auto_ssl` parameter for automatic SSL certificate provisioning.

Migration: Java SDK users on versions 10.0.0–12.1.1 should upgrade to 13.0.0 immediately following the upgrade guide to avoid latent deserialization failures. SendGrid users creating branded links can opt in to `auto_ssl: true` to prepare for Gmail's HTTPS enforcement rolling out by end of October 2026.

model:Java Helper Library (twilio-java) v13.0.0endpoint:Webhook Configuration API - Webhook Settingsendpoint:Webhook Configuration API - Webhook Rulesparam:auto_ssl (Link Branding API)param:auto_ssl_available (Link Branding API)endpoint:Real-Time Transcriptions - Provider Failoverendpoint:Voice API - Say (ElevenLabs voices)endpoint:Verify Custom Templates

9/23/2026

Effective: 9/2/2026

new_featuremedium72% confidence

Several Twilio platform updates are present: a new Webhook Configuration API (Public Beta) supporting OAuth 2.0 and Shared Key auth; a new `auto_ssl` parameter added to the SendGrid Link Branding API; ElevenLabs Voices for Say moving to Public Beta; Verify Custom Templates reaching GA; a critical fix in Java Helper Library 13.0.0 for unknown field deserialization; and behavioral changes including Verify Geo Permission defaults tightening for Italy and Argentina, and messaging rate limits during a Heightened Awareness Period.

Migration: Java Helper Library users on versions 10.0.0–12.1.1 should upgrade to 13.0.0 immediately following the upgrade guide to avoid deserialization crashes. SendGrid users adding link branding should consider the new `auto_ssl` parameter before Gmail enforces HTTPS warnings in October 2026. Verify users with Italy or Argentina geo permissions should verify Fraud Guard is enabled to maintain fraud protection.

endpoint:Webhook Configuration APIparam:auto_sslmodel:auto_ssl_availablemodel:Java Helper Library 13.0.0endpoint:Verify Geo Permissionsendpoint:Say (ElevenLabs voices)endpoint:Verify Custom Templates

9/22/2026

Effective: 9/17/2026

breakinghigh82% confidence

The Java Helper Library versions 10.0.0–12.1.1 have a latent breaking defect where unknown fields in nested API responses cause a crash (ApiConnectionException). Version 13.0.0 fixes this by ignoring unknown fields, but itself introduces breaking changes requiring a migration guide. Additionally, Twilio Functions Classic is being deprecated and will be automatically migrated starting September 13, 2026.

Migration: Upgrade the Java Helper Library to 13.0.0 following the official upgrade guide as soon as possible. For Functions Classic, review the migration guide before September 13, 2026; no action is required for the automatic migration but custom code should be validated against the new Functions environment.

model:Java Helper Library (versions 10.0.0–12.1.1 nested response deserialization)endpoint:Functions Classicparam:auto_ssl (SendGrid Link Branding API)param:auto_ssl_available (SendGrid Link Branding API)

9/18/2026

Effective: 9/13/2026

new_featureinfo72% confidence

Twilio's changelog page contains multiple updates including new features (ElevenLabs TTS voices in Public Beta, Webhook Configuration API in Public Beta, Verify Custom Templates GA, Bulk Messaging WhatsApp Content Templates Beta, Consent Management API Toll-Free opt-out overrides GA), a critical Java Helper Library fix (v13.0.0), a Functions Classic deprecation, behavioral changes to Verify Geo Permissions for Italy and Argentina, and a SendGrid Link Branding SSL update with a new `auto_ssl` API parameter.

Migration: If using the Java Helper Library versions 10.0.0–12.1.1, upgrade to 13.0.0 immediately following the upgrade guide to avoid deserialization crashes. If using Functions Classic, plan migration before September 13, 2026. If using SendGrid Link Branding, consider enabling `auto_ssl` before Gmail begins flagging non-HTTPS links in October 2026.

model:Java Helper Library (twilio-java) v10.0.0–12.1.1endpoint:Webhook Configuration APIparam:auto_ssl (SendGrid Link Branding API)model:auto_ssl_available (SendGrid Link Branding API)endpoint:Bulk Messaging APIendpoint:Consent Management APIendpoint:Verify Geo Permissionsendpoint:Functions Classicendpoint:Voice API <Say> (ElevenLabs voices)endpoint:Verify Custom Templates

9/17/2026

breakinghigh92% confidence

Java Helper Library 13.0.0 fixes a latent breaking bug where versions 10.0.0–12.1.1 crash with ApiConnectionException when API responses contain unknown fields in nested objects. Version 13.0.0 itself includes additional breaking changes requiring migration.

Migration: Upgrade to Java Helper Library 13.0.0 as soon as possible, following the official upgrade guide to handle the breaking changes introduced in v13.

model:Java Helper Library (versions 10.0.0–12.1.1) nested response deserialization

9/16/2026

Effective: 9/2/2026

new_featureinfo72% confidence

Multiple Twilio platform updates including new Public Beta features (ElevenLabs voices for TwiML Say, Webhook Configuration API), GA releases (Verify Custom Templates, Consent Management API Toll-Free opt-out overrides), a new Link Branding auto_ssl parameter, Bulk Messaging WhatsApp Content Templates, and a critical Java Helper Library 13.0.0 fix for unknown field deserialization crashes.

Migration: Java Helper Library users on versions 10.0.0–12.1.1 should upgrade to 13.0.0 immediately following the upgrade guide, as unknown API response fields can cause ApiConnectionException crashes. SendGrid users should add DNS records and set auto_ssl=true on new branded links before Gmail's October 2026 HTTPS enforcement. Functions Classic users should plan migration before September 13, 2026.

endpoint:Voice API /Say (ElevenLabs voices)endpoint:Webhook Configuration APIendpoint:Link Branding APIparam:auto_sslendpoint:Bulk Messaging APIendpoint:Consent Management APImodel:Java Helper Library nested response deserializationendpoint:Functions Classic

9/15/2026

Effective: 8/13/2026

breakinghigh95% confidence

Starting September 15, 2026, the `privacy_policy_url` and `terms_and_conditions_url` fields will be required on all new Toll-Free verification submissions; submissions missing either field will be rejected. Existing verified numbers are unaffected.

Migration: Ensure all new Toll-Free verification API submissions include both `privacy_policy_url` and `terms_and_conditions_url` fields before September 15, 2026.

param:privacy_policy_urlparam:terms_and_conditions_urlendpoint:Toll-Free Verification submission

9/12/2026

Effective: 9/15/2026

new_featureinfo60% confidence

Twilio's changelog page contains multiple updates including: ElevenLabs voices in Public Beta for TwiML <Say>, a new Webhook Configuration API in Public Beta supporting OAuth 2.0 and Shared Key auth, a new Link Branding auto_ssl parameter in SendGrid, Bulk Messaging support for WhatsApp Content Templates, Consent Management API support for Toll-Free opt-out overrides, Verify Custom Templates GA, and a critical Java Helper Library 13.0.0 fix for unknown field deserialization crashes.

Migration: Java Helper Library users on versions 10.0.0–12.1.1 should upgrade to 13.0.0 immediately following the upgrade guide. Functions Classic users should prepare for automatic migration starting September 13, 2026. SendGrid users should evaluate adding auto_ssl to link branding before Gmail's October 2026 HTTPS enforcement.

endpoint:Voice API TwiML <Say>endpoint:Webhook Configuration APIparam:auto_ssl (Link Branding API)model:auto_ssl_available (Link Branding API)endpoint:Bulk Messaging APIendpoint:Consent Management APImodel:Java Helper Library nested response deserializationendpoint:Functions Classic

9/11/2026

Effective: 8/12/2026

breakinghigh92% confidence

The Java Helper Library v13.0.0 fixes a critical deserialization crash on unknown fields in nested API responses. Versions 10.0.0–12.1.1 will fail with ApiConnectionException when Twilio adds any new optional field to nested response objects, making existing integrations latently broken.

Migration: Upgrade to Java Helper Library 13.0.0 as soon as possible and follow the provided upgrade guide, as v13 includes its own breaking changes requiring a migration.

model:Java Helper Library nested response deserialization (profile, configuration, webhook)

9/10/2026

Effective: 9/2/2026

new_featuremedium72% confidence

Multiple Twilio platform updates including: Java Helper Library 13.0.0 critical fix for unknown field deserialization crashes, new auto_ssl parameter for SendGrid Link Branding API, Consent Management API support for Toll-Free network-level opt-out overrides, Functions Classic deprecation with migration to new Functions, and several other behavioral/feature changes.

Migration: Upgrade Java Helper Library to 13.0.0 following the upgrade guide to fix latent deserialization crashes; Functions Classic users should prepare for automatic migration starting September 13, 2026; SendGrid link branding users should evaluate enabling auto_ssl=true before Gmail's October 2026 HTTPS enforcement.

model:Java Helper Library (versions 10.0.0–12.1.1)param:auto_ssl (SendGrid Link Branding API)model:auto_ssl_available (SendGrid Link Branding API)endpoint:Consent Management API (Toll-Free opt-out override)endpoint:Bulk Messaging API (WhatsApp Content Templates)endpoint:Functions Classicendpoint:REST API TLS certificate (all endpoints)endpoint:Verify Geo Permissions (Italy, Argentina)

9/8/2026

Effective: 8/12/2026

new_featureinfo45% confidence

This diff is primarily website navigation/chrome with multiple changelog entries mixed in, covering a Java Helper Library critical fix, new SendGrid Link Branding auto_ssl parameter, Functions Classic deprecation, Consent Management API enhancements, TLS certificate rotation, Verify Custom Templates GA, and new error codes. The most actionable API-impacting change is the addition of the `auto_ssl` and `auto_ssl_available` fields to the Link Branding API, alongside a critical Java Helper Library fix for unknown field deserialization.

Migration: Java Helper Library users on versions 10.0.0–12.1.1 should upgrade to 13.0.0 immediately following the upgrade guide. SendGrid Link Branding API consumers can optionally set `auto_ssl: true` on link creation to enable automatic SSL provisioning.

param:auto_sslparam:auto_ssl_availablemodel:Java Helper Library (versions 10.0.0–12.1.1)endpoint:Link Branding APIendpoint:Consent Management APIendpoint:Bulk Messaging APIendpoint:Functions Classic

9/5/2026

behavioralmedium72% confidence

This diff contains multiple Twilio changelog entries including: a behavioral change to Verify Geo Permissions for Italy and Argentina (defaulting to 'Monitor all traffic for fraud' on Aug 19, 2026), deprecation of Functions Classic (new creation blocked Sep 13, migration Oct 2026), TLS certificate rotation for all REST API endpoints on Sep 9 2026, new Bulk Messaging WhatsApp Content Template support, Consent Management API Toll-Free opt-out override GA, new Event Streams regional IP for US East, SendGrid Domain Authentication 'Send to Coworker' action removal, new error codes for TFV/A2P 10DLC, Voice JS SDK noise cancellation components, and Twilio Email Dedicated IPs GA. The most impactful operational changes are the TLS certificate rotation and Functions Classic deprecation.

Migration: 1) Test TLS connectivity at https://tls-test.twilio.com before Sep 9, 2026; avoid certificate pinning. 2) Migrate Functions Classic to new Functions before Oct 26, 2026. 3) Review Verify Geo Permissions for Italy/Argentina if you rely on unrestricted SMS traffic. 4) Update IP allowlists for Event Streams webhooks in US East before Sep 15, 2026.

endpoint:Twilio REST API (TLS certificate rotation)endpoint:Verify Geo Permissions (Italy/Argentina)endpoint:Functions Classicendpoint:Bulk Messaging APIendpoint:Consent Management APIendpoint:Event Streams Webhooks (US East)endpoint:SendGrid Domain Authenticationmodel:Verify Geo Permissions default state

8/27/2026

Effective: 8/19/2026

behavioralmedium82% confidence

Twilio Verify is automatically updating the default Geo Permissions for Italy (IT) and Argentina (AR) from 'Allow all traffic' to 'Monitor all traffic for fraud' effective August 19, 2026, for all accounts still on the default setting. This is in response to a surge in SMS Pumping fraud targeting those countries.

Migration: No action required if Fraud Guard is already enabled. Review your Verify Geo Permissions in the Twilio Console for IT and AR; note that reverting to 'Allow all traffic' makes your account liable for fraudulent traffic charges.

param:Verify Geo Permissions (Italy / IT)param:Verify Geo Permissions (Argentina / AR)

8/27/2026

Effective: 8/19/2026

behavioralmedium72% confidence

Twilio's changelog page contains multiple updates including a TLS certificate rotation on September 9, 2026 (affecting certificate-pinning customers), a Functions/Assets API timestamp bug fix on September 1, 2026 (date_created/date_updated returning incorrect UTC values shifted by +7 hours), a new Event Streams regional IP address on September 15, 2026, removal of the SendGrid 'Send to Coworker' domain authentication action, and several new features (Dedicated IPs for Email, Voice JS SDK noise cancellation, US Branded Calling GA, WhatsApp Card/Flows in Conversations API, Restricted API Key permissions for Conversations).

Migration: Review date_created/date_updated handling in Functions/Assets integrations before September 1, 2026; update IP allowlists for Event Streams webhooks by September 15, 2026; test TLS certificate rotation at https://tls-test.twilio.com; avoid certificate pinning against Twilio REST API endpoints.

endpoint:Twilio REST API (TLS certificate rotation)model:Functions and Assets date_created / date_updatedendpoint:Event Streams Webhooks (US East)endpoint:SendGrid Domain Authentication (Send to Coworker removed)endpoint:Conversations API (whatsapp/card, whatsapp/flows)endpoint:Conversations API (Restricted API Keys permissions)endpoint:Voice JS SDK (noise cancellation)endpoint:Twilio Email (Dedicated IPs)endpoint:Branded Calling (US GA)

8/13/2026

Effective: 8/3/2026

behavioralmedium72% confidence

Multiple Twilio platform changes are announced, including: a new regional IP address for Event Streams webhooks in US East (effective September 15, 2026), a bug fix correcting UTC timestamp offsets on Functions/Assets API (effective September 1, 2026), an RCS error code change from 30036 to 30046 for undelivered messages (effective August 10, 2026), removal of the SendGrid 'Send to Coworker' domain authentication action, new WhatsApp Card & Flows support in Conversations API, Restricted API Key permissions for Conversations, GA of Enhanced Branded Calling, real-time WhatsApp template approval events via Event Streams, Lookup Line Status public beta, and expanded error code 30915 scope.

Migration: Review the following before their effective dates: (1) Add 3.80.20.0/25 to IP allowlists for Event Streams webhooks by Sept 15, 2026; (2) Audit any logic depending on Functions/Assets date_created or date_updated timestamps before Sept 1, 2026; (3) Update RCS error handling to use code 30046 instead of 30036 before Aug 10, 2026.

endpoint:Event Streams Webhooks (US East)model:Functions and Assets date_created / date_updatedmodel:RCS error code 30036 → 30046endpoint:SendGrid Domain Authentication (Send to Coworker action)endpoint:Conversations API (whatsapp/card, whatsapp/flows)model:Restricted API Keys Conversations permissionsendpoint:Event Streams com.twilio.messaging.template.approval.updatedendpoint:Lookup Line Statusmodel:Error code 30915 (A2P 10DLC + Toll-Free)

8/8/2026

Effective: 8/10/2026

breakinghigh92% confidence

Starting August 10, 2026, the RCS error code for unconfirmed message delivery will change from 30036 to 30046. Developers relying on error code 30036 for RCS delivery failure handling will receive 30046 instead, requiring updates to error-handling logic.

Migration: Update any error-handling code that checks for error code 30036 on RCS messages to also handle or replace with 30046 before August 10, 2026.

model:error_code:30036model:error_code:30046

8/4/2026

Effective: 8/10/2026

behavioralhigh88% confidence

On September 1, 2026, the `date_created` and `date_updated` fields on Functions and Assets API resources will be corrected to return accurate UTC timestamps, fixing a bug introduced in 2023 that shifted values forward by 7 hours (PST offset) despite the UTC 'Z' suffix. The correction applies retroactively to all resources.

Migration: Review any integration logic that uses `date_created` or `date_updated` for sorting, filtering, time-range comparisons, or audit purposes before September 1, 2026. Existing timestamps will shift back by ~7 hours once the fix is applied.

model:Function.date_createdmodel:Function.date_updatedmodel:Asset.date_createdmodel:Asset.date_updated

8/3/2026

Effective: 9/1/2026

behavioralhigh92% confidence

On September 1, 2026, the `date_created` and `date_updated` fields on Functions and Assets API resources will be corrected to return accurate UTC timestamps, fixing a bug where values were shifted forward by 7 hours (PST offset) despite the UTC 'Z' suffix. The correction applies retroactively to all resources.

Migration: Review any integration logic that uses `date_created` or `date_updated` for sorting, filtering, time-range comparisons, or audit purposes before September 1, 2026, and adjust for the corrected UTC values (subtract ~7 hours from current returned values).

param:date_createdparam:date_updatedendpoint:Functions and Assets API

8/3/2026

Effective: 9/1/2026

Twilio

Change History

Get alerts when Twilio changes affect your code