Twilio Changelog

You can now select permissions for TaskRouter APIs while creating a Restricted API Key on Console. The product already supports permissions for Studio, Voice, SIP, Messages, Regulatory Compliance and Long Codes 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.

Customers registering 10DLC Brands and Campaigns for A2P Messaging can now create subscriptions to receive detailed error codes through Event Streams when a Brand or Campaign registration fails.

This enhancement uses Twilio's Event Streams product to push error codes directly to customers, eliminating the need to query the Brand and Campaign endpoints or check the A2P Console Pages.

Existing users must update to Schema version 2 for the following events to start receiving error codes:

• Campaign Registration Failure 
• Brand Registration Failure.

Check out the Event Streams product or documentation on how to get started!

We’re excited to announce the Public Beta release of Flex Mobile, a pre-built app available for iOS and Android devices. Flex Mobile brings the Flex experience to a phone or tablet, giving agents the flexibility to answer calls and messages while away from their desks.

Current Flex customers can download the app and use it with an existing Flex instance at no additional cost and with no new development effort. If you’d like to onboard new agents to Flex for mobile access, contact your Twilio Account team to add additional Flex Mobile licenses that can be purchased at a discounted price.

To read more about Flex Mobile, see our blog post or visit the docs.

Twilio has enabled automatic roaming GLL call handling for Programmable Voice SDKs from our Umatilla/us2 edge location.

Twilio now allows you to pass additional SIP headers as part of an outbound SIP call.

Twilio is introducing the Operator, OperatorType and OperatorAttachment Resources for the Voice Intelligence API, now available in public beta.

The Activity Skills Filter plugin lets you map an agent's status to their skills and enables custom order status in the status selector.

Effective August 1, 2024, Twilio will transition to a unified deployment model for Flex plugins, discontinuing direct deployments through Twilio Functions and Assets. You will need to use the Flex Plugin Builder (Plugins CLI) for all plugin deployments and modifications. This update simplifies maintenance and upgrades across the platform.

Starting April 1, 2025, any legacy plugins that have not been migrated to the new system will stop working within the Flex UI. It’s crucial that you migrate your plugins before this date to avoid any disruption in service. 
Updated 25-Sept-2024: Previously, this changelog entry stated that non-migrated legacy plugins would stop working on November 20, 2024. The deadline has been extended to April 1, 2025.

Previously, Flex plugins could be directly deployed and modified via Twilio Console or the Serverless Toolkit, allowing flexibility in management but varying in standardization.

These changes are aimed at enhancing security and manageability without impacting system performance. We encourage you to follow these steps to ensure a seamless transition:

• Identify your legacy plugins: Review your Flex custom plugins to determine which of your deployments are considered legacy plugins. 
• Install the Flex Plugin CLI: If you haven’t already, use the Twilio CLI documentation to install the Twilio CLI on your local machine. Then, install the Flex Plugins CLI to ensure you have the necessary tools for migration. 
• Follow the migration guide: Our Flex plugins migration guide outlines all necessary steps to reinstall your plugins without impacting your ongoing operations. 

The Make HTTP Request widget configuration now includes a checkbox allowing the request to be made with your Twilio credentials. 

This makes it easy to invoke Twilio APIs that are not available natively as Studio widgets. It is also more secure than embedding your Twilio credentials within the request URL.

To learn more, visit the Make HTTP Request documentation, or try it out now in Studio.

TaskRouter now enables agents to place outbound calls from any queue, whether or not they are a member of that queue. This update enhances TaskRouter’s adaptability and functionality for diverse operational needs.

Effective May 14, 2024, TaskRouter no longer performs backend validation to confirm that an agent is a member of a queue before allowing them to place an outbound call from it. This change improves contact center flexibility by accommodating a wider range of use cases, such as agents who are assigned to multiple queues or who are temporarily assisting in a different queue. 

Previously, TaskRouter required agents to be a member of a queue in order to place a call from that queue. 

This change does not impact system metrics or statistics.