Update Sender ID

Edit the use case description on a sender ID while it's still under review. The name and typecan't be changed after creation.

PENDING Only

Only the use case can be changed, and only while status is still PENDING — name and type are fixed at creation.

Authentication Required

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

PUT

/v1/sender-ids/:id

Stable

Path Parameters

Parameter	Description
id	The sender ID's record id, from the create or list response

Request Body

application/json

JSON

{
  "useCase": "Order confirmations, shipping updates, and delivery notifications."
}

Response

JSON

{
  "success": true,
  "message": "Sender ID updated successfully",
  "data": {
    "id": "cmq804x70000avskxfqpc33yz",
    "name": "YourBrand",
    "useCase": "Order confirmations, shipping updates, and delivery notifications.",
    "type": "ALPHANUMERIC",
    "status": "PENDING",
    "updatedAt": "2026-08-16T14:02:11.000Z"
  }
}

Try It Yourself

PUT

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

Code Examples

Bash

curl -X PUT 'https://api.sendexa.co/v1/sender-ids/SENDER_ID_ID' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Basic YOUR_DASHBOARD_BASE64_TOKEN' \
  -d '{
    "useCase": "Order confirmations, shipping updates, and delivery notifications."
  }'

HTTP Status Codes

Code	Status	Description
200	OK	Sender ID updated
400	Bad Request	Validation failed, or the sender ID is no longer PENDING
401	Unauthorized	Invalid or missing API credentials
403	Forbidden	Sender ID belongs to a different business
404	Not Found	No sender ID with that id

Best Practices

Get the use case right the first time on create — this endpoint only helps once, before approval
If a sender ID was REJECTED, create a new one instead of trying to update the rejected record