Skip to main content

What You Can Do with the Unifier API

The HORISEN Unifier API lets you send and receive messages across multiple channels through a single interface — with built-in fallback routes, delivery tracking, and inbound message handling.

With the API, you can:

  • Send a message to a receiver on any supported channel, with one or more fallback messages if the primary channel fails.
  • Retrieve a previously sent message by its ID, including its sender, receiver, channel, and body.
  • Poll for the latest notifications — DLRs, inbound messages, and fallback events — across all channels.
  • Register a webhook to receive the same notifications pushed in real time instead of polling.
  • Download media files (images, audio, video, documents) delivered by inbound messages.
  • Look up available senders, filtered by one or more channel types.

Supported Channels​

RBM, SMS, Telegram, WhatsApp, Facebook and Instagram Messenger, and Email (outbound only).

Typical Use Cases​

  • Multi-channel notifications with fallback — try RBM first, for example, and fall back to SMS if the receiver doesn't have RCS.
  • Rich messaging — cards, carousels, WhatsApp templates, location, and contact messages, in addition to plain text.
  • Real-time delivery tracking — DLR and status updates via webhook, or by polling for updates.
  • Inbound conversation handling — receiving customer replies and downloading any media they send.

Authentication​

Every REST call, except your own webhook endpoint, must include the API key in the X-API-Key header. The key is the client_secret from your customer connection; some deployments also enforce an IP whitelist.

Quick Examples​

Send a Message with a Fallback​

curl -X POST "https://unifier.horisen.pro/v1/messages" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"message": {
  "sender": "SENDER_ID",
  "receiver": "+41790000000",
  "channel": "whatsApp",
  "body": {"textMessage": {"content": "Your order has shipped!"}}
},
"fallback": [
  {
    "sender": "SENDER_ID",
    "receiver": "+41790000000",
    "channel": "sms",
    "body": {"textMessage": {"content": "Your order has shipped! (SMS fallback)"}}
  }
]
}'

The response confirms which channel actually carried the message:

{
"message": {
  "msgId": "b1f6b8b2-6e7b-4a9a-9a3e-2f7e6a3c9b10",
  "channel": "whatsApp",
  "hasFallbacks": true
}
}

Poll for Notifications​

curl "https://unifier.horisen.pro/v1/updates?order=desc" \
-H "X-API-Key: YOUR_API_KEY"

Look Up Senders for a Channel​

curl "https://unifier.horisen.pro/v1/senders?channelType=whatsApp,sms" \
-H "X-API-Key: YOUR_API_KEY"

Receiving Notifications via Webhook​

Instead of polling for updates, register a webhook URL in your connection settings to receive the same Notification payloads pushed in real time. Each request carries an X-Msg-Api-Signature header (base64(SHA512(body + verifyToken))) so you can verify it was sent by the platform.

Technical Characteristics​

  • REST HTTP API with JSON payloads
  • API key authentication (X-API-Key header), with optional IP whitelisting
  • Multi-channel: RBM, SMS, Telegram, WhatsApp, Facebook and Instagram Messenger, and Email (outbound only)
  • Fallback message chains and rich message types (text, media, cards, carousels, templates, location, contacts)
  • Push notifications via signed webhook, or on-demand polling for updates