Delete an alphanumeric sender ID
Deactivates the sender ID so it can no longer send. Re-creating the
same sender ID via POST /v1/sms/sender-ids re-activates it.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Sender ID resource id.
Response 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.deleteSmsSenderId({ path: { id: 'abc123', },});console.log(data);{
"deleted": true
}{
"error": "string",
"type": "invalid_request_error",
"code": "string",
"param": "string",
"platform": "string",
"platformError": {},
"details": {}
}{
"error": "Unauthorized"
}Get a carrier registration GET
Poll this for approval progress after starting a registration.
Appeal a rejected campaign POST
Appeals a rejected 10DLC campaign with the carrier registry. Only a registration that reached campaign creation can be appealed; a brand-level rejection should be fixed and re-verified instead. On success the registration returns to `pending`. Content rejections (e.g. an opt-in flow without a verifiable form link, or unrealistic samples) should be FIXED in the same call: pass the corrected `messageFlow` / `sample1` / `sample2` and the campaign is updated before the appeal is filed, so the reviewer sees the new content. The current content is on `GET /v1/sms/registrations/{id}` (`campaignContent`).