Twilio Changelog

Effective May 1, 2024, Twilio will introduce tiered pricing and lower the price for Voice Insights Advanced Features. The existing list price of $0.0025/min will change to the tiered pricing

Effective June 1, 2024, Twilio is updating the Voice Insights products, affecting our Voice Insights Customers.

Now Twilio SendGrid accounts can  send email in the EU region. Event data that contains personal information will still be stored globally.

Why is this happening now?

Twilio SendGrid is launching this partial data residency to allow customers to reduce the amount of data leaving the EU. 

How do I get access to the beta?

All Twilio SendGrid customers on Pro plans or higher have access to regional subusers and dedicated IP addresses. To send regional email, be sure to use the base URL api.eu.sendgrid.com.

To learn more about Regional Email in Beta, see our blog post about Regional Email EU.

SendGrid Marketing Campaigns now supports more unique identifiers per contact!

Our latest update to our SendGrid Marketing Campaigns product now allows for up to four unique identifiers per contact: Email, Phone Number ID, External ID, and Anonymous ID. This highly-requested update means an email address is no longer mandatory to store a contact in SendGrid.

Additionally, this new feature gives you greater flexibility in contact management and expanded opportunities for engaging marketing strategies across various channels, all while setting the stage for upcoming SMS capabilities and integration across Twilio and non-Twilio products.

For more information, check out how to Create and Manage Contacts in SendGrid.

We have begun enabling accounts for error log tracking of message creation API errors. Full details are available here. When your account is enabled, the banners on the messaging error log console page will update to reflect that your account is enabled. Note that accounts will be enabled on a per-account-sid basis over the coming weeks; thus certain sub-accounts may gain access before others.

We are excited to announce an enhancement in the Toll-Free Verification process. In our ongoing efforts to streamline and improve the user experience, we now support multiple rejection reasons, new rejection error codes have been added and existing rejection error code descriptions have been improved. These changes are supported in the Toll-Free Verification API, Console, Event Streams - webhooks and email notifications-about a rejected toll-free verification.

With this release, it’s important to note that the Toll-Free Verification API’s LIST, GET and webhook still supports a single rejection reason, but we strongly advise transitioning to the new “rejection_reasons” attribute, so that you pick up all the rejection reasons. 

Previous releases have included this metadata, which you may also find useful when processing a rejection: 

  "rejected_on": "2024-04-05T22:01:58.076Z",

  "edit_expiration": "2024-04-05T22:01:58.076Z",

  "edit_allowed": true,

Additionally, the Twilio-Rejected event webhook now includes the phone number DID: 

  "phonenumber": "+18002225555",

For a detailed list of all toll-free verification error codes please visit Twilio Error and Warning Dictionary.