|
11/21/2022 The planned Twilio Messaging API response header change previously described in this article has been cancelled. The updates to our terms and policies which were jointly announced with this API response header change remain in effect. |
In March 2022, Twilio updated 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).
API response headers for all SMS and MMS messages sent via Twilio’s Messaging APIs had planned to include the following language: “Message Submitted. Pending content verification for US/Canada destination numbers.”
These policy updates were jointly announced with changes to Twilio’s Messaging APIs’ response headers. Those API response header changes have been canceled. Our Messaging APIs response headers remain unchanged.
What do I need to do?
|
API response headers remain unchanged, so it is not necessary to modify your application code if you were planning to use the change to Twilio's Messaging response headers. |
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.
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.