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

Guide · Nigeria

WhatsApp OTP API Nigeria

Deliver Nigerian one-time codes over WhatsApp Authentication with a copy-code button, over SMS, or both, from one API and one prepaid wallet. Nigeria WhatsApp OTP: 4 credits (₦24). Same keys and credits as OTP API and prepaid pricing.

Last updated: September 28, 2026

Why Nigerian OTP stalls on SMS only

Most Nigerian apps verify users with an SMS code at signup, login, and 2FA. When that code is the only path, three things break it: DND filters that treat a misclassified OTP as promotional traffic, a Sender ID that is not registered for the network the user is on, and a single delivery path with nothing else to offer when it goes quiet. The user does not wait. They bounce.

WhatsApp Authentication helps when your users live in WhatsApp and a code sitting in a chat with a copy-code button is easier than one buried in an SMS inbox. It is a second delivery path you choose deliberately, not a replacement for SMS. The SMS OTP API Nigeria guide covers the SMS side, including DND and routing.

WhatsApp OTP is delivery only

On Robase, WhatsApp is an OTP delivery channel and nothing more. Each code is sent as a WhatsApp Authentication template with a copy-code button; the template body is fixed and only the code travels. It is not a general WhatsApp chat or messaging API: no free-form messages, no marketing, no notifications. For receipts and alerts, use transactional SMS.

Workspace delivery modes

The workspace mode is the source of truth for which channel a code may use. Set it in Settings → General under OTP delivery. The default is sms, so an existing integration does not change behaviour until you opt in.

ModeBehaviourchannel on POST /v1/otp/send
smsSMS only. The default for every workspace.Omit it, or send "sms". "whatsapp" is refused.
whatsappWhatsApp only.Omit it, or send "whatsapp". "sms" is refused.
bothOne code on SMS and WhatsApp, both legs charged.Omit it. Naming one leg returns 400.
eitherChoose per request."whatsapp" for WhatsApp; omit it or send "sms" for SMS.

A channel the mode does not allow is an error, never a quiet switch to the other channel.

Pricing

One credit is ₦6. A Nigerian WhatsApp OTP is 4 credits (₦24); a Nigerian SMS OTP starts at 1 credit (₦6). Both draw on the same prepaid wallet as transactional SMS, with no monthly fee. On both, a code is charged for its SMS leg and its WhatsApp leg together. WhatsApp credits below are read from the whatsapp array on GET /v1/pricing, and only destinations priced there are listed.

For what SMS, WhatsApp, and both channels cost per Nigerian code, see WhatsApp OTP vs SMS OTP in Nigeria.

WhatsApp OTP destinationCodeCreditsNGN / code
Default*4₦24
NigeriaNG4₦24

Your first successful top-up adds bonus credits, once per account.Full SMS and WhatsApp tables on the pricing page.

Developer path

Same two calls as SMS OTP: POST /v1/otp/send then POST /v1/otp/verify. Auth is Authorization: Bearer robe_.... Use an E.164 Nigerian number such as +2348012345678 and pass "channel":"whatsapp" on a workspace in whatsapp or either mode. The send response carries an id; verify it as otp_id exactly as you would an SMS code.

  • On either, omit channel (or send "sms") for SMS.
  • On both, omit channel. Naming one leg returns 400.
  • On sms, a request for "whatsapp" is refused rather than sent as SMS.

Send over WhatsApp: POST /v1/otp/send

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: POST /v1/otp/verify

curl -X POST https://api.robase.dev/v1/otp/verify \
  -H "Authorization: Bearer robe_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"otp_id":"<id from the send response>","code":"123456"}'

SDKs

  • Node.js: @robasedev/sdk (npm install @robasedev/sdk)
  • Go: github.com/mantissatech/robase-sdk-go (go get github.com/mantissatech/robase-sdk-go)
  • PHP: robase/sdk (composer require robase/sdk)

Official SDKs are Node.js, Go, PHP. There is no public Python SDK. The full WhatsApp OTP setup, request shapes, and errors are in the WhatsApp OTP docs and the API docs.

No silent WhatsApp to SMS fallback

A failed WhatsApp leg is refunded and reported as failed. Robase never quietly re-sends the code as SMS, and a destination that cannot be priced for WhatsApp is refused before anything is charged. If you want SMS as a second attempt, make that an explicit request from your app, or use both mode and pay for both legs up front.

Transactional SMS on the same keys

Order confirmations, receipts, and alerts use the same robe_ keys and prepaid balance through POST /v1/sms/send. The Transactional SMS API Nigeria guide covers that path, and the SMS API in Nigeria page covers networks, Sender IDs, and NCC notes.

Send: POST /v1/sms/send

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

Compare and keep reading

See how prepaid credits compare in our Nigeria provider comparison and global provider comparison. The OTP API page covers SMS and WhatsApp OTP together, and WhatsApp OTP API for Africa on the blog explains the launch.

FAQ

How much does a WhatsApp OTP cost in Nigeria compared with SMS?

A Nigerian WhatsApp OTP is 4 credits (₦24) per code, read live from the whatsapp array on GET /v1/pricing. A Nigerian SMS OTP starts at 1 credit (₦6). Both come out of the same prepaid wallet, and one credit is ₦6.

Which OTP delivery modes can a workspace use?

Four: sms (the default), whatsapp, both, and either. You set the mode in Settings, General. On either, each request picks with the channel field and omitting it sends SMS. On both, every code goes over SMS and WhatsApp and you omit channel; naming one leg is refused with a 400.

If WhatsApp delivery fails, does Robase resend the code over SMS?

No. There is no silent WhatsApp to SMS fallback. A failed WhatsApp leg is refunded and reported as failed, so your app decides what to do next, for example offering the user an SMS code with an explicit request.

Is Robase a WhatsApp messaging API?

No. WhatsApp on Robase is OTP delivery only: a WhatsApp Authentication template with a copy-code button. You cannot send free-form WhatsApp chats, marketing, or notifications through it.

Which SDKs can I use to send a WhatsApp OTP?

Official SDKs are Node.js (@robasedev/sdk), PHP (robase/sdk), and Go (github.com/mantissatech/robase-sdk-go). There is no public Python SDK. All three wrap POST /v1/otp/send and POST /v1/otp/verify with robe_ API keys.

Is there a public email API or Python SDK?

No. Robase is SMS OTP, WhatsApp OTP delivery, and transactional SMS. There is no public email API and no Python SDK on PyPI.

Is there a free trial?

No. You pay as you go, and creating an account is free. Your first successful top-up adds bonus credits, once per account.

Send your first WhatsApp OTP

Sign up, top up, grab a robe_ key from robase.dev/app, set OTP delivery in Settings, and send a Nigerian code over WhatsApp for 4 credits (₦24).Your first successful top-up adds bonus credits, once per account.