Alpha Sender ID
Request a custom alphanumeric sender ID to brand your outgoing messages.
An alpha sender ID lets you replace the default numeric sender with a recognizable name — for example, MyBrand instead of a phone number. Recipients see your name in the "From" field before they even open the message.
What qualifies as an alpha sender ID
- 1–11 characters
- Letters (
A–Z,a–z), digits (0–9), and spaces - Must not consist of digits only (that would be a numeric sender)
- Must represent your brand or organization name — generic or misleading names are rejected
How to request one
Request a sender ID from the dashboard: open Alpha Sender and choose Request Alpha Sender. Enter the exact name you want (up to 11 characters) and a short description of how you'll use it.
Sender IDs are set up free of charge once your organization sends 2,000 SMS a week. Until then, your request stays pending.
Sending while your request is pending
You don't have to wait. Pass your requested sender ID as from in any SMS API request right away:
curl -X POST https://api.moorsyl.com/api/sms \
-H "Content-Type: application/json" \
-H "x-api-key: sk_live_..." \
-d '{
"to": "+22236551999",
"from": "MyBrand",
"body": "Your order #1042 has been shipped."
}'While MyBrand is pending, the message is sent from the default MOORSYL sender, and the response includes a notice with the code SENDER_PENDING_APPROVAL. Once it's approved, the same requests go out as MyBrand automatically. No code changes needed.
A from value that was rejected, or that isn't on your account, is refused with a 400 BAD_REQUEST (SENDER_NOT_APPROVED).
Reasons a request may be denied
- The name is already in use by another organization
- The name is generic, misleading, or impersonates a third party
- The use case does not comply with Mauritanian telecommunications regulations
- Insufficient account information to verify ownership of the brand
If your request is denied, we'll explain the reason and, where possible, suggest an alternative. Questions? Email support@moorsyl.com.