Twilio Changelog

The Flex Plugins CLI (Command Line Interface) is the new interface for developing, testing, and releasing plugins. It accelerates your plugin development by automating the key workflows you'll use while customizing Flex for your users.

With the Flex Plugins CLI developers can:

• Build new plugins - Start with a blank slate, or build from a template. Access all of Flex’s frontend programmability to customize the UI.
• Deploy and release plugin versions - Define plugin versions to track incremental updates to your customer experience. Deploy updates for each of your plugins individually, or bundle all of your updates together in a single release.
• Manage your version and release history - All of the updates to your plugin versions are tracked as a history of releases. Use this history to quickly identify and track changes in your application, and select a prior configuration to re-release in the event of an issue with your users.

Head over to the installation guide to get started and our migration guide to adopt the Flex Plugins CLI for your existing plugins.

To help developers troubleshoot their applications at scale we are releasing three new Video troubleshooting tools. The first is a console tool called the Video Log Analyzer. It provides detailed information about Video Rooms and Participants. This can be used to quickly investigate Room and Participant issues that occurred in the past 2 days for WebRTC Go Rooms and 7 days for all other Rooms types.

The second is the RTC Diagnostics SDK 1.0.0-beta2, which provides test functions to allow developers troubleshoot camera, microphone, speaker, and network issues. This SDK is a general purpose WebRTC SDK and does not rely on Twilio infrastructure. Developers can incorporate it into their applications for pre-call testing or troubleshooting user issues. The source code and information on using the SDK is available here.

Both the Marketing Campaigns Design Editor and Code Editor now support test data. Test data allows you to render Substitution Tags using sample values directly in each Editor's preview window. By providing test data, you no longer need to send a test email to ensure that your dynamic data will be displayed properly.

Both the Marketing Campaigns Design Editor and Code Editor now support test data. Test data allows you to render Substitution Tags using sample values directly in each Editor's preview window. By providing test data, you no longer need to send a test email to ensure that your dynamic data will be displayed properly.

To get started with your own designs, see Working with Marketing Campaigns Email Designs. For more information on using test data in Marketing Campaigns, see our Design and Code Editor documentation.

We are excited to announce that the Twilio Conversations API is now Generally Available!

Twilio Conversations is a single API for scalable, multiparty conversations across channels. Regardless of whether your clients communicate via web or in-app chat, in WhatsApp conversations, or over native group texting, the Conversations API reduces development time and helps you to deliver a superior customer experience.

In addition to meeting Twilio’s SLA standards for GA products, there’s a ton of new functionality packed into this release. You can read about all of the new features on the Twilio Blog, including dedicated Conversations SDKs for all three platforms – JS, iOS and Android – with support for Delivery Receipts.

We’re also now able to support compliant healthcare use cases for chat and SMS channels that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA).

Head to the updated Docs and start integrating Conversations into your communication flow. We just cannot wait to see what you build!

Policy updated as of September 28, 2020

Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from October 2, 2020 until November 4, 2020. Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.

During this Heightened Awareness Period, the following limitations will apply:

Account-level long code SMS rate limits have been implemented based on the amount of phone numbers:

• Customers with 2,000 or more 10-digit long code numbers on their project can send up to 2,000 MPS toward the United States.
• Customers with 100,000 or more 10-digit long code numbersas of October 2, 2020 on their project can send up to 4,000 MPS toward the United States. Twilio reserves the right to move the effective date of October 2, 2020 to an earlier date if too much capacity is allocated to customers, putting the network at risk.

For more details, please refer to this FAQ.

Policy updated as of September 28, 2020

Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from October 2, 2020until November 4, 2020.

Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.During this Heightened Awareness Period, the following limitations will apply:

• A maximum of 1,000,000 additional 10-digit long code phone numbers can be added to customers' existing accounts within the +1 country code. These numbers are available on a first-come, first-served basis, with inventory being added regularly.

For more information see this FAQ.

Twilio now supports sending up to 25 messages per second through WhatsApp.

If messages are sent at a rate higher than 25 MPS, Twilio maintains a queue. For very high outbound message volumes, messages can remain queued for up to 4 hours.

To achieve higher MPS, you can use Messaging Services. This allows you to distribute high volume across many WhatsApp senders within the Messaging Service.

Read more about MPS in our Best Practices guide.

Twilio Programmable Voice and Elastic SIP Trunking now perform SHAKEN/STIR verification on incoming calls to your Twilio local phone numbers. It can be used to display a trust indicator or to make a routing decision, such as bypassing a voice captcha or IVR and directing the call to an end user.

A verified call that has been given the highest attestation under SHAKEN/STIR means that the carrier that originated the call both (1) knows the identity of the caller, and (2) knows the caller has the right to use the phone number as the caller ID.

In Programmable Voice the request webhook presents the StirVerstat parameter, and in Elastic SIP Trunking there is a new header called X-Twilio-VerStat with the verification result. The new parameter and header are only present for incoming calls with SHAKEN PASSporT identity headers. Today, support for the SHAKEN/STIR call authentication framework is being deployed in the United States only.

You can now disable any Verify v2 delivery channel (SMS, Call, Email) that you are not using to reduce your risk of potential abuse. Navigate to your Verify Service Settings page to use this feature.

Twilio SendGrid now allows you to define multiple From addresses in personalizations objects. This allows you to override the default sender in each personalization as long as the default sending domain and personalizations sending domains match. For more information, visit our Personalizations documentation.