Transactional SMS
Trigger event-driven messages from your backend: payment receipts, booking confirmations, delivery updates, account changes. UGX-billed, MoMo-funded, REST.
Every payment, booking and account change deserves a confirmation that lands instantly. Wesendall's API is shaped for those patterns first.
Median 3-5s delivery on MTN; 4-7s on Airtel.
Atomic wallet writes — concurrent receipt sends can't double-debit.
Refund-on-failure so transactional retries don't drain your balance.
Webhooks for downstream automation (retries, escalations, audit).
Features
Send confirmations the moment a payment lands in your system.
Prioritized routing for time-sensitive event-driven traffic.
Per-recipient status callbacks for retries and audit logs.
Track which API key sent which traffic for accounting + abuse detection.
Send transactional email from the same wallet — no extra integration.
Audit-exportable history meets Uganda Data Protection Act requirements.
FAQ
Transactional SMS is triggered by user actions — a payment confirmation, delivery alert, booking receipt. Bulk SMS is one-to-many marketing or operational broadcasts. Transactional traffic is usually time-critical and needs sub-10-second delivery; Wesendall routes both kinds.
We don't publish a hard SLA, but median delivery is 3-5 seconds on MTN, 4-7 on Airtel. Transactional and OTP traffic share the prioritized routing path.
Yes — messages go from a default short code. A registered sender ID makes it your brand name instead. Strongly recommended for receipts and account alerts (UGX 300,000 one-off on MTN and Airtel).
POST to /api/v1/sms/send with the recipient phone, your message, and the walletId. See /solutions/sms-api for the full integration walkthrough.