SMS API for businesses in Kenya
No sender name needed to start
Send verification codes on Wingu Duck's registered sender name from day one. When you're ready to message customers under your own brand, apply for a sender name in the dashboard.
Your verification code is: 012345.
Do not share it with anyone.
Ref: wd_7K2A9xQm
What you can send
Both use the same API key and the same request shape.
OTP SMS
Send the code your app generated. It goes out on Wingu Duck's registered sender name, so there's no sender name to apply for and nothing to wait on.
POST /api/v1/sms/otpBulk SMS
Send promotional or transactional messages under your own brand. Apply for a sender name in the dashboard and start sending once it's approved.
POST /api/v1/sms/bulk-smsThe request
Send the code your app already generated to the number it already validated. Wingu Duck queues the SMS and replies straight away.
You get back
statusAlways "QUEUED". Delivery happens after the response.sms_message_idReference for this message, shown in the dashboard.wallet_transaction_idThe matching charge on your account.1POST /api/v1/sms/otp2apiKey: <YOUR_API_KEY>3 4{5 "appid": "<YOUR_APP_ID>",6 "phone_number": "+254712345678",7 "otp": "012345"8}The dashboard
Manage accounts, people and sender names in one place.
Run a separate account for each product or client, each with its own API key and sender names.
Invite teammates as Owner, Admin, Operations or Read-only, so everyone sees only what they need.
Apply for a sender name from the dashboard and follow its review until it's ready to use.
API keys are shown once and stored hashed. OTP codes are never logged in plain text.
How it works
Create an account in minutes. OTPs work as soon as you have credit.