Twilio Changelog

Twilio Video Javascript SDK 2.0 is now GA! Thank you to all our beta users and for all the feedback you sent us during the beta period.

Twilio Video Javascript SDK 2.0 introduces the Track Priority API, Network Bandwidth Profile API, Reconnection States and Events, and the Region Selection API.

Track Priority and Network Bandwidth Profile API gives developers the ability to specify how bandwidth should be allocated between video tracks. Furthermore, the three profiles, (“grid”, “collaboration”, and “presentation”), specify when tracks should be switched off (or not) to conserve bandwidth for the highest priority tracks.

The Reconnection States and Events will automatically attempt to reconnect when a transient network error is encountered.

With Region Selection API, the SDK will automatically connect to the lowest latency data center. This API can also be configured to connect to a specific data center for cases where compliance might be required.

If migrating from a 1.x version, please refer to our migration guide.

To get started with Twilio Video JS, check our Getting Started Guide

The most common way to access Twilio REST API is by using your primary Account SID and token. However, you may want to implement a separate access policy for different developers or subparts of your application by utilizing API Keys instead. This allows you to revoke access easily and at the right granularity.

Now, you are able to use the very same API Keys method for authenticating with Media Content Service (mcs.us1.twilio.com) to upload any attachments you would like to be sent over Programmable Chat.

Read more about API Keys support in the documentation.

The path of the executing Function is now available in the context object at runtime, allowing you to reconstruct the full Function URL for use in your application.

We’ve added a brand new Designs API, allowing you to easily create, edit, download, or delete Email Designs without relying on the SendGrid app UI. You can use the Designs you’ve created across all of your Twilio SendGrid Email—from Automations, to Single Sends, and Dynamic Templates. For more about working with the API, see our API Reference.

Collect's Confirm feature simplifies programming your bot to confirm the answers it receives from the user during a question answer sequence. Confirm can be enabled separately on each question using the confirm attribute. Learn more about using Collect Confirm in the docs.

Inbound Context lets you add data to the Autopilot Memory before starting a dialogue with the bot. It can help you make the bot experience more personalized and contextual by making information like names, purchase histories, account numbers etc. stored in third-party systems available directly in the bot conversation.

Inbound Context is available on all channels supported by Autopilot:

• SMS
• Voice
• Studio
• Chat
• WhatsApp
• Facebook Messenger
• Alexa
• Google Assistant
• Custom Channel

Test your email content against spam filters, validate hyperlinks, and preview HTML rendering across browsers and devices with Email Testing for Dynamic Templates. Monthly testing credits included for Trial, Pro and Premier plans, with additional credits available for purchase. See our Email Testing documentation for more details.

We've made some improvements to Transactional Templates. We've renamed them to Dynamic Templates since they can be used to build the content for any type of email message sent over our Email API. They can be found in the app’s sidebar navigation under both the new “Email API” navigation item or the “Templates” navigation item. We've also eased ongoing template management by adding thumbnail images and allowing duplication of entire templates as well as the individual versions within a template.

For more, see our blog post about working with Dynamic Templates.

Twilio Elastic SIP Trunking and SIP Interfaces have added support for a new codec, G.711 A-Law, also referred to as PCMA. Twilio now supports both G.711 versions, µ-Law (PCMU) and A-Law (PCMA).

This addition allows customers more flexibility in configuring their SIP infrastructure, especially in countries where G.711 A-Law is the prevailing standard codec. It also makes connecting with their SIP customers easier, as most SIP implementations will support at least one of the G.711 codec versions. Additionally, acceptance of a new codec could conceivably reduce transcoding on customer networks, which in turn could reduce network overhead and improve performance.

Please see our SIP Interfaces documentation for more information

Getting help while editing a Studio Flow just got easier with the release of the embedded help system. Now you can open help pages and search the docs without leaving the editing canvas.

Click any of the help icons throughout the canvas to load the Studio docs in the help window. The help window can be moved anywhere on the canvas that you find convenient or minimized to stay out of your way while you work.

Open a Flow and click the help icon to try it out in Studio.

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.