Mantissa Robase is a Mantissa product A Mantissa product mantissatech.xyz

SMS API · Kenya (KE)

SMS API in Kenya

Send OTP and transactional SMS to +254 numbers across Safaricom, Airtel, Telkom with delivery webhooks, and prepaid credits from ₦18 + VAT per message.

Kenya is one of Africa’s most digitally advanced markets, with mobile money and app-based services making phone verification and transactional alerts part of everyday flows.

Robase gives Kenyan developers one REST API to send SMS one-time passcodes and transactional notifications across every major network (Safaricom, Airtel, Telkom), with automatic failover in supported markets. You pay in prepaid credits (₦18 + VAT per message to Kenya, billed in a single balance that also works everywhere else Robase delivers) with no monthly fee.

Price / message

₦18 + VAT

3 credits

Dial code

+254

+254 712 345 678

Networks

Safaricom, Airtel, Telkom

Currency

Kenyan Shilling (KES)

Send an SMS to Kenya

Authenticate with a Bearer token and POST a +254 number and your message.

curl -X POST https://api.robase.dev/v1/sms/send \
  -H "Authorization: Bearer robe_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number": "+254712345678",
    "message": "Your order #12345 has shipped."
  }'

Verifying users? The same credentials power the SMS OTP API and the transactional SMS API.

Coverage across Kenya networks

Safaricom

Airtel

Telkom

Robase routes each message to Kenya by network. Supported markets also fail over to an alternate upstream when the primary is unavailable.

Sender IDs & compliance in Kenya

Kenya messaging is overseen by the Communications Authority of Kenya (CA). Yes. New workspaces send transactional SMS under their own approved sender ID, registered with the mobile operators. Kenya asks for your KRA PIN certificate and how users opt in, and approval usually takes about 4 weeks. OTP goes out under Robase sender names after your first top-up, so you don't need your own Sender ID for OTP. Robase routes transactional traffic on the CA-compliant paths so receipts, alerts, and OTPs are delivered promptly.

SMS API in Kenya: FAQ

How much does it cost to send an SMS in Kenya?

An SMS to Kenya costs 3 credits, about ₦18 + VAT per message. 1 credit = ₦6 + VAT, credits are prepaid with no monthly fee, and the same balance covers both OTP and transactional SMS.

Which Kenya networks does Robase reach?

Robase delivers across all major Kenya networks: Safaricom, Airtel, Telkom. Supported markets use multi-provider routing with automatic failover.

Can I send OTP and transactional SMS to Kenya from one API?

Yes. One integration, one set of credentials, and one credit balance send both one-time passcodes and transactional notifications to +254 numbers.

Do you support sender IDs and compliance in Kenya?

Yes. New workspaces send transactional SMS under their own approved sender ID, registered with the mobile operators. Kenya asks for your KRA PIN certificate and how users opt in, and approval usually takes about 4 weeks. OTP goes out under Robase sender names after your first top-up, so you don't need your own Sender ID for OTP. Robase routes transactional traffic on the CA-compliant paths so receipts, alerts, and OTPs are delivered promptly.

How fast can I start sending to Kenya?

OTP can go live in minutes: top up, get an API key from the dashboard, and POST a +254 phone number to /v1/otp/send with a Bearer token. Transactional SMS from a new workspace goes out under your own sender ID. Request your own sender ID any time from Sender IDs, after your first successful top-up. Approval usually takes 1 to 4 weeks. OTP goes out under Robase sender names after your first top-up, so you don't need your own Sender ID for OTP. SDKs are available for Node, PHP, and Go.