Twilio errors 30933 and 30934: the privacy and terms URLs your campaign API call now needs

Updated 2026-10-12 · by Hieu Tran, written with AI agents and checked against the sources below

From 30 June 2026, creating an A2P 10DLC campaign through Twilio's REST API requires two fields: PrivacyPolicyUrl (missing → error 30933) and TermsAndConditionsUrl (missing → 30934). Integrations written before that date, especially platforms that register campaigns for their own customers, fail until they collect and send both.

Free tool: Free rejection decoder: paste any provider's code or message, get the cause, the fix and a check of your site

Paste the rejection as you got it. The decoder maps 181 Twilio codes and three DCA reason lists to the cause and the fix, then checks your privacy policy, terms and opt-in form.

What changed

30933: the PrivacyPolicyUrl field was missing from the create-campaign request. It's not a content rejection; that's 30908 (policy provided but not compliant).
30934: the TermsAndConditionsUrl field was missing. Content problems with the terms are 30882.
Both must be valid, publicly accessible URLs for the business registering the campaign, not your platform's own policy if you register on a customer's behalf.

If you register campaigns for customers (ISV)

Add both URLs to your onboarding form and validate that they load over https without a login.
Send the customer's URLs, not yours: reviewers compare them with the brand's name and website.
Re-check the content too, so the next rejection isn't 30908 or 30882: the privacy policy needs a sentence that mobile numbers and SMS opt-in data aren't shared with third parties or affiliates for marketing; the terms need program description, message frequency, "Message and data rates may apply", HELP and STOP.
Update the failed campaign and resubmit; a new campaign is only needed if the use case or brand was wrong.

Free tool: Free rejection decoder: paste any provider's code or message, get the cause, the fix and a check of your site

Paste the rejection as you got it. The decoder maps 181 Twilio codes and three DCA reason lists to the cause and the fix, then checks your privacy policy, terms and opt-in form.

Did 30933 or 30934 hit your integration, and how do you collect each customer's privacy and terms URLs?

We're researching this problem and read every answer. Tell us what happened (4 short questions, no sign-up; AI tools help us read the answers).

More guides

10DLC campaign rejected? What the reason means, whatever your provider calls it