messaging.twilio.com
POST /v1/Services/{id}/Compliance/Usa2p now requires PrivacyPolicyUrl and TermsAndConditionsUrl
Stopped workingSubscribe to messaging.twilio.comShare
On June 30, 2026, PrivacyPolicyUrl and TermsAndConditionsUrl became required parameters for POST /v1/Services/{id}/Compliance/Usa2p. Requests to create an A2P 10DLC campaign that lack these parameters fail during review. These calls have failed since that date.
Calls it hits
POST /v1/Services/{id}/Compliance/Usa2p
What to use instead of these calls
Include valid, publicly accessible URLs for PrivacyPolicyUrl and TermsAndConditionsUrl in your POST /v1/Services/{MessagingServiceSid}/Compliance/Usa2p requests.
In messaging.twilio.com's words
Starting June 30, 2026, PrivacyPolicyUrl and TermsAndConditionsUrl will be required fields when registering a new A2P 10DLC campaign via the Twilio Messaging REST API. Campaign creation requests that don’t include both fields will be rejected during campaign review.
Facts
- API
- messaging.twilio.com
messaging.twilio.com - Kind
- Behaviour change
- Announced
- April 6, 2026
- Takes effect
- June 30, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against messaging.twilio.com's own pages
Questions
When does this change take effect?
Calls to POST /v1/Services/{id}/Compliance/Usa2p on messaging.twilio.com stopped working on June 30, 2026.
What happens to calls after June 30, 2026?
They have failed since June 30, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.