Slide
Book a Demo
30 min · Product walkthrough with our team
New: One API

One API key.
Every channel.

WhatsApp, SMS, RCS, Email, and Instagram behind a single request contract. Set a fallback chain once and stop building a separate integration, and a separate failure point, for every channel you ship.

Get your API keyRead the docs
Same API keySame scopesZero new infrastructure
POST /v1/messages/send
WhatsApp
SMS

A live look at fallbackChannels: WhatsApp goes undelivered, One API retries SMS automatically.

Six channels

Every channel behind one endpoint

The channel field decides which network handles delivery. The request shape never changes.

WhatsApp Business messaging

Template and session messages delivered over WhatsApp Business.

Unified endpoint

SMS

Transactional and promotional SMS with sender ID and route control.

Unified endpoint

RCS

Rich, branded messaging for RCS-capable Android devices.

Unified endpoint

Email

Templated transactional email with full merge-variable support.

Unified endpoint

Instagram messaging

Direct messages to customers who first reached out on Instagram.

Unified endpoint

Voice

Outbound and inbound calling, transcription, and recording.

Dedicated endpoint · same key
Why One API

Built for teams shipping on more than one channel

Everything you already have access to, reshaped around a single call.

One credential, one scope model

The same API key and the same channel scopes you already have (whatsapp:send, sms:send, and so on) work with One API immediately. Nothing new to provision.

Smart fallback routing

Set fallbackChannels once and One API retries the next channel automatically when the first one fails to deliver, no orchestration code on your side.

One contract instead of five

A single request and response shape for every channel, instead of five payload formats, five error conventions, and five sets of docs living in your codebase.

Faster to integrate

Wire up one endpoint and ship. Adding a new fallback channel later means adding one array entry, not writing a new integration.

A transparent delivery trail

Every attempt, successful or not, comes back in the attempts array so you can log exactly what happened without extra API calls.

Full channel power, still there

The unified endpoint sends messages. Campaigns, templates, and analytics still live in each channel’s dedicated API and dashboard whenever you need them.

The contract

One request. Read it once, use it everywhere.

POST https://slide.synquic.com/api/v1/messages/send

1

Send a simple WhatsApp template

terminal
curl -X POST https://slide.synquic.com/api/v1/messages/send \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+919876543210",
    "channel": "whatsapp",
    "template": {
      "name": "order_confirmation",
      "languageCode": "en",
      "variables": { "1": "John", "2": "ORD-12345" }
    }
  }'
2

Try WhatsApp, fall back to SMS automatically

terminal
curl -X POST https://slide.synquic.com/api/v1/messages/send \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+919876543210",
    "channel": "whatsapp",
    "fallbackChannels": ["sms"],
    "message": "Your order ORD-12345 has shipped!",
    "template": { "name": "order_shipped", "languageCode": "en" },
    "sms": { "senderId": "ACMEIN" }
  }'
3

The response, after the fallback fired

response.json
{
  "status": "sent",
  "channelUsed": "sms",
  "messageId": "sms_9f2a1c8e7b3d",
  "attempts": [
    {
      "channel": "whatsapp",
      "status": "failed",
      "error": "Template not delivered to this recipient"
    },
    {
      "channel": "sms",
      "status": "sent",
      "messageId": "sms_9f2a1c8e7b3d"
    }
  ]
}
Before and after

What changes when you switch

Without One API

  • Five separate integrations to build, test, and maintain
  • Five different request and response shapes to remember
  • Five independent failure points with no shared retry logic
  • You write and own the fallback logic yourself, per channel

With One API

  • One endpoint, one request contract, for every channel
  • One API key, the same scopes you already have
  • A fallback chain configured declaratively, not coded by hand
  • One attempts[] array tells you exactly what happened, in order
Questions

Frequently asked questions

No. It uses the exact same API key and the exact same channel-scoped permissions as every other endpoint. If your key already has whatsapp:send or sms:send, it works with One API today.

Ship every channel from one call

Get your API key and send your first message in minutes. No new infrastructure, no new invoice line.

Get your API keyRead the docs