Stop losing users to failed OTP delivery.
One SMS API for Africa.
Send one-time passcodes over SMS or WhatsApp and transactional messages over a single integration, with the same routing, automatic failover in supported markets, and prepaid credits. Priced routes for Nigeria, Kenya, Ghana, South Africa, the UK, Benin, Ivory Coast, and the US. Other destinations on request.
Cost per message depends on country and network. See live rates on the pricing page.+ VAT Pricing →
Your brand name on transactional SMS. OTP goes out under Robase sender names after your first top-up, so you don't need your own Sender ID for OTP.
Verify users
OTP API
One-time passcodes for login, signup, and 2FA over SMS or WhatsApp. Configurable length and expiry, per-phone rate limits, and prepaid credits.
Explore the OTP APINotify users
Transactional SMS API
Receipts, alerts, and order updates that arrive at their destination, with the same routing, failover, and credits as OTP.
Explore the SMS APIBy the numbers
OTP + SMS
One integration, two APIs
8
Priced markets with published credit costs
₦6+ VAT
Nigeria: 1 to 3 credits per message (network-dependent)
3
SDKs: Node.js, Go, PHP
Why Robase
Everything you need to send SMS
OTP or transactional, one API. Built by developers, for developers.
Multi-provider routing
Per-country route selection. Supported markets retry a fallback upstream if the primary fails.
One API for OTP + SMS
Send passcodes (SMS or WhatsApp) and transactional SMS through the same endpoints, keys, and credits.
Prepaid credits
Pay as you grow. Cost per message depends on country and network. No monthly fees, no surprise bills.
Webhooks & logs
Delivery events for every message (sent, delivered, failed) plus searchable logs.
Two endpoints
Ship in three lines
Send an OTP
POST /v1/otp/send { "phone_number": "+2348012345678", "code_length": 6 }
Send a transactional SMS
POST /v1/sms/send { "phone_number": "+2348012345678", "message": "Order #12345 shipped." }
FAQ
Questions, answered
Does Robase support transactional SMS as well as OTP?
Yes. Both use the same API, routing, failover, and credits: POST /v1/otp/send for one-time passcodes and POST /v1/sms/send for transactional messages.
How much does the SMS API cost?
Prepaid credits, from ₦6 per message in Nigeria, priced per destination country. Credits cover both OTP and transactional SMS. There is no monthly fee. Prices exclude VAT. VAT applies to the credit price. The processing fee is separate.
Which countries does Robase cover?
Prepaid routes are published for Nigeria, Kenya, Ghana, South Africa, the United Kingdom, Benin, Ivory Coast, and the United States. Canada and other +1 numbers stay deliverable on the rate table but are not marketed as extra coverage. Additional African destinations are added as priced routes on request.
How does provider failover work?
Supported markets have a primary and a fallback upstream. If the primary rejects or times out, the send is retried on the fallback in the same request. The UK and US routes are currently single-provider. Credits are refunded if every configured provider fails.
Do you have SDKs?
Yes. Node, Go, and PHP, plus a plain REST API you can call from anywhere.
Is there a free trial?
No. You pay as you go, and creating an account is free. Nigeria SMS from ₦6 + VAT. See all rates on Pricing. Your first successful top-up adds bonus credits, once per account.
Can my SMS show my brand name?
Yes. New workspaces send transactional SMS under their own approved sender ID. Custom sender IDs are available in selected markets. See Sender IDs in the dashboard for availability. Request your own sender ID any time from Sender IDs, after your first successful top-up. Approval usually takes 1 to 4 weeks. OTP uses Robase sender names.
Stop losing users to failed OTP delivery
Create a free account, then top up to use the OTP and transactional SMS APIs. Your first successful top-up adds bonus credits, once per account. Multi-provider failover is on by default in supported markets. No monthly commitment.
Last updated: October 9, 2026