Public URL shortener rejected (Twilio 30892, 30963): use branded links
Short answer
Don't use bit.ly, tinyurl or other shared shorteners in samples or real messages, and use https:// everywhere. Full links on your own domain are safest. A short domain you own and use only for your own links, like go.yourbrand.com, is also accepted by most providers.
What you'll see
| Where | Code | Wording |
|---|---|---|
| Twilio (10DLC) | 30892 | “Campaign vetting rejection - Invalid Sample Message - Public URL Shorteners” |
| Twilio (10DLC) | 30963 | “Campaign rejected: public URL shortener detected in campaign” |
| Twilio (10DLC) | 30964 | “Campaign rejected: non-secured URL (http://) detected” |
| Twilio (toll-free) | 30449 | “Toll Free verification rejection - URL issues in sample message” |
| Bandwidth Proxy, Infobip | 6013 | Samples use a public URL shortener |
| The Campaign Registry | embeddedLinkSample | “public URL shorteners (e.g., bitly, tinyurl) are not accepted” |
Text in curly quotes is the provider's wording; the rest is our summary.
Why it happens
- A bit.ly, tinyurl, ow.ly or similar link in a sample.
- An http:// link.
- A link through a third-party redirect or tracking domain that hides the destination.
- A link to a different business's domain than the one registered.
How to fix it
- Replace shortened links with the full https:// URL on your registered domain.
- If you need short links, use a branded short domain you own and use only for your own links (CTIA allows a shortener on a domain and IP dedicated to the sender).
- Avoid redirect chains. T-Mobile warns multi-layer redirects may cause suspension.
- Check that every link in samples, the opt-in confirmation and the HELP reply opens a page of the same business.
What each rulebook says
- AT&T:
The practice of using public URL shorteners in bulk Messaging is prohibited
. - T-Mobile: public shorteners are
highly discouraged, and messages containing them may be subject to blocking
. - The Campaign Registry:
not accepted
. - CTIA: a shortener is acceptable only on
a web address and IP address(es) dedicated to the exclusive use of the Message Sender
.
Since September 15, 2026, Twilio treats 30963 and 30964 as fixable: correct every link and resubmit. HighLevel's help center still lists them as high risk and ineligible, so check what your platform shows.
Check before you resubmit. Every rejection costs days, and often another $15 vetting fee. Paste your description, message flow, samples and policy text into the free preflight check, or generate a consistent set with the campaign builder.
Frequently asked questions
Are branded short links allowed?
Yes, on a domain you own and use only for your own messages. Bandwidth, Sinch, Vonage and Telnyx explicitly allow them, and CTIA permits shorteners dedicated to one sender.
Can I resubmit after a shortener rejection?
At Twilio, yes: since September 15, 2026, 30963 and 30964 are eligible for correction and resubmission, and 30892 and toll-free 30449 are fixable too. Remove every public shortener and http:// link first.
Do shorteners matter after approval?
Yes. Carriers filter live traffic, and messages with public shorteners can be blocked even on an approved campaign.
Sources
- Twilio error 30892 (accessed 2026-10-03)
- Twilio error 30963 (accessed 2026-10-03)
- Twilio error 30964 (accessed 2026-10-03)
- Twilio error 30449 (accessed 2026-10-03)
- Twilio changelog: new error codes for TFV and A2P 10DLC registration (published 2026-08-06, effective 2026-09-15)
- The Campaign Registry: CSP API OpenAPI spec (accessed 2026-10-03)
- AT&T Code of Conduct for Short Code and 10-Digit A2P SMS (March 1, 2021 (latest found))
- T-Mobile Code of Conduct v2.2 (November 2020 (latest public))
- CTIA Messaging Principles and Best Practices (May 2023 (current))
- Bandwidth: Proxy Connector vetting rejection reasons (2026-03-17)
- HighLevel: A2P campaign rejections, required fixes and vetting errors (modified 2026-09-09)
Rules change often and providers sometimes disagree; where they do, this page says so. This is general information, not legal advice, and no one can guarantee approval. See the disclaimer.
Related problems
- Twilio 30893, 30538, 30499, 30911 · DCA 602, 603 · Proxy 6012-6014 · TCR SAMPLE_MESSAGESample messages rejected: how to write samples reviewers approve
- Twilio 30889 · DCA 601 · Bandwidth 3109Embedded link or phone number flag doesn't match samples (Twilio 30889, DCA 601)
- Twilio 30891, 30907, 30919-30922, 30473, 30489, 30526 · DCA 804, 807 · Proxy 1003 · TF 1201-1205Website rejected for A2P or toll-free: what reviewers need to see
The Approval Kit adds industry template packs, opt-in and policy page templates, and an agency checklist.