Messaging Overview
EnableX provides a comprehensive messaging platform that lets you reach customers across SMS, WhatsApp, and RCS channels through individual channel APIs or a single Unified Messaging API with intelligent fallback.
Integration Paths
EnableX offers two approaches to messaging integration:
| Approach | Description | Best For |
|---|---|---|
| Direct Channel APIs | Dedicated API per channel (SMS, WhatsApp, RCS) with full feature access | Single-channel use cases, maximum control over channel-specific features |
| Unified Messaging API | Single API endpoint with multi-channel orchestration, cascade fallback, and delivery optimization | Multi-channel campaigns, fallback delivery, cost optimization |
Channel Comparison Matrix
| Capability | SMS | RCS | |
|---|---|---|---|
| Base URL | api.enablex.io/sms/v1/ | api.enablex.io/whatsapp/v1/ | api.enablex.io/rcs/v1/ |
| Authentication | HTTP Basic, Bearer Token | HTTP Basic, Bearer Token | HTTP Basic, Bearer Token |
| Token Expiry | 60 minutes | 60 minutes | 60 minutes |
| Template Messaging | Via template_id | Pre-approved templates (text, rich media, interactive) | Pre-approved templates (text, card, carousel) — required in India |
| Session Messaging | N/A | 24-hour window after user reply | 24-hour window after user reply (India) |
| Rich Media | No | Image, Audio, Video, Document, Sticker | Rich Card, Carousel, Suggestions |
| Interactive Elements | No | Quick Reply Buttons, CTA Buttons, Lists | Suggested Replies, Suggested Actions (dial, URL, location, calendar) |
| Inbound Messages | Webhook | Webhook | Webhook |
| Delivery Reports | Webhook + Polling | Webhook | Webhook |
| Read Receipts | No | Yes | Yes |
| Regulatory | DLT (India), 10DLC (US), TCPA, country-specific | WABA approval, template approval | RBM Agent registration, template approval (India) |
Choosing Your Integration
| Scenario | Recommended Approach |
|---|---|
| Single channel (e.g., WhatsApp only) | Direct Channel API |
| Multi-channel with fallback | Unified Messaging API |
| Cost-optimized delivery | Unified API with preference: "budget" |
| Fastest delivery | Unified API with preference: "priority" |
| Broadcast to all channels simultaneously | Unified API with multi_channel_delivery: true |
| Rich interactive messaging | WhatsApp or RCS Direct API |
Getting Started
| Step | Action |
|---|---|
| 1 | Review Messaging Prerequisites for your target channel(s) |
| 2 | Create a project on the EnableX Portal and obtain APP_ID and APP_KEY |
| 3 | Configure webhooks for delivery notifications and inbound messages |
| 4 | Integrate using the channel-specific API or the Unified Messaging API |
API Reference Pages
| Channel | API Reference | Webhooks |
|---|---|---|
| SMS | SMS API | Included in SMS API page |
| WhatsApp API | WhatsApp Webhooks | |
| RCS | RCS API | RCS Webhooks |
| Unified | Unified Messaging API | Included in Unified API page |
Frequently Asked Questions
Which messaging channels does EnableX support?
EnableX supports SMS, WhatsApp Business API, and RCS (Rich Communication Services). All three channels are accessible through the unified Messaging API, and you can run multi-channel campaigns with automatic fallback routing, for example try WhatsApp first and fall back to SMS if undelivered.
Can I send WhatsApp messages through EnableX?
Yes. EnableX is a Meta Business Solution Provider and supports the WhatsApp Business API. You can send pre-approved message templates, interactive messages with buttons and lists, and rich media including images, documents, and videos.
What is RCS messaging and how is it different from SMS?
RCS (Rich Communication Services) is the next-generation messaging standard built into Android Messages. Unlike SMS, RCS supports branded sender identity, rich cards, carousels, suggested replies, read receipts, and high-resolution images with no app download required. EnableX supports RCS A2P messaging for Android devices.
Does EnableX support two-way SMS conversations?
Yes. Inbound SMS messages are delivered to a webhook URL you configure, enabling two-way conversational messaging. You can reply programmatically, route messages to agents, or trigger automated flows based on the message content.
How does fallback routing work in messaging campaigns?
In the EnableX Campaign tool, you configure a primary channel and up to two fallback channels. If the primary message is not delivered within a set timeout or is explicitly rejected, EnableX automatically attempts delivery on the next fallback channel. This maximises reach without manual intervention.
What compliance requirements apply to SMS messaging?
For India, SMS requires DLT registration where sender IDs and message templates must be pre-registered with a telecom operator. For the US, A2P 10DLC campaign registration is required. EnableX supports the required DLT template tagging and sender configuration for compliant delivery.