Product changelog and announcements

Effective 5 February, 2024, Twilio will deprecate HTTP voice media endpoint and redirect requests to fetch recordings media files to HTTPS. As a result, CNAME to serve media from custom hostname will no longer be supported.

With Generative Audiences, you can use generative AI to create Engage Audiences.

Using natural language prompts, you can describe your desired audience based on events performed, profile traits, or existing audiences in your workspace.

To learn more, visit Segment’s Generative Audiences documentation.

Effective January 31, 2024, messages sent from toll-free numbers pending verification will be blocked. Only fully verified toll-free phone numbers will be eligible to send messages. 

Blocked messages will return Error 30032 (any message sent from a restricted or pending TFPN) or Error 30007 (if spam/unwanted on a verified TFPN), and are subject to messaging fees.

These verification efforts, along with increased message filtering, help Twilio combat spam and create a trusted messaging ecosystem for you and your customers.

You may use our Twilio Console or API options to submit toll-free phone numbers for verification.

For more information, please check out our guide Toll-Free Message Verification for US/Canada.

The Google Display and Video 360 destination, rebuilt on Destination Actions, is now in public beta.

This destination lets you streamline activation of end-to-end ad campaigns under Google Marketing Platform.

Segment will deprecate the Personas DV360 destination. Moving forward, all users will work with the new Display and Video 360 (Actions) destination.

To learn more about the destination and migration steps, view the Display and Video 360 (Actions) documentation.

The United Kingdom (UK) regulators are enforcing new Know Your Customer (KYC) requirements and guidelines for UK long codes. Twilio will collect KYC information through Regulatory Compliance (RC) bundles either in Console or through our API.

As previously communicated, Twilio's public Voice IP migration has completed as of 8am UTC-8.

We previously announced that the Notify product would end of life (EOL) on April 25, 2024. Notify will now EOL on December 31, 2025, in order for Twilio to provide an alternative solution for the current Notify product. Note that this EOL doesn’t affect other push notification use cases powered through other Twilio products such as Verify, Voice, Conversations or Engage.

We will update you via our Twilio Blog as soon as we have an alternative solution for the current Notify product. We have also prepared a migration guide and recommend reaching out to our support team with any questions.

The Compliance Embeddable is a React application you can i-frame into your existing web portal / application so you can collect business information directly from your end customers via self-service

Starting February 15, 2024, Twilio will reject GET requests with a non-empty body sent to Twilio REST API endpoints; this change is part of an infrastructure upgrade to enhance security and resilience, reinforce best practices, and mitigate any potential risks. After this date, these requests will return a Status Code 403 Access Denied message.