Key authentication
Authenticate with an API key scoped to your account. Revoke or rotate a key from the panel at any time.
A JSON REST API for sending single or bulk SMS to Tanzanian numbers, with API-key authentication, per-message delivery status and signed webhooks.
Authenticate with an API key scoped to your account. Revoke or rotate a key from the panel at any time.
Submit one recipient or a batch in the same call and get a message id back for every accepted recipient.
Send under a registered sender ID rather than a shared number. We handle the registration for you.
Read per-message delivery status from the operator using the same message id returned at send time.
Register an HTTPS endpoint and receive a signed callback the moment a message is delivered or fails.
The API is plain REST and JSON, so it works from PHP, Laravel, Python, Node.js or a simple cURL request.
Need messages verified by regulators under your own name? See Sender ID Tanzania. Sending one-time codes instead of campaigns? See OTP SMS Tanzania.
The API reference is public and generated from the same document the API serves, so it always matches what the endpoints actually accept.
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.
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.
One published rate per message, and it is the same rate for every customer. Buying a hundred thousand credits costs exactly a hundred times what buying a thousand costs, so there is no volume tier to reach and no discount to negotiate. You buy credits up front, there is no line rental and no minimum spend, and credits never expire.
Get an API key, send a test message, and check the delivery status from the same account you use in the portal.