# Transactional SMS & Encoding
URL: /docs/guides/transactional-sms

> High-priority single and multi-recipient SMS dispatch, GSM-7 vs. UCS-2 segment billing, and Sender ID rules.

Use the transactional messaging endpoint (`POST /api/v1/public/sms/send`) for latency-sensitive notifications such as login alerts, payment confirmations, and order updates.

## Single vs. Multi-Recipient Dispatch [#single-vs-multi-recipient-dispatch]

The transactional endpoint supports **1 to 10 deduplicated recipients** per request via `to` (single MSISDN) or `recipients` (up to 10 numbers or comma-separated string).

```json title="Multi-recipient request body"
{
  "recipients": "+233241234567,+233501234567",
  "senderId": "SMSPRO",
  "message": "Order #4821 has shipped and arrives tomorrow.",
  "deliveryCallbackUrl": "https://myapp.com/webhooks/dlr"
}
```

<Callout type="info" title="Larger Audiences">
If you need to target more than 10 recipients in a single API call, use the asynchronous [Bulk & Campaign Messaging](/docs/guides/bulk-campaigns) endpoint (`/api/v1/public/sms/bulk/jobs`).
</Callout>

## Character Encoding & Segment Math [#character-encoding--segment-math]

Telco carriers bill SMS by **segment**. SMS Pro inspects your payload automatically and selects either GSM-7 or UCS-2 (Unicode) encoding:

| Encoding | Single Segment Limit | Concatenated Segment Size | Triggered By |
| :--- | :--- | :--- | :--- |
| **GSM-7** | `160` characters | `153` characters / part | Standard Latin letters, numbers, basic symbols |
| **UCS-2 (Unicode)** | `70` characters | `67` characters / part | Emoji, accented non-GSM characters, curly quotes |

Pre-flight character count and compliance checks are available via `POST /api/v1/public/sms/validate` and `POST /api/v1/public/sms/validate-recipients` before dispatching live traffic.

## Alphanumeric Sender IDs [#alphanumeric-sender-ids]

- Alphanumeric Sender IDs (`senderId`) support up to **11 characters** (for example `SMSPRO` or `CLINIC`).
- Ensure your Sender ID is registered and approved in the SMS Pro Dashboard before sending to carrier networks that enforce strict sender whitelisting.

## Polling Message History & Status [#polling-message-history--status]

- Query a single message by ID: `GET /api/v1/public/sms/messages/{messageId}`
- Paginate dispatch history: `GET /api/v1/public/sms/history`
- Filter by date range or status: `GET /api/v1/public/sms/history/search`