ZAMBOX
Create accountSign in

OTP & transactional
messaging for Zambia.

Send secure login codes, payment alerts, order updates, and reminders to Zambian customers through SMS, WhatsApp, and email—from one API.

Built for +260 workflows/api/messaging/v1/
OTP requestPOST
/api/messaging/v1/sms/send
{
  "to": "+260•••••••••",
  "body": "Your login code is 482913. It expires in 5 minutes.",
  "metadata": {
    "purpose": "login_otp"
  },
  "webhook": {
    "url": "https://your.app/events"
  }
}

Illustrative payload. Use your approved sender identity and customer flow.

AcceptedExplore the API
Message switch
  1. Authenticate
  2. Validate
  3. Queue
  4. Route
Ready
01

SMS

/sms/send
Channel-native inputOTP · transaction alert · receipt
Normalized lifecycleSent · delivered · failed
02

WhatsApp

/whatsapp/send
Channel-native inputAuthentication template · utility update
Normalized lifecycleSent · delivered · read
03

Email

/email/send
Channel-native inputCode · HTML receipt · reply-to
Normalized lifecycleSent · delivered · failed
One return railDelivery webhooks
QueuedSentDeliveredReadFailed
ZMW usage billing

Prepaid wallet and per-send records

Sender identity

Use the approved SMS sender on your account

Delivery events

Status logs and optional HMAC signatures

Single or bulk

Send to 1–1,000 recipients per request

Zambia messaging demand18B

SMS messages were sent in Zambia during 2024, up 28.3% year on year.

Source: ZICTA 2024 Annual Market Report

For customer moments that cannot wait.

Zambox gives banks, fintechs, online stores, logistics teams, clinics, and schools one programmable path for urgent customer communication.

Banking & fintechLogin codes, payment confirmation, fraud and account alerts
CommerceAccount verification, receipts, orders, and collections
LogisticsDispatch, delivery windows, and proof-of-delivery updates
Health & educationAppointment, fee, attendance, and service reminders

One API for every critical update.

Use the same authentication, queued response, message lookup, delivery logs, and webhook rhythm across each channel.

  1. 01

    Secure sign-in

    Send short-lived login and account-recovery codes over SMS, WhatsApp, or email.

  2. 02

    Confirm payments

    Deliver transaction codes, receipts, and account alerts with a traceable message ID.

  3. 03

    Update orders

    Keep customers informed from checkout and dispatch through delivery.

  4. 04

    Send reminders

    Automate appointment, fee, renewal, and service reminders without manual follow-up.

Choose the channel the moment needs.

Use SMS for broad reach, WhatsApp authentication or utility templates for rich mobile updates, and email for detailed receipts and records.

View the channel schemas
SMS
OTPs · transaction alerts · order updates · reminders · approved sender identity+260 · body
WhatsApp
Authentication and utility templates · text · image · document · interactivemessage.*
Email
One-time codes · payment receipts · HTML body · plain-text fallback · reply-tosubject + html
Operational evidence

Know what happened after send.

Urgent messages need more than a 200 response. Inspect queue state, provider outcomes, delivery events, usage charges, and failure context from one organization-scoped record.

Queue control

Worker claim
Atomic and idempotent
Retry policy
Capped exponential backoff
Backpressure
Checked before bulk enqueue
Queue repair
Dry-run and bounded requeue

Delivery evidence

  • Queued

    Accepted for asynchronous delivery

  • Sent

    Accepted by the active provider

  • Delivered

    Provider confirmed recipient delivery

  • Failed

    Error and retry context recorded

Webhook security

webhook-idwebhook-timestampwebhook-signature

Add a secret to sign callbacks. Delivery attempts, HTTP outcomes, retries, and terminal state are persisted for diagnostics.

Message, usage, and webhook records stay scoped to the API key organization.
Zambia launch checklist

Build compliance into the message flow.

Zambox provides delivery and audit controls; your business remains responsible for its lawful basis, customer notices, retention, and channel approvals.

  1. 01
    Register data roles

    Confirm whether your business acts as a controller or processor with Zambia’s Data Protection Commission.

    DPC registration
  2. 02
    Separate OTP from marketing

    Use the correct lawful basis and honour opt-outs for direct marketing communications.

    Electronic communications law
  3. 03
    Approve sender identities

    Complete provider and network onboarding before using a branded SMS sender ID or shortcode.

    ZICTA shortcodes
  4. 04
    Review data transfers

    Assess cross-border processing before routing personal data through overseas WhatsApp or email infrastructure.

    Zambia Data Protection Act
Current default rate card

Usage pricing in Zambian kwacha.

Fund your organization wallet, send what you need, and inspect the exact unit rate recorded for every message.

SMS OTP & alerts

Automatic volume pricing

K0.25per segment to start
0–999
K0.25
1,000–4,999
K0.22
5,000–9,999
K0.18
10,000–19,999
K0.16
20,000+
K0.14

Monthly segment volume selects the rate automatically. Long or Unicode messages may use more than one segment.

Transactional email

Codes, receipts, and records

K0.02per email

HTML and plain-text bodies use the same metered email unit.

Meta WhatsApp

Category-based rates

Authentication
K0.55
Utility
K0.20
Marketing
K0.90

Rates shown are current Meta Cloud defaults per message. Provider and account pricing can differ.

Prices are current default ZMW sell rates. Your active organization rate card is applied at send time. Terminal provider failures are refunded; taxes or provider-specific charges may apply.

Open billing console

Put your first +260 OTP in the queue.

Start with the generated OpenAPI explorer, create an organization-scoped key, and integrate SMS, WhatsApp, or email without rebuilding your delivery lifecycle.

Create your accountExplore API docs