OverviewProductsPlatformsAPI ReferenceResources
SMS

Pre-check a carrier registration

POSThttps://zernio.com/api/v1/sms/registrations/preflight

Dry-run of POST /v1/sms/registrations for 10DLC. It returns the findings WITHOUT creating anything.

It does three things:

  1. Validates and composes the exact brand/campaign payloads a submission would store (branding, disclosures, auto-replies).
  2. Runs deterministic compliance lints over them.
  3. Runs an AI reviewer over them.

Use it to fix issues before submitting. block severity findings indicate a near-certain carrier rejection.

Authentication

AuthorizationBearer tokenRequired

API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.

Body

application/json

What every request needs

registrationTypestringRequiredOne of standard_10dlc | sole_prop_10dlc
brandobjectRequired

Same shape as the registration brand.

campaignobjectRequired

Same shape as the registration campaign.

Optional parameters2 fields
phoneNumbersarray of strings
messagingBrandNamestring, max 60

Responses

Success· the request worked

Errors· the request failed

POST/v1/sms/registrations/preflight
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.sms.preflightSmsRegistration({  body: {    registrationType: 'standard_10dlc',    brand: {},    campaign: {},  },});console.log(data);
{  "composed": {    "brand": {},    "campaign": {}  },  "advisories": [    {      "field": "string",      "code": "string",      "concern": "string",      "severity": "block"    }  ],  "verdict": "pass",  "aiUnavailable": true}
OpenAPI specification
Was this page helpful?