Twilio Changelog

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.

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.

On 10 October 2023 Twilio will be updating the public media IPs and port ranges for SIP and Voice SDK calls in all regions. We are moving from a per-region IP range allocation to a single global range: 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000 to 10000-60000.

Old IP and port ranges will no longer accept or send traffic after 10 October 2023 but will need to be kept open in your infrastructure until that time. We are making this change to provide flexibility, reliability, and scalability for the next ten years. You will need to update your network infrastructure to ensure that you have allowlisted the full IP and port ranges before 10 October 2023. Failure to do so will result in one-way audio and dropped calls.

Impacted Edge locations include: Sydney (AU1), Sao Paulo (BR1), Dublin (IE1), Frankfurt (DE1), Tokyo (JP1), Singapore (SG1), Ashburn (US1), Umatilla (US2).

Twilio Interconnect connections are excluded from these initial changes, but will be migrated separately in the future.

This release reversed changes made to the usage of Sync for outbound, transfer and conference state workflows that were introduced in v1.33. For full details on the changes included in this version read the release notes.

For more info on what changes were introduced in v1.33 and are now being reversed, refer to ‘Changes to Sync usage in Flex UI’ in the Flex UI release notes.

Twilio now supports a Sole Proprietor registration option for US 10DLC messages via the Console and APIs.

In our efforts to constantly improve customer experience and increase our adherence to compliance best practices, the Generic Pay Connector is now available in the TEST and LIVE mode. In the TEST mode, you can configure your payment gateway URL and perform testing using test credit card and bank account numbers. 

By default, any new Generic Pay connector instance will be created in the TEST mode. In order to move your connector to LIVE mode to perform live transactions, you will need to file a support ticket with Twilio with following details: The latest (non-expired) PCI Attestation Of Compliance (AOC) document received from your payment gateway, the configured URL of your payment gateway and a confirmation that you have reviewed the AOC document of your payment gateway.

Once approved, you can switch your connector instance to LIVE mode and your payment gateway URL will become immutable. After moving to LIVE mode, any changes to the configured payment gateway URL will require a support ticket with the details mentioned above.

Learn more about this feature in our API Docs.

Voice Integrity for Spam Remediation is now available in Public Beta.  We have added  Voice Integrity Trust Product in Trust Hub which enables you to register your Twilio phone numbers to remediate spam labeling through the Trust Hub API.

This allows you to:

• Increase your call answer rates by making sure your phone numbers do not get labeled as spam and avoiding calls getting blocked due to negative reputation. 

If you are currently using Voice Integrity in private beta, you will need to update your code. 

To learn more about Voice Integrity, please check our docs. 

Read more about Voice Integrity in this blog post.

Twilio has updated the behavior of status callbacks for calls placed to Android and iOS Voice SDK applications. Starting 15 March 2023, Twilio will emit the ringing callback after the mobile application has successfully received the push notification and established a connection to Twilio. Previously, we would emit the ringing the callback as soon as the push notification was sent. Devices that were powered off, unreachable due to network availability, or users who were not logged in were inaccurately reporting the call progress events before this change.

Fraud Guard is now enabled by default for all new and existing Verify services*. 

Check it on your Twilio Console by navigating to the Verify Services page and selecting your Service, where you can view Fraud Guard under the SMS tab. Read our documentation and blog to learn more about it. 

*not applicable to Verify customers using custom verification codes.

Twilio Event Streams Segment Sink is now Generally Available. Check out Segment Quickstart to learn more, and start sending Twilio events. With this Sink:

• You can send your data to one of 400+ destinations available via Segment.
• You can use Segment Profiles to link your Twilio data to an individual for an omni-channel view of your customer’s interactions, or use customer engagement tools, such as Engage, to deliver personalized, omnichannel experiences.