Product changelog and announcements

Compliance Toolkit is now available in Public Beta, allowing you to use Artificial Intelligence and machine learning to help manage compliance obligations with respect to certain local regulatory or compliance requirements.

To start using Compliance Toolkit, Opt in through the Twilio Console and review the detailed setup instructions in our developer documentation.

A faster, more reliable, and user-friendly way to port US local numbers now available in Public Beta. This does not impact the previous experience "Port a Number" which can continue to be used.

Earlier in May 2025, geolocation data was temporarily removed from the IP Access Management (IPAM) feature and related API endpoints on Twilio SendGrid. 

This feature has now been reintroduced. IP-based location data is now provided in the console and through API.

• SendGrid Console:
  • The location field in Settings > IP Access Management > Locations
• API:
  • The IPAM logs API endpoint    

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.

Consent Management in Unify and Engage in Public Beta!

With this release, Segment now stores end-user consent preferences, collected from streaming events or warehouse sources, directly on Unify Profiles as traits. These consent traits enable automatic enforcement of preferences in Engage Profile Audiences when sharing data with third-party Engage Destinations.

Additionally, users can leverage these traits to manually enforce consent preferences within Engage. For more information, see the Consent in Unify and Consent in Engage documentation.

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.
 

Liquid functions support in destination mappings is now Generally Available.

We’ve introduced liquid functions support in the mappings dropdown, allowing you to apply LiquidJS tags and filters to clean, format, or conditionally transform event data like user properties, timestamps, or metadata. This feature empowers you to tailor data to match the exact requirements of downstream tools with ease!

Key highlights include:

• 🏷 Supported liquid tags: Includes if, else, elsif, unless, case, when, assign, capture, increment, decrement, echo, comment, raw, and liquid for conditional logic, variable assignment, and nested code execution

• 🌊 Supported liquid filters: Over 40 filters like downcase, upcase, strip, prepend, append, replace, date, json, slugify, and where to manipulate strings, numbers, arrays, and dates

Real-world use cases:

• Standardize data, e.g., convert emails to lowercase with {{ event.properties.email | downcase | strip }}

• Format phone numbers, e.g., using filters like remove, prepend, and strip

• Set default values or apply conditional logic with if/else and default

For more information, check out our docs.