A CPaaS (communications platform as a service) lets a business add messaging to its own apps and workflows through an API, without building carrier connections. BroadNet CPaaS covers six channels for enterprises, with white-label passthrough for resellers.
Six channels, one platform, one billing wallet.
WhatsApp, SMS, Telegram, Email, Instagram and Messenger — sent and replied to from a single REST API, a single dashboard, and a single pre-paid wallet. Four messaging workflows on every channel. One Omni Inbox for every reply. White-label passthrough for resellers.
Enterprises and resellers running multi-channel programs on BroadNet CPaaS
Send across SMS, WhatsApp and RCS in a few lines, then watch every reply land in a single threaded inbox. Below is an illustrative snapshot built from sample data.
Same request shape, whichever channel you route to.
curl -X POST https://api.broadnet.me/sms/sendSms \ -H "Authorization: Bearer $BROADNET_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "senderId": "BroadNet", "destinationNumber": "447700900123", "message": "Your verification code is 482913", "messageType": "TEXT" }' # 200 OK → response body is the message ID, e.g. 2603121407537573731One customer thread — SMS, WhatsApp and RCS in one place.
Illustrative example — sample conversation and code, not a live feed or an SLA.
The same workflow patterns across every channel — so engineering ships once, marketing learns once, support agents work from one screen.
One API across the six channels customers actually use.
Quick Send · Bulk · Personalized · Auto-Schedule.
Per-message template pricing across every market WhatsApp operates.
Every channel, every reply — one screen.
Auth, validation, workflow routing, channel adapter, response — the same five-stage pipeline regardless of whether the message is a WhatsApp template, an SMS, an Instagram DM, or a scheduled email.
REST submit, Bearer or OAuth 2.0 token, dedupe by message id on send. Test credentials to build against before production traffic.
Auth + schema validation, channel-specific template approval check, wallet balance + per-account TPS enforcement.
Quick Send · Bulk · Personalized · Auto-Schedule. Per-channel routing chooses the right provider and template format.
WhatsApp · SMS (HTTP / SMPP) · Telegram · Email (SMTP) · Instagram · Messenger — each via its native provider API.
Status events pushed to your webhook; inbound replies land in the Omni Inbox for agent response across every channel.
REST submit, Bearer or OAuth 2.0 token, dedupe by message id on send. Test credentials to build against before production traffic.
Auth + schema validation, channel-specific template approval check, wallet balance + per-account TPS enforcement.
Quick Send · Bulk · Personalized · Auto-Schedule. Per-channel routing chooses the right provider and template format.
WhatsApp · SMS (HTTP / SMPP) · Telegram · Email (SMTP) · Instagram · Messenger — each via its native provider API.
Status events pushed to your webhook; inbound replies land in the Omni Inbox for agent response across every channel.
Four reasons enterprises and resellers consolidate every channel onto BroadNet rather than running six different integrations.
We hold our own SMPP and SS7 binds with destination operators in 86 countries, and every other route is a labelled partner route. No grey routes, no surprise re-routing, no opaque price markups in the middle.
Operating since 2003, headquartered in Dubai. We carry 300M+ application-to-person messages a day for banks, governments, airlines, and the platforms that power the modern internet.
Local presence across the Middle East and North Africa, plus pan-African, South Asian, and South-East Asian operator relationships that make global rollouts feel like a single market.
ISO 27001 / 9001 / 22301, SOC 2 Type II, GSMA Associate Member, HIPAA-aligned, GDPR-aligned. Sender-ID registrations handled by an in-region compliance team in every regulated market.
Six channels
Template + session messages, media support, QR links — Marketing, Utility, Authentication, Service categories.
HTTP and SMPP. Bulk campaigns, DLR receipts, HLR lookup, Unicode + GSM encoding, global reach.
Text, voice, GIF, video, contact cards. Full inbound and outbound tracking with real-time costing.
SMTP and IMAP provider configuration, HTML templates, attachment support, bounce and open tracking.
Direct-message and comment replies, OAuth 2.0 page onboarding, full Meta integration for business pages.
Facebook Page integration via OAuth 2.0, bulk campaigns, personalized and auto-scheduled messaging.
Workflows × Channels
The same Quick Send, Bulk, Personalized and Auto-Schedule patterns work uniformly across WhatsApp, SMS, Telegram, Email, Instagram and Messenger. Learn the workflow once, use it everywhere.
One-to-one immediate message. OTP, transactional alert, agent reply.
Send to thousands of contacts from a segment, with full delivery reporting.
Variable substitution per contact — name, order, account — at bulk scale.
Queue messages for a future date / time. Supports one-time and recurring sends.
Omni Inbox
Customer support agents stop juggling six tools. WhatsApp, Telegram, Instagram, Messenger, Email and inbound SMS all land in the same threaded inbox with channel-aware composer. Assignment, tagging, and reporting work the same way across every channel.
WhatsApp pricing model
WhatsApp bills per delivered template message, with rates that vary by country and category. BroadNet exposes the full rate matrix to authorised admins so per-market pricing reviews are a one-screen exercise. Per-country rates are quoted privately on engagement.
Per-country rates available on engagement. Passthrough margin is configurable per sub-account for white-label resellers.
White-label · passthrough billing
A passthrough margin is added on top of base rates and charged to each sub-account automatically — fully configurable per client. BroadNet handles the wallet, the rate cards, and the provider integrations; your brand stays on the surface.
Audit-ready, regulator-recognised across MENA, deployable as managed cloud or white-label.
Pair with
The dedicated WhatsApp Business API page — template approvals, per-message pricing, official Meta BSP status.
Learn moreChannel-fallback orchestration. CPaaS gives you all six channels; Omnichannel decides when to use which.
Learn moreThe SMS-focused single-channel API for teams that just need direct enterprise SMS delivery.
Learn moreA Communications Platform as a Service exposes every customer-messaging channel — WhatsApp, SMS, Telegram, Email, Instagram, Messenger — through a single API, a single dashboard, and a single billing wallet. Instead of integrating six separate vendor APIs, learning six different authentication models, and reconciling six bills, you ship and operate one integration. The operational simplicity translates directly into lower engineering cost and faster time-to-market.
Three modes. Bearer system tokens for admin operations (onboarding, provider config). Bearer user tokens for day-to-day messaging, scoped per account and wallet. OAuth 2.0 for Instagram and Messenger — one-click Meta page connection, long-lived page tokens fetched and stored automatically. Test credentials come with test access and use the same API as production; request it and we reply within one business day.
Every channel supports Quick Send (immediate one-to-one), Bulk Campaign (segment broadcast with delivery report), Personalized (variable substitution per contact at bulk scale), and Auto-Schedule (queue for a future date or recurring). The same workflow signature works across WhatsApp, SMS, Telegram, Email, Instagram and Messenger. Learn the workflow once, use it everywhere.
Every inbound reply — WhatsApp message, Instagram DM, Messenger reply, Telegram message, email, inbound SMS — lands in a unified threaded inbox keyed per customer. Agent assignment, tagging, internal notes and reporting are channel-agnostic. The composer is channel-aware: it applies the right template, encoding and media rules per channel when an agent replies.
WhatsApp bills per delivered template message in three categories (Marketing, Utility, Authentication), with service replies priced separately, and rates that vary across every country WhatsApp operates in. The full rate matrix, covering 200+ countries, is exposed to admins. Per-country rates are quoted privately on engagement to keep the commercial conversation contextual to your traffic mix.
Yes. Passthrough margin is applied per sub-account on top of base rates and billed in the reseller's name. Wallets, role separation (reseller, admin, user), and webhook callbacks are scoped per sub-account. Reseller onboarding is a configuration exercise — not an engineering project — once the parent account is established.
Test access uses the same API and the same endpoint as production, so nothing in your integration changes at go-live. The difference is who you can reach: test messages go only to your own verified numbers, with delivery webhooks. Request test access and we reply within one business day. Integration typically takes 2–5 business days and approval 3–10 in parallel, so most accounts are live in 5–15 business days. Production traffic starts after approval, on your commercial terms.
Status events — submitted, sent, delivered, read, failed — and inbound messages are pushed in real-time to your configured webhook URL. Delivery is at-least-once, so acknowledge with an HTTP 200 and de-duplicate on the message id. Webhook URLs respond to a one-time verification challenge before going live; we do not push to unverified endpoints.
Question not here? Ask our engineering team
The same platform that carries 300M+ messages a day, available as building blocks for your stack.
Bring the customer journeys you want to run. We will scope the channel mix, the workflows, the Omni Inbox routing, and the wallet model — and send you test credentials to build against.
Go deeper on the concepts behind this product.