Twilio Changelog

You can now submit and query Media messages by using the Conversations REST API, opening up a host of use-cases for Media in your application.

How can you benefit?

• Implement Chat Bots that send images and other files
• Send notifications or system messages with images from the REST API
• Detect and manage media files in your backend with the Conversations Messages resource.
• Intercept and decline or transform inbound media from your customers by capturing the onMessageAdd webhook.

Get a guided tour and see more details in the updated documentation!

Media support in Conversations

The Programmable Voice Calls REST API now accepts TwiML when updating in progress calls. Prior to this change, you were required to provide an absolute Url that Twilio would use to return TwiML from your application. This change allows you to provide TwiML instructions when modifying in progress calls thus simplifying your application. For more details on modifying live calls checkout Modify Calls In Progress.

We have updated the Programmable Voice Conference REST APIs to improve performance and resolve some minor issues. There were some corner cases where the behavior of the Conference REST APIs was either not clear or not working as expected. These include:

• When fetching multiple Conference resources, the list returned is now sorted by the date created
• When fetching a Conference Participant resource, the status field returned is now populated with the correct status value
• Updating a Conference Participant resource with an unsupported combination of the fields hold, coach, and announce will now return an error code

The full list of the changes and clarifications are documented here.

This release of Flex UI and WebChat UI bring a number of usability improvements and new features to Flex Messaging:

• Browser Notifications: Flex now sends a browser notification when the Flex window is not in focus and the agent is assigned a new task or receives a new message.
• Markdown: Added support for markdown markup language for WebChat.
• WebChat Customer Presence: Indicator for WebChat tasks signaling whether the customer is still online.
• Typing Indicator in Task List: Added typing indicators in the Task List specific for WebChat.

Other notable changes in this release include:

• Improved Notifications API with browser notifications and actions support
• Support for double-byte characters (Chinese, Japanese, Korean) for WebChat message input

For a full changelog, visit our Flex UI release notes and WebChat UI release notes

The Flex Plugin Builder v3 is now Generally Available. This release enables you to build and deploy your plugins directly from the command line interface by leveraging the Functions & Assets API. This allows you to integrate your plugin development within a CI/CD pipeline.

You must update existing plugin repositories to take advantage of the new deployment options. These details can be found within our migration guide.

This release of Video iOS SDK introduces the ability to select the region to use when joining a Room. The default setting uses Global Low Latency (GLL), a latency based routing algorithm that selects the region with the least latency. If you don’t want to use latency based selection, you can specify any of the supported regions to connect to via this new API.

Refer to this guide for more information about region selection.

You can find the release here and API docs here

You can now get data about whether a user has enabled an unlock method to open their Authy app, when it was last unlocked, and the method used. This allows you to use the app unlock as an additional authentication factor for PSD2 SCA compliance and account takeover prevention.

This data is available in the User Status endpoint.

You can now search and add logos to your authenticator accounts, so it’s easier than ever to find them. Available in the Beta version.

Twilio SendGrid now has a default rate limit of 600 requests/minute/user on some of the V2 API endpoints, excluding the mail/send endpoint. If you exceed that rate limit you will receive a 429 error response with a “too many requests” message. We recommend updating your processes to ensure you do not exceed our default rate limit of 600 requests/min/user. We also recommend building in the consumption of the rate limit headers we send back, which gives specific information about how many requests you have remaining and when the rate limit amount will reset. For more information, see the Knowledge Center.

Twilio <Pay> now supports securely capturing and transmitting ACH payments on Twilio’s PCI-compliant Voice platform. Businesses can now allow their customers to make payments using consumer checking, consumer saving, or commercial checking accounts by providing their bank’s account number and routing number. ACH payment support, along with existing support for credit card payments, enables businesses to offer customers their preferred method for secure payment over the phone.

Learn more about <Pay> and how to securely capture payments.