Product changelog and announcements

We previously announced that the Notify product would end of life (EOL) on October 23, 2023. We’re now extending the EOL deadline; the new EOL date for Twilio Notify is April 25, 2024. After this date, any requests made to the Notify API will fail.

We hope this extension will provide you with enough time to transition to alternative options. To assist you in this process, we have prepared a migration guide and recommend reaching out to our support team with any questions.

Twilio now supports a Sole Proprietor registration option for US 10DLC messages via the Console and APIs.

When users reply to a specific WhatsApp message, Twilio now passes additional context to the WhatsApp Sender’s webhook URL. The OriginalRepliedMessageSender and OriginalRepliedMessageSid parameters will include information about the previous message the user replied to. If you need the content of the original message, you can use this API to fetch the Message Resource.

Note that only message replies to messages sent within the last 7 days will contain this additional context. Incoming message replies to messages sent over 7 days ago will still be delivered, but will lack this additional information.

For more information about this and other inbound message parameters, please refer to this page.

Twilio is making changes to Geo-Permissions in the Twilio Console to better differentiate traffic being sent to both Israel and Palestine. Palestine, which previously was only +970 will now include Palestinian networks operating with +972 prefixes. If you enabled geo permissions for Israel and/or Palestine, then we have updated your selection based on the corrected prefixes.  Israel will no longer send traffic to +97256 and +97259 since these two prefixes are associated with Palestinian Jawwal and Wataniya cellular communication company.

If needed, you can enable or disable SMS Geo Permissions to any country at any time in Twilio Console by following the steps in this Support Article.

In an ongoing effort to raise awareness of the risk of SMS Traffic Pumping fraud, Twilio has added a popup asking customers to acknowledge the risk when opting to send SMS traffic to countries Twilio has identified a rise of SMS Traffic Pumping Fraud. Twilio will update this list from time to time.

What do I need to do?

We recommend review of the current geo-permissions on your account in Console.

(Support Article) Please take the following steps to protect your account from SMS Traffic Pumping Fraud:

1. Log in to your Twilio Account and verify the traffic history on your account is legitimate in Messaging Insights.
2. Take steps to protect your applications from abuse by following best practices in this SMS Traffic Pumping article, including turning off geo permissions for countries when not in use.

In order to provide additional information and transparancy around delivery timing we are adding a new parameter (RawDlrDoneDate) to Delivered and Undelivered status update webhooks for MMS and SMS messages. This parameter is a passthrough of the Done Date included on the DLR (Delivery Receipt) that we receive from our carrier partners. It takes the format of YYMMDDhhmm where:

YY = last two digits of the year (00-99)

MM = month (01-12)

DD = day (01-31)

hh = hour (00-23)

mm = minute (00-59)

Important notes on this data:

The format only includes minute level precision.

• The format does not provide timezone information. In practice, the timezone offset varies between carrier partners and even within the same carrier.
• Because of SMS/MMS signaling intricacies, not all messages will receive a RawDlrDoneDate in the Delivered or Undelivered status. Not all carrier partners offer DLRs and some messages go undelivered before a DLR is available.
• This parameter will also be added to Event Streams in the near future. Integrating with the parameter in event streams will require upgrading to a new schema version.
• The feature will be rolled out gradually. We expect the vast majority of Delivered/Undelivered messages to include the data by the end of February 2023.

It is strongly recommended that you use a Twilio provided signature validation library to verify the provenance of all webhooks arriving at your servers. The specific ordering and parameters included with each webhook depend on a number of factors and will evolve over time; thus it is important to follow the full specification of signature validation. This is already fully implemented and tested in the Twilio provided SDKs.

On Thursday, January 12th, 2023 at 9:00am PST, Twilio’s request to the webhook URL configured for a phone number will no longer contain the ReferralNumMedia property for SMS and MMS messages. This parameter is only relevant for WhatsApp messages generated from Meta’s “Click-to-WhatsApp” ads. It was previously incorrectly added to all messages, but will only be returned on WhatsApp messages going forward.

Twilio recommends that customers validate Twilio’s requests to their webhook URL by following this guide, making sure to pass all parameters sent to the webhook URL without filtering to the validateRequest call. Twilio strongly discourages validating based on the presence (or absence) of certain parameters.

Update: This is now completed. SMS and MMS messages will no longer have the ReferralNumMedia property sent to the SMS Webhook URL.

The change we announced in March 2022 to API response headers for all SMS and MMS messages sent via Twilio’s Messaging APIs has been canceled. The updates to our terms and policies, which were jointly announced with the potential pending content verification API response header change, are unaffected by this announcement and remain in effect.

Twilio continues to strive for high message deliverability and to keep consumers safe. Thank you for doing your part in promoting trusted communications by ensuring your compliance with Twilio’s Acceptable Use Policy and Messaging Policy and securing proper consent from senders and recipients before messages are sent.

Twilio has released changes to the US A2P 10DLC Campaign creation process in the Twilio API and Twilio Console to reflect the latest ecosystem guidelines. These changes include collection of new fields regarding user consent (e.g., opt-out keywords and auto-reply messages), as well as enforcement of length requirements to existing and new fields. Please read more about this change from the Twilio support article, and check out code samples and API guidelines from Twilio docs.