Skip to main content
A Sender Name (also known as a Sender ID) is the identifier displayed on a recipient’s device when they receive a message from your application. Examples: 
ZECKTA
MyShop
AcmeBank
Sender Names help recipients recognize your brand, improve trust, and increase engagement.

​
Supported Types

Alphanumeric

Brand-based identifiers such as ZECKTA, MyShop, or AcmeBank. Best suited for alerts, notifications, OTPs, and transactional messaging.

Numeric

Phone number-based identifiers used in regions where alphanumeric Sender Names are not supported or where two-way messaging is required.

​
Sender Name Lifecycle

Every Sender Name follows an approval workflow. 
PENDING
   ↓
APPROVED
or 
PENDING
   ↓
REJECTED

​
Statuses

StatusDescription
PENDINGAwaiting review and approval.
APPROVEDAvailable for production use.
REJECTEDRequest was declined.

​
Requesting a Sender Name

Submit a Sender Name request for review and approval. 
POST /v1/messaging/sender-names

​
Request Body

FieldTypeRequiredDescription
senderstringYesDesired Sender Name.
purposestringYesDescription of how the Sender Name will be used.
senderTypestringYesType of Sender Name.

​
Supported Sender Types

TypeDescription
alphanumericBrand-based Sender Name (e.g. ZECKTA).
msisdnPhone number-based Sender ID.
shortcodeShort code assigned by a carrier or messaging provider.

​
Example Request

{
  "sender": "ZECKTA",
  "purpose": "Transactional alerts, account notifications, and OTP delivery.",
  "senderType": "alphanumeric"
}

​
Example Response

{
  "success": true,
  "message": "Sender name submitted successfully",
  "data": {
    "senderNameId": "e4c5b85f-7db5-4a11-8dc1-c3b1d18a7f93",
    "sender": "ZECKTA",
    "senderType": "alphanumeric",
    "countryCode": null,
    "status": "PENDING",
    "statusReason": null,
    "submittedAt": "2026-06-09T18:00:00Z",
    "approvedAt": null
  }
}

​
Managing Sender Names

The Sender Names API allows you to manage Sender Names within your workspace.
ActionEndpoint
Create Sender NamePOST /v1/messaging/sender-names
List Sender NamesGET /v1/messaging/sender-names
Get Sender NameGET /v1/messaging/sender-names/{uuid}
Update Sender NamePUT /v1/messaging/sender-names/{uuid}
Delete Sender NameDELETE /v1/messaging/sender-names/{uuid}

​
Sender Name Response Fields

FieldDescription
senderNameIdUnique identifier of the Sender Name.
senderRegistered Sender Name.
senderTypeSender Name type.
countryCodeCountry or region associated with the Sender Name, when applicable.
statusCurrent approval status.
statusReasonAdditional information about approval or rejection decisions.
submittedAtTimestamp when the request was submitted.
approvedAtTimestamp when the Sender Name was approved.

​
Using a Sender Name

Once approved, the Sender Name can be supplied in SMS requests. 
{
  "src": "ZECKTA",
  "dest": "+233240000000",
  "message": "Your verification code is 123456"
}
Only approved Sender Names may be used for message delivery.

​
Workspace Isolation

Sender Names are isolated at the workspace level. A workspace can only:
  • View its own Sender Names
  • Update its own Sender Names
  • Delete its own Sender Names
  • Use Sender Names registered within the same workspace
Cross-workspace access is not permitted.

​
Compliance Requirements

Sender Name requirements vary by country, carrier, and destination network. To improve approval rates:
  • Use a name that clearly matches your business or brand.
  • Avoid impersonation of financial institutions, government agencies, telecom operators, or third parties.
  • Provide an accurate messaging purpose during registration.
  • Ensure your messaging activity complies with local telecommunications regulations.

​
Best Practices

  • Use a consistent Sender Name across your messaging campaigns.
  • Keep Sender Names short and easily recognizable.
  • Register Sender Names before launching production traffic.
  • Test delivery behavior in destination markets where possible.
Using an unapproved Sender Name may result in message rejection, carrier filtering, or reduced delivery performance.

Send Single SMS

Send messages using an approved Sender Name.

Create Campaign

Use Sender Names in bulk messaging campaigns.