WhatsApp OTP API for Africa: SMS or WhatsApp, one prepaid wallet
Robase · 2026-09-22
Many users read a one-time code faster in WhatsApp than in SMS. Robase now delivers OTP over WhatsApp as well as SMS, on the same prepaid API and the same credit wallet.
This is OTP delivery, not a general WhatsApp messaging API. Codes use a Meta Authentication template with a copy-code button. You choose the channel per workspace (or per request), and you pay in credits.
What you get
- SMS OTP and WhatsApp OTP on
POST /v1/otp/send - Transactional SMS unchanged on
POST /v1/sms/send - One prepaid wallet (1 credit = ₦6)
- Dashboard control for how each workspace may send OTP
Set OTP delivery under Settings → General (also on post-signup setup and Getting started):
| Mode | Behaviour | | ---------- | --------------------------------------- | | sms | SMS only (default) | | whatsapp | WhatsApp only | | both | One code, SMS and WhatsApp together | | either | Pick per request with channel |
On either, omit channel to send SMS, or send "channel": "whatsapp". On both, omit channel. Naming one leg is refused so you are never billed for two when you asked for one. A failed WhatsApp leg is refunded and reported as failed; it is never silently re-sent as SMS.
Send and verify
curl -X POST https://api.robase.dev/v1/otp/send \
-H "Authorization: Bearer robe_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+2348012345678",
"channel": "whatsapp"
}'
Verify with the same otp_id as SMS. The code is never returned in the API response. Full field reference: Send an OTP.
Credits
SMS OTP still uses the published SMS rate for the destination. WhatsApp OTP uses a separate cost table (Meta authentication rate plus delivery fee), converted to Naira, then charged as cost + 20% in whole credits (minimum 1).
Live WhatsApp credit figures are on Pricing and GET /v1/pricing. Destinations without a WhatsApp cost row are not charged as free. They are refused until priced.
Your first successful top-up adds bonus credits, once per account. Listed SMS markets remain Nigeria, Ghana, Kenya, South Africa, the United Kingdom, Benin, Ivory Coast, and the United States. We do not publish a delivery-rate percentage.
When to use WhatsApp vs SMS
- Prefer WhatsApp when your users are active there and you want the copy-code button.
- Prefer SMS when the handset may not have WhatsApp, or your workspace must stay SMS-only for compliance.
- Use
eitherwhen your app decides per user. - Use
bothwhen you intentionally pay for two legs for the same code.
What to do next
- Confirm WhatsApp OTP is available on your workspace (Settings → OTP delivery).
- Send a test with
channel: "whatsapp"to a number you control. - Verify on the same
otp_id. - Check Pricing for WhatsApp credits before you scale.
Guides: OTP verification · Product page: OTP API