Twilio Changelog

You can now send and receive media messages that are up to 16MB in size on Twilio API for WhatsApp, an increase from a previous size limit of 5MB.

The Twilio API for WhatsApp supports sending and receiving images, audio, PDF files, and video. The following formats are currently supported:

• Images: JPG, JPEG, PNG
• Audio: MP3, OGG, AMR
• Documents: PDF
• Video: MP4

Please refer to our Guidance on WhatsApp Media Messages for additional details on media messages on Twilio API for WhatsApp.

Happy building!

Secure Real-time Transport Protocol (SRTP) provides encryption to ensure that the call media is private during transmission over a public network.

Pricing

SRTP Document

Programmable Voice SIP Document

To increase the capacity of chat applications, Actions Per Second (APS) limits for critical operations now apply on a per channel basis, rather than a per Chat Service basis. Until recently the number of messages you sent and number of channels you had were in a competition with each other.

The following operations are rate-limited per channel, with a default maximum set at 30 APS separately for each channel:

• Channel update
• Member create, update, delete
• Message create, update, delete
• Invite create, update, delete

The following operations will still be governed globally, with a single 30 APS limit applying to each Chat Service as a whole:

• Channel create, delete
• User create, update, delete
• Role create, update, delete
• Binding delete

This means users of your application can now communicate as much as they wish to without affecting the application.

Read more on the Programmable Chat Limits page.

To increase the capacity of your application, Actions Per Second (APS) limits for critical operations now apply on a per conversation basis, rather than a per Service basis. Until recently the number of messages you sent and number of conversations you had were in a competition with each other.

The following operations are rate-limited per conversation, with a default maximum set at 30 APS separately for each conversation:

• Conversation update
• Participant create, update, delete
• Message create, update, delete

The following operations will still be governed globally, with a single 30 APS limit applying to each Service as a whole:

• Conversation create, delete
• User create, update, delete
• Role create, update, delete

This means users of your application can now communicate as much as they wish to without affecting the application.

Read more on the Conversations Limits page.

Twilio Media Streams, introduced at SIGNAL 2019, is now Generally Available. Media Streams API gives you access to the raw audio of your Programmable Voice calls by forking the audio stream in real-time and sending it to the destination of your choosing using Websockets or SIPREC. Media Streams lets you improve customer experience in real-time by unlocking use cases such as real-time transcriptions, voice authentication, sentiment analysis, speech analytics and more. Send your forked audio stream to your own application or to a third party provider such as Google Speech-to-Text, Google Dialogflow, Amazon Lex, or Gridspace Sift.

Learn more about how to use it and check out our Github code samples.

To provide the best audio experience for multi-party Voice Conferences we automatically suppress the background noise of participants who are not speaking. However, in a very low-noise Contact Center environment, customers may believe the agent has hung up the call when the agent stops speaking. To avoid this problem we have added a new audio setting called Background Noise Passthrough.

When this setting is enabled the background noise of the agent will be passed through to the customer and provide an audible indication the call is still in progress. This can result in fewer abandoned calls by customers.

To learn more, visit the Conference Settings in the console.

Request Inspector now shows API requests made to Twilio's Voice APIs for call creation, call modification, conference participant creation, conference participant modification, and conference modification with respective parameters. Previously developers would need to enable logging of API request parameters in their applications and manually compare their application logs with the call behavior in Twilio Console to know if a call ended or a participant was muted using the API. These requests are available to view in Console for both completed and in-progress calls. This change simplifies debugging of call behavior issues by providing the API requests, TwiML requests and responses in one place.

Twilio now supports Amazon Polly Neural Text-to-Speech (TTS) Voices allowing you to use higher quality voices with TwiML <Say> in your voice applications. The ground-breaking improvements in speech quality come through a new machine learning approach which converts text into lifelike speech. Amazon Polly Neural voices are currently available in two speaking style voices - Newscaster and Conversational and across four languages - English (British), English (US), Portuguese (European), and Spanish (US).

Try these voices in your IVR applications by selecting them in the TTS console or by setting them in your TwiML <Say> attributes. For more information on the voices and on pricing, please visit Twilio Text-to-Speech docs and Amazon Polly docs.

This release of Flex UI introduces a pilot release of Advanced Team View Filters. This feature allows supervisors to search or filter their agents by name or activity or use custom, programmatically defined, filter criteria like teams or skills.

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

This release of Flex UI introduces an Initial Audio Device Check. This feature allows you to perform an audio device availability check when Flex starts up to make sure you are ready to receive voice calls.

Initial Audio Device Check is currently available as a Pilot feature. To enable it, visit the Pre-Release Features Page. You can learn more about this feature within our documentation.

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.