Create Sender ID

Request a new sender ID for your business. It's created as PENDING and becomes usable for sending once an admin approves it.

Four Types Supported

ALPHANUMERIC, DEDICATED, SHARED (letters/digits/spaces, 3–11 chars) or SHORT_CODE (3–6 digits).

Format Validated Up Front

Name length and character set are checked before anything is written — bad requests fail fast with a clear message.

Duplicate-Safe

Both exact and case-insensitive matches against your existing sender IDs return a 409 instead of creating a near-duplicate.

Starts PENDING

Every new sender ID is created PENDING. It becomes usable for sending only once approved.

Authentication Required

Use Basic Authwith the precomputed Base64 token from your dashboard, set in the `Authorization` header as `Basic <token>`.

POST

/v1/sender-ids

Core

Stable

Request Body

application/json

JSON

{
  "name": "YourBrand",
  "useCase": "Order confirmations and delivery updates for our e-commerce store.",
  "type": "ALPHANUMERIC"
}

Response

JSON

{
  "success": true,
  "message": "Sender ID created successfully",
  "data": {
    "id": "cmq804x70000avskxfqpc33yz",
    "name": "YourBrand",
    "useCase": "Order confirmations and delivery updates for our e-commerce store.",
    "type": "ALPHANUMERIC",
    "status": "PENDING",
    "createdAt": "2026-08-16T13:38:56.488Z"
  }
}

Try It Yourself

POST

https://api.sendexa.co/v1/sender-ids

Code Examples

Bash

curl -X POST 'https://api.sendexa.co/v1/sender-ids' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Basic YOUR_DASHBOARD_BASE64_TOKEN' \
  -d '{
    "name": "YourBrand",
    "useCase": "Order confirmations and delivery updates for our e-commerce store.",
    "type": "ALPHANUMERIC"
  }'

HTTP Status Codes

Code	Status	Description
201	Created	Sender ID created, status PENDING
400	Bad Request	Validation failed, or business ID missing from token
401	Unauthorized	Invalid or missing API credentials
409	Conflict	An identical or case-insensitive-matching sender ID already exists
500	Internal Server Error	Unexpected server error

Best Practices

Write a specific use case — vague descriptions slow down manual review
Poll the list endpoint or watch your inbox for the approval email rather than guessing when it's ready
Pick DEDICATED for a name only this business uses, SHARED if the same name spans multiple related businesses you operate
Store the returned id if you plan to edit the use case before approval