Twilio Changelog

You can now filter the results returned by the Read Multiple Conversations API by created date and state. 

The Lookup API now has a new package in Public Beta! Identity Match will give you the ability to confirm the identity of your users at any point in your customer journey. We suggest using Identity Match every time a new user registers for your platform, or any time a high risk transaction takes place. Please review our documentation pages for more information on this exciting new product.

Call and conference creation and modification events, as well as call progress events, can now be subscribed to via Event Streams. Creation and modification events enable developers to see the initial creation and subsequent modification parameters for any calls, conferences, or conference participants made via API. Call Progress Events notify you of what’s happening during an outbound call and alert you when it progresses through key events, such as Initiated, Ringing, Answered and Completed. 

Twilio is making changes to SMS Geo-Permissions in the Twilio Console to better differentiate traffic being sent to the United Kingdom to better protect our customers from SMS Pumping. The United Kingdom will be broken out into four territories: Guernsey, Isle of Man, Jersey, and the United Kingdom which was previously solely under the United Kingdom (+44) prefix. If you enabled SMS Geo-Permissions for the United Kingdom(+44)  and had past activity within the following prefixes: Guernsey (+44778, +44783), Isle of Man (+447624, +44745), and/or Jersey (+4477003, +4478299), we have enabled your SMS Geo-Permissions in the newly created territory within the United Kingdom.

If needed, you can enable or disable SMS Geo Permissions to any country at any time in Twilio Console by following the steps in this Support Article.

Effective May 3rd, 2023, Twilio SendGrid customers will be able to configure multiple endpoints for our Event Webhook feature. This enhanced feature provides customers with greater flexibility and control with the ability to  deliver event data to multiple endpoints, each configured to receive whichever events make sense for your email program. For example, you could have one Event Webhook to monitor engagement data and another for delivery events, or one Webhook sending data to your marketing analytics pipeline and another feeding your application monitoring stack.

With this new feature roll-out we have updated the user interface (UI). All the webhook settings are in one place. In the SendGrid UI, click on Mail Settings in the left navigation, and you will see Event Webhooks below the  Webhook settings heading.. We have consolidated our security features: Signature Verification and OAuth 2.0 in one place, providing you with a streamlined user interface.

Additionally, we have added four new fields in the UI and API:
1. Friendly Name
2. Webhook ID
3. Created Date
4. Updated Date

Note:
* Existing webhooks will not be affected by this change, but customers can add additional endpoints as desired.
* The number of endpoints per user is dependent on the TSG plan you are on. See the SendGrid pricing page for details.

We hope this new feature will enhance our customers' experience with Twilio SendGrid and improve their ability to track and analyze their email engagement and delivery data.

As previously communicated, Twilio has changed how withheld caller ID is displayed on outbound <Dial> calls. This change has been made for inbound Programmable Voice calls as well. Any Programmable Voice calls where the caller ID has been withheld will now display anonymous in the From field. 

The Twilio Programmable Voice SDKs now offer the new Call Message Events: User-Defined Messages and User-Defined Message Subscription resources for application developers. This release, available now in Public Beta on the latest major versions of Voice JS and iOS SDKs, supports relaying custom events to and from your backend to a registered Voice SDK Client on any active call - all within the Twilio platform. This closes the loop on our December ‘22 release by extending support for established (“in-progress”) calls to also support for calls in a ringing state. By leveraging the existing signaling connection, you no longer need to set up your own communication channel between your client-side and server-side applications. This unlocks a host of advanced use cases, including:

• Relaying (and taking action on) call progress events
• In-line text transcriptions
• Upgrading 2-party call to multi-party via Voice Conference
• Presenting valuable context in your application at the right time, such as quick text reply buttons in a mobile app

In coming releases we’ll bring this functionality to our Android SDK as well as explore options to provide “out-of-the-box” event subscriptions for common use cases. Check out the docs for more information on how to use the new functionality in your application. We can’t wait to see what you build!

We previously announced that the Notify product would end of life (EOL) on October 23, 2023. We’re now extending the EOL deadline; the new EOL date for Twilio Notify is April 25, 2024. After this date, any requests made to the Notify API will fail.

We hope this extension will provide you with enough time to transition to alternative options. To assist you in this process, we have prepared a migration guide and recommend reaching out to our support team with any questions.

As previously communicated we have updated the status callback behavior for mobile Voice SDK calls. This change more accurately reflects the actual condition of the call; i.e. calls sent to powered off or otherwise unreachable devices will no longer return a ringing call progress event. If your application logic depends on the ringing status callback for its performance, you will need to update your application to handle this condition appropriately.