CPaaS Platform
One platform for every transaction
SMS, voice and OTP through a single integration — with the routing intelligence of a wholesale carrier underneath, not a reseller markup on top.
Request RatesOne API call, end to end
LIVE FLOWPOST /v1/messages
{
"to": "+2348012345678",
"from": "4GNET",
"text": "Your code is 482913"
}202 Accepted
{
"id": "msg_8f3a92",
"route": "direct",
"status": "accepted"
}
// webhook, seconds later:
{ "status": "delivered" }Three channels, one integration
Send SMS, place calls and run OTP flows from the same API and the same account — no juggling providers per channel.
Carrier-grade underneath
The same 200+ direct interconnects that carry our wholesale traffic carry your API calls. Route quality is the product.
Reporting you can act on
Per-message delivery status, per-destination performance and cost visibility — the data your growth and finance teams both need.
What is CPaaS?
A Communications Platform as a Service puts messaging and voice behind simple APIs, so your product team ships customer communication features without building telecom infrastructure. The difference between platforms is what sits underneath: ours runs on direct carrier routes across Asia and Africa, which shows up in your delivery rates.
Built for high-volume apps
OTT platforms verifying millions of users, fintechs confirming transactions, marketplaces updating orders — traffic like this needs corridor depth in exactly the markets where generic global platforms are weakest. If your users are in Nigeria, India, Pakistan, Bangladesh or China, that is our home ground.
Getting started
- Request API access through our sales team
- Integrate with SMPP or HTTP API — documentation and sandbox included
- Test against your real destinations before committing volume
- Go live with per-destination reporting from day one
Frequently asked questions
Is there a sandbox to test against?
Yes — API access comes with a sandbox and documentation, so your developers can integrate and test message flows before any commercial commitment. Moving to live traffic is a credential change, not a re-integration.
Can we start small and scale?
That is the intended path. Start with trial volumes on your real destinations, watch the per-destination reporting, and scale corridor by corridor. There is no minimum that forces you to commit before the routes have proven themselves.
Do you support delivery webhooks?
Yes — status callbacks post to your endpoint in real time: accepted, submitted to carrier, delivered, or failed with a reason code. The same events are available in reporting exports for reconciliation.
How is CPaaS priced?
Per-transaction, by destination and channel, on wholesale-derived rates — because the platform runs on our own interconnects rather than reselling another provider. Share your traffic profile and we will price it precisely.
Related services
Ready to get your traffic moving?
Test routes in days. Talk to our Hong Kong team about rates, corridors and integration.