Request a higher sender ID daily limit
Asks support to raise the workspace's daily sender-ID message cap. There is no self-serve raise: the request (desired cap + use case) is reviewed manually, usually within a business day.
API key authentication - use your Zernio API key as a Bearer token
In: header
Desired daily message cap. Must exceed the current cap.
Use case and audience (what you send, to whom, opt-in status).
10 <= length <= 2000Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.sms.requestSmsSenderIdLimitIncrease({ body: { requestedCap: 0, reason: 'string', },});console.log(data);{
"requested": true,
"requestedCap": 0
}{
"error": "string",
"type": "invalid_request_error",
"code": "string",
"param": "string",
"platform": "string",
"platformError": {},
"details": {}
}{
"error": "Unauthorized"
}Pre-check a carrier registration POST
Dry-run of `POST /v1/sms/registrations` for 10DLC: validates and composes the exact brand/campaign payloads a submission would store (branding, disclosures, auto-replies), runs deterministic compliance lints plus an AI reviewer over them, and returns the findings WITHOUT creating anything. Use it to fix issues before submitting; `block` severity findings indicate a near-certain carrier rejection.
Re-send the sole-prop OTP POST
Re-sends the sole-proprietor verification PIN to the brand's mobile number — use it when the original code expired or never arrived. Only valid while the registration is pending and awaiting its OTP; rate limited to one send per minute.