Twilio Changelog

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.

The new version of Marketing Campaigns now provides a sample of 50 contacts within the UI for any given list. To view all contacts included in a list, users can use the export option.

Twilio Video Group Rooms now support FEC (Forward Error Correction) for video tracks. With this feature, video traffic received by Twilio Video Media Servers is now protected with redundancy. This means moderate packet loss in the network can be recovered without degrading the video quality. FEC will improve video quality for participants experiencing high-latency and lossy network links. FEC is activated automatically when required, no application updates are needed to use this feature.

Developers can now select the geolocation of the Twilio infrastructure that serves their Video Rooms. In addition, developers can use a new GLL (Global Low Latency) option. When selected, Twilio automatically chooses the closest region to minimize the latency of participants connecting to the room.

By default, GLL is deactivated. To implement this feature for your application, you need to use the SDK API, the Rooms REST API or the Twilio Video Console to specify a different region as explained in our docs.

The Network Bandwidth Profile API is a new API designed for optimizing quality in Group Rooms. It enables developers to specify how much bandwidth should be allocated to each video track as a function of the track priority. For example, it can be used to prioritize a screen share or the dominant speaker video track over the rest. The API also allows control of the total consumed bandwidth by enforcing limits to the maximum subscribed bitrate and to the maximum number of visible subscribed video tracks. In addition, it automatically enforces a mechanism that switches-off the less relevant tracks to protect audio and high-priority video tracks quality in case of network congestion.

By default, the Network Bandwidth Profile API is deactivated. To take advantage of this new feature, you will need to set a Network Bandwidth Profile.

The Track Subscriptions API is a new REST API available for Group Rooms. It allows developers to define which participants are subscribed to which tracks. Currently Group Rooms use a "subscribe-to-all" model meaning that participants are subscribed automatically to all the tracks published to the Room. With this new API, developers can now set, in a dynamic and configurable way, the desired communication topology: one-to-many (e.g. presentations where only one participant publishes and the rest only receive), some-to-many (e.g. collaborative presentations where some participants talk and the talk is published to the rest), whisperers (e.g. participants that can listen/view to all but can only be listened/viewed by some), and more.

By default, the Track Subscription API is deactivated. To implement this functionality for your applications, you will need to use the API to set subscribe rules.

The Network Quality API provides you a network quality measure that can be used to indicate the current network quality to your users. As network conditions vary, showing this information helps you provide a more intuitive user interface.

For more information, refer to the [docs] and the [Tutorial]

This release is available here: [bintray]