OTP + transactional SMS

SMS API for Nigeria & Africa

Send receipts, alerts, and order updates — plus OTP — over one prepaid API. Priced routes for Nigeria, Kenya, Ghana, South Africa, the UK, Benin, Ivory Coast, and the US. Same keys and credits.

Sends default to the Sender ID Robase. RAlerts is a second preapproved ID you can pick.

OTP API · Nigeria OTP guide · Pricing · vs Termii · Docs

Send a transactional SMS

POST /v1/sms/send uses the same robe_ keys and prepaid credits as OTP. Official SDKs: Node, Go, and PHP. Get a key from the dashboard at robase.dev/app.

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

Dedicated coverage pages for Nigeria, Kenya, Ghana, and South Africa. The UK and US are priced routes on the same API — see pricing.

SMS API coverage FAQ

Which countries does the Robase SMS API support?

Prepaid routes are published for Nigeria, Ghana, Kenya, South Africa, the United Kingdom, the United States, Benin, and Ivory Coast. Dedicated coverage pages are available for Nigeria, Kenya, Ghana, South Africa, each with local networks, pricing, and compliance details.

Is it one API for every country?

Yes. One integration, one set of credentials, and one prepaid credit balance send OTP and transactional SMS to every published market. Only the destination number changes.

How does per-country pricing work?

1 credit = ₦6. Each message costs a number of credits based on the destination country — from 1 credit (₦6) in Nigeria. Credits are prepaid, never expire, and cover both OTP and transactional SMS.

Which Sender IDs can I use?

Sends default to the Sender ID Robase. RAlerts is a second preapproved ID you can pick. Both work for OTP and transactional SMS on the same prepaid credits.