Platform
One API, one dashboard, one bill for every message your product sends. Transactional email runs in production today. Marketing email, SMS, and WhatsApp are being built on the same surface, so your team learns one API and grows into the rest without changing vendors.
The same authentication, the same idempotent send, the same signed webhooks and one error shape. Learn it once for email and reuse it for every channel that follows.
Every message, across every channel, in one log. Open a send and read its whole story: what was delivered, what bounced, what was opened, and when.
Priced in Naira, billed on your normal card via Paystack or Flutterwave. No dollar invoices, no FX surprises, and no second vendor to reconcile.
Channels
Each channel reaches your customer where they are. All of them share the same integration, the same dashboard, and the same Naira bill.
The channel SendByte ships today. One POST request sends a receipt, a one-time passcode, a password reset, or an alert, with authentication, suppression, and per-domain reputation handled for you.
Typical sends: Receipts, one-time passcodes, password resets, statements, system alerts.
Brands, lists, segments and campaigns in the same dashboard as your transactional mail, but on a separate sending reputation. A newsletter that collects complaints cannot drag down the receipts and passcodes your product depends on.
Typical sends: Product updates, newsletters, lifecycle campaigns, segmented broadcasts.
Reach a phone when email is not enough. The same API and the same bill send one-time codes, delivery updates, and time-critical alerts over SMS across African networks.
Typical sends: One-time codes, delivery updates, payment alerts, appointment reminders.
Templated notifications and two-way conversations on WhatsApp, from the same send call your backend already makes, so a customer can get a receipt where they actually read it.
Typical sends: Order updates, receipts, reminders, and support replies over WhatsApp.
One integration
The send surface does not change per channel. The same key, the same idempotency, the same signed webhooks, and the same single error shape carry from email to whatever you send next.
Live today for transactional email. Marketing, SMS, and WhatsApp will follow the same request and response contract, so integrating a new channel is a new endpoint, not a new vendor.
import { SendByte } from '@sendbyte/node';
const sendbyte = new SendByte(process.env.SENDBYTE_API_KEY);
// Live today: transactional email.
const { id } = await sendbyte.emails.send({
from: 'PayLink <receipts@paylink.ng>',
to: 'amaka@halo.ng',
subject: 'Receipt for ₦45,000',
html: '<p>Payment received. Thank you, Amaka.</p>',
});curl -X POST https://api.sendbyte.africa/v1/emails \
-H "Authorization: Bearer $SENDBYTE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "PayLink <receipts@paylink.ng>",
"to": "amaka@halo.ng",
"subject": "Receipt",
"html": "<p>Payment received.</p>"
}'One request shape. One webhook contract. Every channel.
One dashboard
Today the log is full of email. As channels open, they land in the same view, filtered by channel, so support and engineering never learn a second tool.
Foundation
Adding a channel should not mean re-earning trust. Infrastructure, compliance, deliverability, and reliability are shared, so a new channel arrives production-ready.
Ingestion at the African edge and processing in African regions, for lower latency and data residency your procurement team can sign off on.
Data residency, retention controls, audit logs on every action, and a DPA when you need one. Compliance is in the core, not a bolt-on.
Seed inboxes at the providers your users actually use, per-domain reputation, and inbox-placement you can read in the dashboard.
Idempotent sends, replayable webhooks, real-time logs, and a sandbox that behaves exactly like production.
Send transactional email today, on a free tier with no card required, and get early access to marketing, SMS, and WhatsApp as they open.