SwalaSMS
Account verification
Confirm a phone number belongs to the person creating an account before you trust it.
OTP SMS
OTP SMS for applications and businesses in Tanzania
Send one-time verification codes to Tanzanian numbers through the same REST API used for bulk campaigns, with per-message delivery status.
Where OTP SMS fits
Login verification
Add a second factor to sign-in without building your own SMS delivery infrastructure.
Password reset
Send a reset code by SMS for users without reliable access to email.
Transaction confirmation
Confirm a payment or order with a code sent at the moment it happens.
Phone number verification
Verify a number is real and reachable before it's stored against an account.
Delivery status
Know whether a code actually reached the handset, through the API response or a signed webhook -- rather than assuming it did.
Integrate with the same API used for bulk SMS
There is no separate OTP product to learn -- send a single-recipient message through the standard SMS API and read its delivery status the same way a bulk campaign does.
Common questions
Do you have an API?
Yes, a REST API with JSON payloads and API-key authentication, plus signed delivery webhooks. It is documented interactively, and most teams have their first message sending within an afternoon.
How do I know a message was delivered?
Every message carries a delivery status returned by the mobile operator, visible per message in the portal, in reports, and pushed to your webhook if you use the API.
Send your first OTP message
Create a developer account, get an API key, and send a test verification code before you wire it into your app.