Changes to API response headers on Messaging requests (content verification for US/Canada traffic)

In March 2022, Twilio is making updates to our terms and policies to clarify that we will proactively identify and block SMS and MMS messages that are in violation of Twilio’s Acceptable Use Policy (AUP).

Starting April 12, 2022, API response headers for all SMS and MMS messages sent via Twilio’s Messaging APIs will include the following language: “Message Submitted. Pending content verification for US/Canada destination numbers.” This new language in the API response header refers to an automated content verification process to prevent non-compliant traffic being sent to the US and Canada. This content verification will not slow down the delivery of your messages.

As with other filtered messages, any messages that are blocked due to this filtering will be marked as “undelivered” with error 30007. For more details on filtering, see How Does Message Filtering Work?

What do I need to do?

We recommend that you review your current terms to confirm that your customer and recipient consents are adequate. If you are an Independent Software Vendor (ISV) providing messaging services to other businesses, we recommend you ensure that your customers reflect these changes with their recipients.

In terms of your application code, most customers will not need to do anything as a result of this change. However, if you have coded your application in such a way that a change to Twilio’s API response header might result in an error, please make sure your application is set up to expect the added language (described above) prior to this change going into effect on April 12, 2022.

If a message is identified and blocked as a result of Twilio filtering, that message will be marked with the “undelivered” status and error 30007. If you are seeing error 30007 on your messages, we strongly recommend you review our Messaging Policy and our AUP, and check out How do I prevent my Twilio messages from being filtered (blocked)? for additional guidance.

Have more questions? Submit a request
Powered by Zendesk