Twilio Changelog

We’ve made an important update to A2P 10DLC Phone Number Registration events in Twilio Event Streams — now including the Messaging Service SID in all related events.

With this enhancement, you can directly identify which A2P Campaign a phone number is associated with by referencing the messaging_service_sid field in the 2.0 schema version. This improves traceability and helps streamline debugging, monitoring, and automation workflows tied to number registration.

The following Event Streams now include the messaging_service_sid field:
- com.twilio.messaging.compliance.number-deregistration.pending
- com.twilio.messaging.compliance.number-deregistration.successful
- com.twilio.messaging.compliance.number-registration.pending
- com.twilio.messaging.compliance.number-registration.successful

To learn more about A2P Notifications through Event Streams , check out our guide docs.

Requests made to the Recording Transcription resource for .csv and .html response formats will return an HTTP 404 error.

You can now select permissions for Usage Records and Event Streams API while creating a Restricted API Key. The product already supports permissions for Messaging, Phone Numbers, Studio, Voice, Task Router, Monitor, Lookup and Verify APIs.

Restricted API Keys allow you to decide which Twilio API Resources an API Key can access, and which action(s) the API Key is allowed to take on those API Resources.

We’ve made a key improvement to Authentication+ to support programmatically triggering a new 2FA verification email for A2P 10DLC Brand registrations that have failed. 

Alongside the endpoint, we’re introducing a set of dedicated 2FA error codes that surface precise failure reasons and point you to the fastest remedy, so your users can complete brand verification with fewer support tickets and less manual work.

To learn more about Authentication+, check out our Support Article and Twilio API Docs.
 

Twilio will now support RCS Title and description text in twilio/card. We will support backwards compatability to ensure no existing templates fail to deliver based on channel limitations. 

No changes will occur in WA translations. 

• Twilio supports RCS title via the title field in twilio/card
  • Up to 200 characters for RCS title
  • Twilio will translate twilio/card title to description if twilio/card title is greater than 200 characters
• Twilio supports RCS description with the body field in twilio/card
  • twilio/card subtitle will also be appended onto the body to form RCS description

Voice Recording Storage billing behavior is changing to improve accuracy and will provide daily usage metrics.

Real-Time Transcriptions are now available in Public Beta, allowing you to access the transcribed text from participants in your Video Group Rooms and provide on-screen captions for accessibility. You can opt in to transcriptions on a per-Room basis via the REST API or enable it by default on all Rooms via the Twilio Console configuration.   

Real-Time Transcriptions leverages the scale and programmability of the Twilio Communications Platform. You can choose supported languages and speech models, and control when transcriptions start or stop in each Group Room. The feature is available in the latest JavaScript, iOS, and Android SDKs.

To start using Real-Time Transcriptions, upgrade your Video Client SDK and review the detailed setup instructions in our developer documentation.

With Enhanced RBAC we are introducing more granular roles called built-in roles, which provide access to specific Twilio products including Messaging, Studio, Phone Numbers etc. You can find the complete list of new roles here.

We can assign these roles at organization, account or subaccount level unlike the current general roles which can be assigned only at the account level.

Studio now supports the ability to shorten links within your message body when using the Send Message and Send & Wait For Reply widgets. You can also shorten links to track customer engagement with click events.