Submit or resubmit a toll-free number for verification (TFV)
Submit (or resubmit) the Toll-Free Verification form for a toll-free DID so the carrier can approve it for messaging — without an approved TFV, US / CA toll-free traffic is throttled or blocked with 30032 errors. Supply the messaging use case, a use-case summary, 1–5 sample messages, business identity (name, website, and either an EIN or a business registration number + ISO country), a contact email and E.164 phone, the opt-in type with 1–5 opt-in proof image URLs, and the expected monthly message volume. Samples are content-linted before submission, so disallowed-vertical content is rejected up front (422) instead of after a multi-day carrier review; political use cases additionally require a Campaign Verify token. Org-ownership is enforced per call so a sibling sub-org sharing the tenant schema cannot submit attestation against another org’s DID. Scoped on numbers:write (owner / admin).
Authorizations
Dashboard JWT token from Clerk
Path Parameters
Body
Toll-free messaging use case (from the carrier-approved use-case list, e.g. Customer Care).
40–500 character description of how the number is used.
40 - 5001–5 representative outbound messages the carrier will review.
1 - 5 elementsE.164 contact phone (e.g. +14155550123).
How subscribers opted in to messaging.
VERBAL, WEB_FORM, PAPER_FORM, VIA_TEXT, MOBILE_QR_CODE 1–5 HTTPS URLs to opt-in proof screenshots.
1 - 5 elementsExpected monthly message-volume band (e.g. "10,000").
US Employer Identification Number (xx-xxxxxxx). Supply this OR business_registration_number + business_registration_country.
ISO-3166 alpha-2 country of the business registration number.
Set true for political messaging; requires cv_token.
Campaign Verify authorization token (required for political use cases).