Skip to content

One API. Every channel.

Developer Hub – SMS, OTP, WhatsApp, RCS & Voice APIs

One REST API for SMS, OTP, WhatsApp, RCS and voice — with JSON requests, delivery webhooks and sandbox keys for testing.

  • DLT-ready onboarding
  • Real-time delivery reports
  • No setup fee

Priority routes

Fast, direct delivery

Live reports

Status for every message

API + panel

No-code or full API

Human support

Real people, fast replies

Overview

How the API works

All channels share the same pattern: create an API key in the panel, call the send endpoint over HTTPS with a JSON body, and receive a message ID. Delivery reports, read receipts and inbound replies are posted to a webhook URL you configure.

Because the pattern is the same, adding WhatsApp or RCS to an app that already sends SMS is mostly a change of channel and template, not a new integration.

Developers

Compliant by design

TRAI & DPDP aligned

Integration steps

  1. 1

    Get API keys

    Request access; sandbox and live keys are issued from the panel.

  2. 2

    Register templates

    DLT templates for SMS, Meta-approved templates for WhatsApp.

  3. 3

    Send a test message

    Call the send endpoint with a sandbox key and your own number.

  4. 4

    Set up webhooks

    Receive delivery status and replies at your HTTPS endpoint.

  5. 5

    Go live

    Switch to live keys and monitor traffic in the panel.

What you can do with the API

  • Send single or bulk messages on SMS, WhatsApp, RCS and voice
  • Send and verify OTPs with automatic channel fallback
  • Pass DLT entity and template IDs with each SMS
  • Receive delivery, read and failure events by webhook
  • Receive inbound WhatsApp and SMS replies
  • Query message status and download reports

Security

Requests are made over HTTPS only and authenticated with API keys that you can rotate or revoke from the panel. Keep keys on your server, never in a mobile or browser app, and restrict them by IP where possible.

Guides

Developers guides

Integration guides for each channel and common platforms.

SMS APISoon
WhatsApp API integrationSoon
OTP APISoon
WebhooksSoon
Code samples (PHP, Python, Node.js)Soon
FAQ

Developers FAQs

Is there a sandbox?+

Yes. Sandbox keys let you send test messages to your own numbers before going live.

Do I need separate integrations for each channel?+

No. The same API and webhook format is used for SMS, WhatsApp, RCS and voice; only the channel and template change.

How do I get delivery reports?+

Configure a webhook URL and we post a status event for each message. You can also query status by message ID.

Can I send SMS without DLT templates?+

No. In India every commercial SMS must match a DLT-registered template, and the template ID is sent with the request.

Start building

Request API access and we'll set up sandbox keys and share the API reference.