Twilio Changelog

Outbound calls made using the REST API are throttled and queued to never exceed the Calls Per Second (CPS) threshold value that is set on your account. Today we are releasing support for updating that CPS threshold from the Voice Settings console page. You can use the QueueTime attribute, which describes the estimated call queueing time in milliseconds, to tune the CPS value for your account.

Using Twilio console, you can now update your CPS to take effect immediately or schedule changes to take place in the future.

You can now update your Flex application to use the latest version of React and ReactDOM. This allows you to use React’s newest APIs, including React Hooks, when developing your Flex plugins.

This feature is available in Flex UI v1.19 and above. You can update your application to use the latest React version on the Pre-Release Features Page. For more details, visit our React documentation.

The Programmable Video iOS SDK 3.7.0 release adds support for the new local network privacy policy introduced in iOS 14.0 and iPadOS 14.0. This policy requires user permissions for local network access and Peer-to-Peer applications using previous versions of our iOS SDK may break if permission is not granted. Applications that use Group Rooms are unaffected.

With this SDK release the local network path is no longer automatically included as one of the connection candidates. This modification ensures that users will not see a change in application behavior when upgrading to iOS 14.0 or iPadOS 14.0. Developers can still opt to include the local network as a connection candidate by setting a parameter. We recommend developers upgrade their Peer-to-Peer application to ensure correct behavior with iOS 14.0 and avoid any adverse changes to the experience.

For additional information, see the iOS SDK changelog and our helpdesk article.

This release includes support for the expansion of Twilio’s Global Infrastructure via Edge Locations which allows connectivity control into and out of Twilio’s platform. These changes will provide an improved experience bringing Twilio’s public and private connectivity closer to your application.

Note: All these changes are backward compatible and will not impact existing configurations.

The Elastic SIP Trunking API supports Edge Locations for connections to Twilio’s infrastructure via the Trunking Base URL in Twilio's API https://trunking.{edge}.us1.twilio.com.

Updates to your Super SIM’s status or Fleet are completed asynchronously. Its status first transitions to ‘scheduled’ while the update procedures complete at which point the status reaches the desired state (e.g. ‘active’).

You can now provide a callback URL when making the update request using the Super SIM API. When the update finishes, we will send a HTTP request to the provided URL letting your application know that the update is finished.

To learn more about this new feature, see the documentation.

See which links are getting the most clicks within your emails, and learn which link locations perform best. Learn more more about click tracking .

Super SIM has been added to the API Explorer. Use the API Explorer to test out Super SIM API calls from Console.

You can use the API Explorer to perform actions that can currently only be done through the API, such as sending SMS Commands to your Super SIMs, from Console.

Voice Insights Subaccount Dashboard provides an overview of subaccounts and the ability to identify those subaccounts which are performance outliers for common metrics including call volume, average length of call, answer ratio, post-dial delay, SIP responses, and more.

The dashboard displays subaccount performance over defined time periods and can help shine a light on accounts disproportionately impacted by call quality and subjective user experience degradation.

Voice Insights Subaccount Dashboard provides multiple views of the data with export capability. Filtering is available for date range, time zone, account SIDs, and call volume percentiles.

For more information see the documentation.

You and your team can now control who receives what critical communications from Twilio.

Earlier, we were sending emails like developer updates and pricing changes to the account owner.

Now, we will let you decide what notifications you want to receive, through role based access control.

As the Owner or Administrator of your account, you can customize which roles in your organization will receive each of these five types of Twilio notifications

• Pricing Updates: Updates to product prices and rates
• Regulatory and Compliance Alerts: Alerts on regulatory and compliance issues/requests
• Developer Updates: Updates to Twilio APIs, helper libraries and other developer tools
• Legal and Privacy Updates: Updates to our legal terms, such as a our Terms of Service or Privacy Notices
• Security and Fraud Alerts: Warnings about active fraudulent attacks and potential security vulnerabilities

As the Developer, Billing Manager, or Support person, you can manage the notifications that the Owner or Administrator of your account has already opted you into.

Start managing your notification preferences now.

Check out this blogpost to learn more about managing your notifications.

Questions/Feedback? Reach out to asriram@twilio.com.

It is now possible to track the status of each message in a Conversation with the Delivery Receipts feature for the Conversations API.

The same statuses you rely on for your messaging functionality are now supported for the Conversations API, offering instant status updates like "sent" or "delivered" via REST API. These Receipts show detailed information on each message in a conversation, including the "read" status for WhatsApp.

Aggregated statuses are visible directly in the REST API Messages resource and you are able to see individual receipts by setting up a dedicated webhook or through the Receipts API resource. Direct SDK exposure is also to follow soon.

Check documentation and use-cases for more information!