API + Android Relay + Dashboard for reliable operational delivery with clear control.
Built first for OTP and operational notifications instead of early expansion into bulk messaging.
The relay app sends through your own SIM with clearer visibility into device, battery, and network state.
From queue to retry to sent/delivered to webhook, you see the path instead of guessing.
The same product serves the developer, operator, and customer without splitting the workflow across separate tools.
The problem is not only delivery. It is the lack of visibility across device, SIM, queue, and webhook lifecycle.
Some markets and operating models need more flexibility than a single external provider.
When the device fails, battery drops, or network is lost, the real reason disappears.
Queued states, retry attempts, and failure reasons must be visible to the customer and engineers.
Even after sending, you need to know what webhook was delivered and what was retried.
SMS Relay is explained as a clear system: account, device, API, then status flowing back to the dashboard.
Create an account and configure login, activation, and developer access.
Install the app, sign in, grant permissions, and choose the SIM or smart mode.
Send OTP or transactional SMS using a clean endpoint with headers and metadata.
Follow queue state, errors, and webhooks from the client dashboard or your own system.
Send and verify OTP with expiration, metadata, and fast integration.
Learn more →Order, invoice, booking, and operational alerts instead of mass marketing.
Learn more →Relay app sends through the SIM with foreground service and health monitoring.
Learn more →Client dashboard, devices, queue/retry, webhooks, and clear logs for developers and operations.
Learn more →Instead of a generic messaging platform, we provide an OTP-first and transactional-first system with better visibility into device, SIM, queue, and webhooks.
Show the customer the app, dashboard, and developer pages with a direct visual preview.
Login and quick setup
Analytics and operations follow-up
API docs and examples
Device and SIM monitoring
See device state, last seen, battery, network, and active SIM from one place.
HealthAuto or manual device/SIM routing with room for smarter policies later.
RoutingEvery message gets a clear lifecycle with retry reasons and timeline logs.
LifecycleSend events back to your system with retries and clear attempt logs.
IntegrationsDaily and minute limits, duplicate prevention, and suspicious activity control.
SafetyAccess tokens, snippets, Postman, clean JSON, and a strong day-one integration experience.
DocsClean Base URL, auth header, cURL/PHP/Node/Python/Flutter examples, webhooks, Verify OTP, and Postman inside the developers page.
{
"to": "+9639XXXXXXX",
"message": "Your OTP is 482913",
"type": "otp",
"device_strategy": "auto",
"webhook_url": "https://example.com/hooks/sms"
}
Not in the first version. The customer connects an Android device with their own SIM, and the platform handles routing, management, and observability.
The main focus is OTP and transactional messaging like password reset, alerts, invoices, and bookings—not mass marketing.
An account on the platform, an Android device, an active SIM, and a simple API or dashboard setup.
Yes. You can increase the number of devices from Subscription & Billing, and pricing is calculated by the selected plan and device count.
Not necessarily. You can start directly from the client panel, while ready-made examples are available for developers when API integration is needed.
WhatsApp