ZS-07 · Messaging API
OTP and transactional messaging API for Zambia
Zambox is the messaging layer behind the moments a customer cannot wait for: a login code, a payment confirmation, a dispatch notice, an appointment reminder. One API sends over SMS, WhatsApp and email, and returns the same normalised delivery lifecycle whichever channel carried the message.
Urgent messages need more than a 200 response, so queue state, provider outcome, delivery events, usage charges and failure context are all recorded against an organisation-scoped record you can inspect. Callbacks can be signed, and usage is billed in kwacha from a prepaid wallet.
- Runs at
- zambox.zambrite.com
- Built for
- Banks, fintechs, online stores, logistics operators, clinics and schools sending time-critical customer messages, and the developers integrating them.
- To start
- Create an account and generate an API key
- Payment
- Prepaid organisation wallet in kwacha, drawn down per message sent.
What Zambox does
- 01One API for SMS, WhatsApp and email, with a normalised delivery lifecycle
- 02Short-lived login and account-recovery codes on any channel
- 03WhatsApp authentication and utility templates
- 04Payment confirmations and receipts carrying a traceable message ID
- 05Delivery webhooks with HMAC-signed callbacks
- 06Idempotent queue claims, capped exponential backoff and backpressure checks
- 07Per-send usage and delivery records scoped to the API key organisation
- 08Single or bulk send, up to 1,000 recipients per request
- 09Generated OpenAPI explorer and published channel schemas
Who uses it
- Banking and fintech
- Login codes, payment confirmations, and fraud and account alerts.
- Commerce
- Account verification, receipts, order updates and collections.
- Logistics
- Dispatch notices, delivery windows and proof-of-delivery updates.
- Health and education
- Appointment, fee, attendance and service reminders.
How it works
- 01Create a keyRegister an organisation, generate a scoped API key, and work against the generated OpenAPI explorer.
- 02Send on any channelOne endpoint each for SMS, WhatsApp and email, taking channel-native input and returning a queued response.
- 03Watch what happenedDelivery webhooks, status logs and per-send usage records, with retries and terminal state persisted.
Common questions
- Which channels does Zambox support?
- SMS, WhatsApp and email from one API. WhatsApp uses authentication and utility templates; email carries HTML and plain-text bodies with a reply-to.
- How do we know a message was delivered?
- Every send moves through a normalised lifecycle — queued, sent, delivered, read, failed — reported through delivery webhooks and status logs, with error and retry context recorded.
- Are the webhooks secure?
- Callbacks can be signed with a secret, using webhook id, timestamp and signature headers. Delivery attempts, HTTP outcomes, retries and terminal state are persisted for diagnostics.
- Can we send in bulk?
- Yes, from one to a thousand recipients per request, with backpressure checked before bulk enqueue and a capped exponential backoff retry policy.
- How is usage billed?
- From a prepaid organisation wallet in kwacha, drawn down per message, with the exact unit rate recorded against every send.
Use Zambox, or have us build something like it
Zambox runs at zambox.zambrite.com with its own sign-up and its own pricing in kwacha. If your requirement is close but not the same, the team that built it takes on custom work.