💬 WhatsApp API @ Best Rate | Zero Setup Fee → 99.9% Uptime OTP Delivery — Try FREE Demo! 🏆 10,000+ Registered Businesses — 2,000+ Enterprise Clients Served 🚀 API Integration in Under 5 Minutes 🏅 Verified Business Badge with RCS Messaging 💬 WhatsApp API @ Best Rate | Zero Setup Fee → 99.9% Uptime OTP Delivery — Try FREE Demo! 🏆 10,000+ Registered Businesses — 2,000+ Enterprise Clients Served 🚀 API Integration in Under 5 Minutes 🏅 Verified Business Badge with RCS Messaging
DLT Registration Developers Api's
Talk to Sales: India 1800 102 1822
bulk sms call
Marketing automation connector

WebEngage + SMSGatewayHub: SMS, WhatsApp & RCS in every journey

Use SMSGatewayHub as the SMS, WhatsApp and RCS service provider inside WebEngage. One connector key, India DLT-ready SMS, your approved WhatsApp templates and RCS rich cards — with delivered, read and failed reports flowing straight back into WebEngage analytics.

Set up the connector How it works
3 channelsSMS · WhatsApp · RCS
1 keyone endpoint for all
Real-timedelivery & read reports
DLT-readytemplate & entity IDs

Live in four steps

No code. Everything is set up from your SMSGatewayHub profile and your WebEngage dashboard.

Create the connector key

Panel › My Profile › Connectors › WebEngage › Create connector key. Choose your WebEngage data centre.

Add your channel keys

Save your SMS API key (checked live) and RCS API key. WhatsApp uses the number you already connected.

Add SMSGatewayHub in WebEngage

In WebEngage › Integrations › Channels, add SMSGatewayHub as the SMS / WhatsApp / RCS provider and paste the key.

Send & track

Run a test campaign. Every message and its delivery status shows in your profile and in WebEngage reports.

SMSGatewayHub appears in WebEngage once WebEngage enables it for your account. Our team arranges this with WebEngage for you — contact us after creating your key.

Everything WebEngage sends, delivered

Built on WebEngage's provider specification for SMS (SSP), WhatsApp (WSP) and RCS (RSP).

SMS

  • India DLT: content template ID and principal entity ID sent with every message (payload v2.0)
  • Promotional, transactional / service and OTP routes, plus international
  • Unicode (Hindi and regional languages) detected automatically
  • Delivered / failed reports with SMS part count back to WebEngage
  • Clear reasons: DND, invalid number, sender or template blocked, low balance

WhatsApp

  • Your Meta-approved templates with variables
  • Image, video and document headers; personalised images and PDFs
  • URL buttons, coupon-code buttons and carousels
  • Delivered and read reports, failure reasons mapped to WebEngage codes
  • Opt-outs (STOP) respected automatically

RCS

  • Approved RCS templates: text, rich card and carousel
  • WebEngage parameters mapped one-to-one to template variables
  • Sender = your verified RCS agent (Bot ID)
  • Delivered / read / failed reports to WebEngage
  • Your existing RCS webhook keeps receiving every event

For developers

One static HTTPS endpoint for all three channels. WebEngage authenticates with your connector key as a Bearer token.

// WebEngage → SMSGatewayHub
POST https://www.smsgatewayhub.com/cpaas/webengage/send.ashx
Authorization: Bearer sghwe_…
Content-Type: application/json

{ "version": "2.0",
  "smsData": { "toNumber": "9198XXXXXXXX", "fromNumber": "STRIPL",
               "body": "Your order 1043 is confirmed - STRIPL" },
  "metadata": { "campaignType": "TRANSACTIONAL", "messageId": "we-123",
    "indiaDLT": { "contentTemplateId": "1107…", "principalEntityId": "1201…" } } }

// answer
{ "status": "sms_accepted", "statusCode": 0 }
ChannelPayloadReports to WebEngage
SMSsmsData v1.0 / v2.0 (DLT)sms_sent, sms_failed + smsCount
WhatsAppwhatsAppData.templateData (TEXT, IMAGE, VIDEO, DOCUMENT, CAROUSEL)whatsapp_sent, whatsapp_read, whatsapp_failed
RCSrcsData.templateData (TEXT, RICH_CARD, RICH_CAROUSEL)rcs_delivered, rcs_read, rcs_failed
DuplicatesThe same messageId is accepted once — WebEngage retries never send twice.
ErrorsWebEngage status codes: 2000 balance, 2003 number, 2004 sender, 2005 auth, 2006 DND, 2021-2023 template, 2024 opted out, 2026 DLT template blocked, 2015 throttling.

Questions

Anything else? Call +91 9907922122 or contact us.

Which channels can WebEngage send through SMSGatewayHub?

SMS (promotional, transactional and OTP routes, plus international), WhatsApp template messages and RCS template messages — all with one connector key from your profile.

Do delivery reports reach WebEngage?

Yes. SMS delivered / failed, WhatsApp delivered / read / failed and RCS delivered / read / failed are posted to WebEngage's tracking endpoint for your data centre (India, US or KSA), with WebEngage's own status codes.

Is it DLT compliant?

Yes. Use WebEngage's DLT fields on each SMS template; the content template ID and principal entity ID go out with every India SMS, exactly as approved on DLT.

Do I need WhatsApp or RCS to use it?

No. Turn on only the channels you use. SMS works with your existing SMS account; WhatsApp needs your WhatsApp Business number connected in the panel; RCS needs your verified RCS agent.

What does it cost?

There is no extra fee for the connector. Messages are charged at your usual SMSGatewayHub SMS, WhatsApp and RCS prices.

Is my data safe?

Your channel keys are stored encrypted, the connector key is kept only as a fingerprint, and every WebEngage request is checked against it. You can create a new key or remove it at any time.

Ready to connect WebEngage?

Create your connector key in two minutes — free, no code.

Open my profileCreate a free account