Twilio Changelog

A2P 10DLC brand and campaign registration for all 501(c) nonprofit organizations is now available as part of Twilio’s A2P 10DLC Console and ISV API onboarding experience.Nonprofit organizations can register using the Charity / 501(c)(3), Political, or Standard use cases depending on their entity type:

• 501(c)(3) organizations should register campaigns with the Charity / 501(c)(3) special use case. Charity / 501(c)(3) is a reserved use case for 501(c)(3)s to receive discounts on A2P carrier fees.
• 501(c)(4), 501(c)(5), and 501(c)(6) organizations sending messages that are political in nature should register with the Political special use case, or register non-political messaging with standard campaign use cases. The Political use case receives increased messaging throughput on A2P.
• All other 501(c) designations should register their campaigns with standard campaign use cases.

For more details on the Charity / 501(c)(3) and Political campaign use cases, please see this support article on special use cases.

Note: We're still working to enable registration for 527 Political organizations and for the Emergency Special use case.

This release features the creation of the Elastic SIP Trunking Pricing API. Use this API to query a list of countries with pricing available and the origination and termination trunking prices for a particular country with the Trunking Country subresource. Additionally, query for phone number prices for a particular country, or the price for originating from a particular Twilio phone number to any destination number with the Trunking Number subresource. Prices returned will be specific to your account.

On November 1, 2021, Twilio will discontinue support for the 2008 Calls API. Customers who are still using this interface after it’s been discontinued may receive error responses. This change was previously communicated via email to customers with 2008 API usage on December 7, 2020 and April 24, 2021.

Please follow these migration guidelines to update your code from the 2008 API to the 2010 API.

Messaging Customers are required by U.S. carriers to register for A2P 10DLC. Independent Software Vendors that offer other customers the ability send SMS and MMS need to register themselves as an ISV brand via Trust Hub in the Twilio console and then they can register each customer as a Standard Brand or a Starter Brand. Registered Brands can then register use case campaigns.

Starter Brand registration is now available for all independent software vendor (ISV) customers to register your customers for US 10DLC compliance and send SMS and MMS in the US with 10-digit long codes. Starter Brand registration is intended for customers who send fewer than 3,000 daily SMS segments and MMS messages over 10-digit long codes AND use five or fewer 10-digit U.S. long codes. Twilio is covering the costs for Starter Brand registration and monthly campaign fees.

ISV Customers can read the Starter Brand overview and step-by-step API walkthrough as they prepare to register their customers.

Version 2 of the Twilio SendGrid Segmentation API is now in Public Beta. Based on Structured Query Language (SQL), this API unlocks new segmentation use cases such as segmentation on multiple engagement events and segmentation on NOT events.

See the Segmentation v2 API documentation for examples of what's possible with this new API.

Voice Insights Call Events and Call Metrics are now available on Event Streams, in addition to Call Summary which was already available. Developers can now subscribe to these Voice Insights events and have them delivered to their preferred destination through Event Streams.

We have updated all Flex projects that use Automatic Updates to Flex UI 1.27.

This release of Flex UI includes a public beta for Real-Time Queue Monitoring. This feature displays real-time metrics that are useful for managing queues during the day. We have added new default metrics - number of handled customers, number of abandoned customers, and SLA. The SLA shows the percentage of waiting customers that were connected to an agent within a desired target time. Developers can programmatically add additional metrics to extend this dashboard.

Real-Time Queue Monitoring can be enabled from the Flex Features page.

For more information check our documentation. Check how to enhance and customize queues monitoring programmatically.

For more details on this release, please visit the release notes for Flex UI.

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.

It is now possible to do a single participant lookup in the Conversations API. With this feature, you can now easily list all Conversations for a specific participant. The lookup is performed using the participant identifier: identity for a chat participant and address for SMS and WhatsApp participants.

Explore the lookup documentation and give it a try!

Starting 31 August 2021 Twilio will begin to escape & and = in query parameters provided in RecordingStatusCallback values for the creation of Calls and Conference Participants.

Today, a bug in RecordingStatusCallback encoding/decoding results in Twilio dropping everything after & in query parameter strings for the provided URL.

Some customers have identified this bug and implemented a workaround where they escape the & before sending it to Twilio. Other customers have developed a workaround that escapes everything except for =. The bug fix will break both of these workarounds, but will result in proper and expected encoding/decoding of HTTP query parameters.

If your application escapes these characters when constructing a RecordingStatusCallback URL you will want to update its behavior to be resilient to this change by August 31st.

Twilio has now extended the maximum Voice call duration on Programmable Voice calls from 4 hours to 24 hours. We’ve also added the ability to set the maximum duration for individual calls generated via the Programmable Voice API and TwiML, using the timeLimit parameter. You can also use the same API parameter to update the maximum duration on active calls.

You can enable the 24-hour Maximum Call Duration in your Programmable Voice Settings console, and the timeLimit parameter is available for you to use in your applications using the Programmable Voice API and TwiML.

For more details on this feature, see our blog post here.