Twilio Changelog

Twilio allows customers to set caller ID as transferor or transferee for call forwarding use cases.

With this release you are now able to configure caller ID for call forwarding use cases in the console and API.

For details, check our documentation.

Customers can now view the reasons for their brand registration failures in the A2P wizard in the console or via the ISV APIs for US A2P 10DLC. In the A2P Wizard in the Twilio console, brand failures will result in an error screen with reasons for the failure and instructions to fix your brand registration before you can move forward. The GET Brand API call returns the failure reasons for ISVs registering their customers via API. You can review the failure reasons and API details here and reduce the likelihood of your brand registration failing by following the brand registration best practices here.

SendGrid has updated the system responsible for processing and logging spam report events. This change improves our system’s ability to process and count spam reports that come to us from mailbox providers when recipients mark a message as spam.

This change will result in elevated spam report metrics for some Twilio SendGrid users that will level off once our system catches up to all emails that have been marked as spam. The increase in spam reports is not the result of more recipients marking more mail as spam, rather it is the result of our system capturing spam report events more completely from this date onward.

Note that while this is a GA release, the updates are slowing being rolled out across all accounts.

Twilio SendGrid has launched the Apple Open Indicator in the Event Webhook. Open events now includes a new boolean field, sg_machine_open, to identify anonymous open events generated by Apple Mail Privacy Protection.

Super SIM now has one more location of our Distributed IoT Mobile Core in Singapore, to provide an Internet breakout for IoT customers in the APAC region. With this new location, Twilio has three Internet breakouts for Super SIM traffic: in Ashburn, Frankfurt, and Singapore, with more locations to follow.

Using distributed breakout to the Internet is important to achieve low latency, which opens up new use cases such as adding real time voice/video communications to an IoT device. In addition, it means less data crossing borders, and thus helps with data sovereignty.

To make use of the breakout location in Singapore, Super SIM customers must configure “sg1.super” as the APN on the devices (see Super SIM APN configuration). The existing default APN “super”, when used, results in traffic breaking out to the Internet via our mobile core in Ashburn, USA. When “de1.super” is used, the traffic breaks out to the Internet through our mobile core in Frankfurt.

If you are interested in using the Singapore Internet breakout location, please reach out to Twilio support.

One year after launch, we are excited to announce quota increases for WebRTC Go to allow you to build, launch, and run 1:1 video applications for free, for longer. The changes are as follows:

1. WebRTC Go now comes with unlimited TURN usage, removing the previous 25 GB/month limit.
2. You can now scale up to 500 concurrent participants or rooms, up 500% from the previous limit of 100.

To learn more about the quota increases and some of the key improvements we made for WebRTC Go developers over the last year, refer to the One year of WebRTC Go blog post.

Customers associating emergency addresses with their phone numbers don’t have to set EmergencyStatus to Active in the IncomingPhoneNumbers resource of the Phone Numbers API. Attempting to set the EmergencyStatus to Active or Inactive will be ignored, and will not have any effect on the enablement or disablement of emergency calling.

When fetching an Incoming Phone Number, a new parameter EmergencyAddressStatus is returned with the registration status of the emergency address with the values registered, unregistered, pending-registration, pending-unregistration, registration-failure, and unregistration-failure.

Voice customers with US and Canada phone numbers should provide their accurate physical address to comply with the FCC and CRTC E911 rules. If you make a 911 call from a US or Canada phone number without a registered emergency address, Twilio will pass through a $75 fee per 911 call for the call to be delivered to a national emergency location center where a trained agent will ask for the emergency location.

For additional information, check our SIP Trunking and Programmable Voice documentation.

Customers registering for their Primary A2P Brand for US 10DLC traffic automatically get their brand vetted by carriers through a process called Secondary Vetting. This vetting costs $40 and was being covered by Twilio till Sept 30. The Secondary Vetting fee will now be passed through to customers and reflect in customer bills as the waiver has ended.

Note Starter Brands and Starter Campaigns continue to remain free of charge.

Businesses can now move their existing WhatsApp Business API phone numbers to the Twilio platform at any time whether they were previously registered through a different Business Solution Provider or directly with Facebook. Upon a successful migration, the transferred number retains its display name, messaging limit tier, quality rating, and Official Business Account status. High quality message templates on the account that it was previously registered on will also be copied over to the new account on Twilio.

For more details on how to move WhatsApp numbers to Twilio, please take a look at this support article.

Twilio MMS can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.