Send your first message in minutes: our API, SDKs and MCP

Adding SMS or OTP to a product should take an afternoon, not a sprint. The difference is almost always the tooling. Here is how we think about the developer side, and what is waiting when you start.

A REST API that reads the way you expect

One endpoint to send, clear JSON in and out, real HTTP status codes, and webhooks that tell you what happened to each message. You can send your first text with a single authenticated request and get a delivery receipt back without polling for it.

SDKs in the languages you already use

Nobody wants to hand-roll HTTP calls and auth logic. We publish libraries so you install a package, drop in your key, and call a method. That is the whole integration. The behaviour is the same across languages, so the code looks familiar whatever your stack.

Plugins when you would rather not write code

Running a store on WooCommerce, OpenCart, PrestaShop or Magento? Install the plugin, connect once with your Hellio login, and order updates and checkout OTPs start flowing without touching the API at all.

An MCP server for the AI tools you now use

This is the newer one. Our MCP server lets an AI assistant or agent talk to the platform through the Model Context Protocol, so a tool like Claude can check a balance, send a message or pull a report on your behalf, safely and only with your permission. As more work moves into AI assistants, your messaging comes along.

And SMPP when you need raw throughput

For high-volume senders who want a direct binding, we speak SMPP too, so you can plug straight into the same routes at scale.

The thread through all of it is the same: meet you where you already work. Start with the developer docs, send a test in minutes, and grow from a single call to millions of messages without ever changing providers.