--- title: "CPaaS platform: one API for messaging and voice" description: "A CPaaS platform from BroadNet: WhatsApp, SMS, RCS, Messenger, Instagram, Telegram, email and push through one REST API, plus voice, webhooks, SMPP and an SDK." canonical: "https://omnichannels.ai/cpaas/" language: "en" updated: "2026-11-04" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" --- # CPaaS platform: one API for messaging and voice Canonical: https://omnichannels.ai/cpaas/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies OmniChannels.ai is the CPaaS platform of BroadNet Technologies, in business since 2003. Build WhatsApp, SMS, RCS, voice, social, email and push into your product with one API, or run them from a shared inbox. **Short answer:** CPaaS (communications platform as a service) lets developers add messaging and voice to their own software through APIs instead of building carrier connections. OmniChannels.ai is BroadNet's CPaaS: one REST API with about 330 documented paths covers WhatsApp, SMS, RCS, Messenger, Instagram, Telegram, email and push, voice is provisioned by our engineers, with webhooks, SMPP, an SDK, an MCP server and channel fallback. ## What the OmniChannels.ai CPaaS includes - **REST API and OpenAPI 3.1:** About 330 documented paths covering SMS, WhatsApp, RCS, Messenger, Instagram, Telegram, email and push, described in an OpenAPI 3.1 specification. - **Nine channels, one platform:** WhatsApp Business API, SMS, RCS, voice, Facebook Messenger, Instagram, Telegram, email and push notifications. - **Webhooks for delivery statuses:** Statuses (SUBMITTED, SENT, DELIVERED, READ, FAILED, REJECTED) and inbound messages arrive on your webhook URL in one normalised format. - **Channel fallback:** Send on one channel and fall back to the next, for example WhatsApp, then RCS, then SMS. The order is configured per use case. - **SMS over direct operator connectivity, plus SMPP:** A2P SMS over BroadNet's direct operator connectivity, and SMPP 3.4 over TLS with binds provisioned per account for high volume. - **SDK and MCP server:** A TypeScript SDK, @broadnet/cpaas-sdk, and an MCP server that lets AI agents call the platform. - **Shared inbox and campaigns:** The same channels are available to non-developers in the Omni Inbox and the campaign tools, so product and support teams share one platform. - **White-label for resellers:** Resellers get multi-tenant sub-accounts and a console, billing and reports carrying their own brand, plus a reseller API. ## CPaaS, UCaaS and CCaaS compared | Model | What it is | Typical user | Delivered as | |---|---|---|---| | CPaaS | Communications capabilities (messaging, voice, verification) that you embed in your own software | Developers and product teams | Best when messaging is part of your product or workflow. | | UCaaS | Ready-made team communication: calling, meetings and chat for staff | Employees inside a company | Best for internal collaboration. | | CCaaS | A contact centre: queues, agents, routing and reporting for customer service | Support and sales agents | Best for running a service desk. A CPaaS can supply the channels behind it. | ## How to choose a CPaaS provider 1. **List the channels you need today and next year:** Check that each one is supported through the same API, not only on a roadmap, and whether voice, RCS and social channels are included. 2. **Check network and registration support:** Ask how SMS is routed, whether direct operator connections exist in your countries, and who handles sender ID and WhatsApp registrations. 3. **Read the API documentation:** Look for an OpenAPI specification, SDKs, sandbox or dry-run options, webhook payloads, error codes and rate limits. 4. **Test delivery visibility and fallback:** Confirm you get delivery statuses per message, and that you can define a fallback order between channels. 5. **Verify security and compliance:** Ask for current certifications and attestations, data-protection terms and where data is processed. 6. **Understand the pricing model:** Compare how each channel is billed (per message, per session, per minute), what pass-through fees apply, and whether the final quote is confirmed in writing. See our pricing page. ## Is a CPaaS the right fit? ### A good fit when - You want to embed messaging, verification or voice in your own app, CRM or backend. - You need several channels through one integration and one webhook format. - You send high volumes and want SMPP or direct operator connectivity. - You resell messaging and need white-label sub-accounts. ### Good to know before you start - A CPaaS gives you building blocks. If you only need a ready-made team phone system, UCaaS is the closer fit. - Channels such as WhatsApp and RCS follow the rules of Meta and Google, and registrations and approvals are decided by them, not by us. - Teams without developers can use the shared inbox and campaign tools instead of the API. ## CPaaS questions ### What is CPaaS? CPaaS stands for communications platform as a service. It is a cloud platform that gives developers APIs for messaging, voice and verification, so they can add those features to their own software without building carrier connections. Common channels are SMS, WhatsApp, RCS, voice, email and push. ### What is the difference between CPaaS and UCaaS? CPaaS provides APIs you embed in your own software, mostly for communicating with customers. UCaaS is a finished application for staff communication: calling, meetings and team chat. CPaaS is built by developers, while UCaaS is configured and used as delivered. ### What is the difference between CPaaS and CCaaS? CCaaS is a complete contact-centre application with queues, agent desktops, routing and reporting. CPaaS supplies communication building blocks, such as channels and verification, that you assemble yourself. A CCaaS can use a CPaaS for its channels. ### What are examples of CPaaS use cases? Common examples are one-time passcodes, order and delivery updates, appointment reminders, marketing campaigns, WhatsApp customer service, voice IVR and in-app push notifications. All of them are triggered by your own systems through an API. ### How do I choose a CPaaS provider? Compare channel coverage, network and registration support, API documentation and SDKs, delivery visibility and fallback, security certifications, support quality and the pricing model. Test the API with a real use case before you commit. ### How is CPaaS priced? Providers usually charge per message or per minute by channel and destination, and sometimes add platform or seat fees. WhatsApp also carries Meta's own charges. We publish our SMS and WhatsApp list rates on the pricing page, and the final quote confirms the cost. ### Which channels does the OmniChannels.ai CPaaS cover? WhatsApp Business API, SMS (including SMPP 3.4), RCS, voice, Facebook Messenger, Instagram, Telegram, email and push notifications. The messaging channels are reached through the REST API, voice is set up with our engineers, and delivery statuses come back in one webhook format. ### Who is behind OmniChannels.ai, and is it certified? OmniChannels.ai is the platform of BroadNet Technologies, in business since 2003, serving more than 60,000 enterprises with direct connections to more than 1,000 operators and aggregators. BroadNet holds ISO/IEC 27001:2022, ISO/IEC 27018, ISO 9001:2015, ISO 22301 and SOC 2 Type II, and is GDPR compliant. Updated: 2026-11-04