Twilio Changelog

You can now use our new REST APIs to create and manage Restricted API Keys. This unlocks your ability to programmatically use Restricted API Keys which provide scoped access credentials to Twilio API resources. We have also added new permissions for Monitor Events and Monitor Alerts APIs. 

Restricted API Keys allow you to decide which Twilio API Resources an API Key can access, and which action(s) the API Key is allowed to take on those API Resources.

As of September 10, 2024 the Lookup Line Status Private Beta is now available!

Lookup’s Line Status package allows you to get the status information of a mobile phone number. Line Status provides statuses that lets you know if the mobile number is active, inactive, unreachable, reachable or unknown.  Validate phone numbers in your contact database to improve the efficiency of your campaigns.

Additional Documentation on this feature can be found here

We are excited to announce the release of RCS in Twilio Programmable Messaging as a public beta. Twilio is offering RCS text in the Programmable Messaging API as a branded, verified messaging experience. When sending SMS messages with Messaging Services, Twilio will automatically send RCS messages to capable devices. Devices that cannot receive RCS will continue to receive SMS messages. If you’d like to learn more about RCS and request access you can do so here.

The ReferralCtwaClid parameter that is already available through Twilio webhooks (Changelog) can now also be delivered through Event Streams (docs). Update to version 4 of the schema for Inbound Message events (schema definition) to start receiving this parameter through Event Streams.

This new support will guarantee at-least-once delivery of this business critical event, as well as improve integration flexibility for customers using multiple Twilio products or a product that is built on top of multiple products, such as Flex and Studio by making this data easier to consume.

Sending Content Templates with a messaging service sid in the from or a MessagingServiceSid field is now optional!

Previously using a messaging service and specifying its sid was a requirement to use Content Templates. Now customers can send a content template by using the standard to and from fields containing a phone number with the sender prefix if relevant. 

Previous methods of sending a content template using messaging service sid will still be supported. 

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’ve updated our email notifications to include extra details like the parent account and the associated phone number. 

Visit our Twilio Docs for more information on Toll-Free Verification Notification Emails.

Effective September 30, 2024, Twilio will begin billing for failed messages in Programmable Messaging.

[Update] For a more in depth description of nuance here please see our help article.

As part of our commitment to transparency and improving message deliverability, we have introduced new features that provide detailed insights into message delivery errors and how to address them. With these enhancements, a failed message processing fee of $0.001 will be applied to messages that terminate in a "Failed" status. This does not affect messages that end in any other status.

Please note that you will not be billed for:

• Failures due to Twilio internal errors (Error codes: 12400, 20500, 20504, 30036, 30103, 30500, 63010, 63012).

• Failures due to Twilio account suspension or fraud detection limits (Error codes: 30002, 30454, 63038, 90010).

• Messages failed by SMS Pumping Protection and Messaging Geographic Permissions (Error code 30450, 21408).

• Meta imposed WhatsApp restrictions beyond a customer’s ability to remedy (Error codes: 63013, 63018, 63021, 63024, 63032).

You will never be billed for errors that are Twilio internal issues, or linked to other products or features. 

Why is this happening?

Twilio conducts pre-checks to help you avoid standard termination costs incurred by most CPaaS providers. Processing failures incurs costs for us, and this new fee will help us maintain and improve our services sustainably.

What do you need to do?

Review your account’s failed message volume in the Messaging Insights dashboard in Twilio Console to better understand your Twilio integration’s health and the impact of this change. If you see a high rate of message failures, use the messaging insights tool to explore their common error codes and causes. For the vast majority of customers this change will change your bill by less than 1%.

Common causes for elevated error rates include:

• Retrying requests to create messages when Twilio’s API responds with a 4xx HTTP status code.

• Invalid numbers in your contact lists (e.g., error codes 21211, 21614, or 21610)

• Other specific error codes that you can review in our error dictionary with potential causes and solutions.

Starting on August 12, 2024 we will introduce a new field into the response for the Content API fetch approval status endpoints. 

Affected endpoints will include: 

Fetch Content and Approvals

Fetch an Approval Status Request

The new endpoint will be in preparation for an upcoming new content type twilio/flows!

A host of new functionality is now supported in Content Templates! These templates are omnichannel ready. As more channels such as RCS, support the content type, you will be able to use the same rich content template on newly added channels. Use Content API to: