Error code
30713: Invalid Vetting Token
What this error means
The external vetting token you attached to the brand is expired, malformed, or belongs to a different brand.
Causes, most likely first
- Token expired.
- Token truncated or reformatted on paste. Campaign Verify tokens are multi-field and pipe-delimited, so a clipped value fails validation.
- Token was issued for a different brand; a Campaign Verify token binds to exactly one brand.
Fields Twilio names for this error
Twilio’s page for this error names these submission fields:
VettingId
How to fix it
If your numbers are managed by a platform
If your numbers sit inside a reseller platform, for example LeadConnector numbers inside GoHighLevel, you do not have access to the Twilio Console, and the interface shows the rejection without the code. Ask that platform's support team for the Twilio rejection error code, in writing, before you change anything. You can also read it yourself from your browser, which is faster: see how to get the code.
The substance of the fix is yours to make: the business details, the website, and the opt-in flow described in the Twilio path all belong to you, not to the platform. Make those changes first, confirm they are live, then ask support to resubmit. A resubmission filed before the underlying facts change will fail again on the same reason.
If you own the Twilio account
Confirm the token belongs to this brand. If expired, request a new one from the vetting provider. Paste the full value verbatim, no reformatting. Via API, submit it as VettingId when creating the brand's Vettings subresource.
Timing and resubmission
Token validity is set by the issuing vetting provider, not Twilio. A new token means a new vetting request upstream.
Two ways forward
Have it handled for you
A2P registration is handled for you on Growth at $597/mo and on Scale at $1,197/mo. Registration, resubmissions, and the compliance work behind them are included.
Fix it yourself
Send your email and we will send the fix playbook for registration rejections.
Verified against Twilio documentation on 2026-08-10.