> ## Documentation Index
> Fetch the complete documentation index at: https://developer.zeckta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sender Names

> Register, manage, and use Sender Names for SMS messaging.

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:

```text theme={null}
ZECKTA
MyShop
AcmeBank
```

Sender Names help recipients recognize your brand, improve trust, and increase engagement.

***

## Supported Types

<CardGroup cols={2}>
  <Card title="Alphanumeric" icon="font">
    Brand-based identifiers such as <code>ZECKTA</code>, <code>MyShop</code>, or <code>AcmeBank</code>. Best suited for alerts, notifications, OTPs, and transactional messaging.
  </Card>

  <Card title="Numeric" icon="hashtag">
    Phone number-based identifiers used in regions where alphanumeric Sender Names are not supported or where two-way messaging is required.
  </Card>
</CardGroup>

***

## Sender Name Lifecycle

Every Sender Name follows an approval workflow.

```text theme={null}
PENDING
   ↓
APPROVED
```

or

```text theme={null}
PENDING
   ↓
REJECTED
```

### Statuses

| Status     | Description                   |
| ---------- | ----------------------------- |
| `PENDING`  | Awaiting review and approval. |
| `APPROVED` | Available for production use. |
| `REJECTED` | Request was declined.         |

***

## Requesting a Sender Name

Submit a Sender Name request for review and approval.

```http theme={null}
POST /v1/messaging/sender-names
```

### Request Body

| Field        | Type   | Required | Description                                      |
| ------------ | ------ | -------- | ------------------------------------------------ |
| `sender`     | string | Yes      | Desired Sender Name.                             |
| `purpose`    | string | Yes      | Description of how the Sender Name will be used. |
| `senderType` | string | Yes      | Type of Sender Name.                             |

### Supported Sender Types

| Type           | Description                                             |
| -------------- | ------------------------------------------------------- |
| `alphanumeric` | Brand-based Sender Name (e.g. ZECKTA).                  |
| `msisdn`       | Phone number-based Sender ID.                           |
| `shortcode`    | Short code assigned by a carrier or messaging provider. |

### Example Request

```json theme={null}
{
  "sender": "ZECKTA",
  "purpose": "Transactional alerts, account notifications, and OTP delivery.",
  "senderType": "alphanumeric"
}
```

### Example Response

```json theme={null}
{
  "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.

| Action             | Endpoint                                   |
| ------------------ | ------------------------------------------ |
| Create Sender Name | `POST /v1/messaging/sender-names`          |
| List Sender Names  | `GET /v1/messaging/sender-names`           |
| Get Sender Name    | `GET /v1/messaging/sender-names/{uuid}`    |
| Update Sender Name | `PUT /v1/messaging/sender-names/{uuid}`    |
| Delete Sender Name | `DELETE /v1/messaging/sender-names/{uuid}` |

***

## Sender Name Response Fields

| Field          | Description                                                         |
| -------------- | ------------------------------------------------------------------- |
| `senderNameId` | Unique identifier of the Sender Name.                               |
| `sender`       | Registered Sender Name.                                             |
| `senderType`   | Sender Name type.                                                   |
| `countryCode`  | Country or region associated with the Sender Name, when applicable. |
| `status`       | Current approval status.                                            |
| `statusReason` | Additional information about approval or rejection decisions.       |
| `submittedAt`  | Timestamp when the request was submitted.                           |
| `approvedAt`   | Timestamp when the Sender Name was approved.                        |

***

## Using a Sender Name

Once approved, the Sender Name can be supplied in SMS requests.

```json theme={null}
{
  "src": "ZECKTA",
  "dest": "+233240000000",
  "message": "Your verification code is 123456"
}
```

<Info>
  Only approved Sender Names may be used for message delivery.
</Info>

***

## 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.

<Warning>
  Using an unapproved Sender Name may result in message rejection, carrier filtering, or reduced delivery performance.
</Warning>

***

## Related Resources

<CardGroup cols={2}>
  <Card title="Send Single SMS" href="/messaging/send-single-sms">
    Send messages using an approved Sender Name.
  </Card>

  <Card title="Create Campaign" href="/messaging/create-campaign">
    Use Sender Names in bulk messaging campaigns.
  </Card>
</CardGroup>