Twilio Changelog

The latest Twilio PHP helper library v6.0 is now available on GitHub. This latest version has full support for many of the features in PHP 7 such as scalar and return type declarations and of course the illustrious spaceship operator <=>. For PHP applications running PHP 7.2 and later, we recommend upgrading to this latest version to take advantage of the new PHP features and continue getting Twilio updates.

Note that with this release, we are officially ending support for PHP versions that are already end-of-life, including PHP 5.5, 7.0, and 7.1. If your application requires PHP versions 7.1 or below, you can continue using older versions of the Twilio helper libraries, but they will not receive updates.

You can download the latest PHP library from Packagist or source code on GitHub.

The Regulations API is moving to Public Beta. The Regulations API resource allows users to programmatically fetch the Regulations for a given phone number’s country, type, and the end-user type. The Regulations API is in sync with the Regulatory Guidelines webpage and is continually updated.

For additional details:

• Regulations Public API
• Regulatory Guidelines
• Getting Started: Creating a new Regulatory Bundle

Twilio Interconnect has been expanded with a new Interconnect Exchange Installation in Sydney, Australia.

The new exchange provides customers with connectivity via cross connect, VPN, Bring-Your-Own-MPLS, and the Equinix Cloud Exchange with initial product support for Elastic SIP Trunking, SIP Interface and Voice WebRTC.

Twilio now has three Interconnect Exchanges in the APAC region, one in Singapore, another in Tokyo and this new one in Sydney, Australia. This allows APAC customers to set up redundant interconnects from their networks to Twilio adding an additional layer of resiliency while benefiting from the security and consistency of a dedicated interconnect.

Click here for information about Twilio Interconnect and here for documentation.

Provisioning new phone numbers with identity regulations through the Twilio /IncomingPhoneNumbers API now requires an approved BundleSid. End-users will be required to include the proper documentation for regulated phone numbers, which are most phone numbers outside the US and Canada. API calls to provision regulated phone numbers that do not include a compliant BundleSID that is valid for the phone number will fail with error code 21649.

For additional details:

• Blog post on this change
• Phone Number Regulatory FAQ

We have added new properties to the Task resources and the TaskQueue Statistics API in TaskRouter, to enhance TaskQueue insights in scenarios when tasks are transferred to another TaskQueue.

The TaskRouter Task resource now has a new property task_queue_entered_date, which captures the time when the task entered its current TaskQueue.

The TaskRouter TaskQueue Statistics API has three new properties, LongestRelativeTaskSidInQueue and LongestRelativeTaskAgeInQueue, which provide the task SID of the task waiting in the TaskQueue the longest and its relative age in the TaskQueue, respectively.
WaitDurationInQueueUntilAccepted provides relative wait duration in the TaskQueue stats (avg, min, max, total) for tasks that were accepted while in this TaskQueue.

To learn more about the new Task field, please refer to our documentation on Task properties.
To learn more about the new TaskQueue Statistics API fields, please refer to our documentation on TaskQueue Real-time Statistics and TaskQueue Cumulative Statistics.

Automation (available within the Advanced Marketing Campaigns plan) now supports a new entry criteria option to trigger an automation when a contact joins a segment. This also expands the functionality of the exit criteria, automatically removing contacts when they no longer match the entry criteria (i.e., they’re no longer in the segment). For more information, see the documentation in the Knowledge Center.

We have updated all Flex projects that use Automatic Updates to Flex UI 1.16.2.

This release of Flex UI introduces Chat and Messaging Transcripts for Flex Insights. Supervisors can now open a historical chat or messaging conversation from Flex Insights and see its content. While viewing the content, it is also possible to comment and assess these conversations.

Other notable changes:

• New Actions to programmatically send DTMF tones when there is an active voice connection.
• Flex Insights screens are accessible from top-level Flex navigation.
• Flex Insights Player opens directly within the dashboard instead of opening in a separate window. This significantly improves the speed with which you can scan through multiple calls or chats.
• You can now attach references to 3rd-party web content related to conversations – such as CRM records – and open these directly in Flex Insights.

For a full changelog, visit the Flex UI release notes.

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.

As of February 3rd, 2020, we have discontinued Fraud Lookup, a feature that provided phone attributes like porting history and advanced line type for fraud prevention. This feature was released as a Developer Preview to receive customer feedback. We are incorporating the feedback we’ve received into our future product designs, which we’ll share more about when they become available. The rest of the Lookup product, which is Generally Available, will continue working as-is and is unaffected by this change.

The beta for Client Insights ended on August 5, 2019 and was superseded by the general availability of Voice Insights. The Client Insights Dashboard was removed from Console at that time, though we have continued to respond to requests made to the preview API. Twilio will cease responding to API requests to preview resources on May 1, 2020. Any HTTP requests to preview resources after this date will result in a 404 response from the API.

If your application is currently making requests to any of the preview API endpoints described below, you will need to migrate to the new Voice Insights API endpoints.

Twilio Functions lets you deploy NodeJS code into Twilio's serverless environment to handle communications events in support of your applications. Functions can be deployed via API or UI. Previously, Functions deployed via the API used NodeJS version 10, but Functions deployed via UI used NodeJS version 8. NodeJS version 8 is now End Of Life. From today all Functions deployed, either via UI or API use NodeJS version 10. Click here for more information about the upgrade.