Pre-check a carrier registration
Dry-run of POST /v1/sms/registrations for 10DLC. It returns the findings WITHOUT creating anything.
It does three things:
- Validates and composes the exact brand/campaign payloads a submission would store (branding, disclosures, auto-replies).
- Runs deterministic compliance lints over them.
- Runs an AI reviewer over them.
Use it to fix issues before submitting. block severity findings indicate a near-certain carrier rejection.
Authentication
API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
Body
application/jsonWhat every request needs
standard_10dlc | sole_prop_10dlcSame shape as the registration brand.
Same shape as the registration campaign.
Optional parameters2 fields
Responses
Success· the request worked
Errors· the request failed
List carrier registrations
Previous Page
Start a carrier registration
Starts the US carrier registration that a number needs before SMS delivers: 10DLC (standard company or sole-proprietor) or toll-free verification. - 10DLC needs `brand` + `campaign`. - Toll-free needs `tollFree`. Approval is asynchronous; poll `GET /v1/sms/registrations/{id}`. Sole-prop registrations first need the OTP step: a code is texted to the brand's mobile number, submit it via `/verify-otp`. ### Alternatives - Already have an approved registration? Add another number to it with `POST /v1/phone-numbers/{id}/sms/reuse-registration` instead of registering (and paying the carrier brand fee) again. - Rather have your client fill in the legal business details? Create a share link with `POST /v1/sms/registrations/share`.