OneXtel adds WhatsApp, RCS and SMS as sendable channels inside WebEngage. Campaigns are built and
triggered in WebEngage, and every channel goes through the OneXtel connector on one host, which
translates each payload into a OneXtel message. On the way back, the connector turns every OneXtel
delivery report into a WebEngage Delivery Status Notification (DSN), with OneXtel’s code mapped
onto WebEngage’s status-code table.
Pick your channel once. The sections below have WhatsApp, RCS and SMS tabs.
Choosing a tab in any section switches every section on the page to that channel.
Scope
OutboundDelivery reportsSent, delivered, read and failed, with Meta’s and OneXtel’s failure codes mapped onto
WebEngage’s WhatsApp codes.InboundNot supported — see Limitations. OutboundDelivery reportsDelivered, read and failed, with operator and OneXtel failure codes mapped onto WebEngage’s
RCS codes.InboundNot supported — see Limitations. OutboundDelivery reportsSent and failed, with OneXtel’s India and international codes mapped onto WebEngage’s SMS
codes.InboundNot supported — see Limitations. Before you start
- A WebEngage account with the channels you intend to use enabled.
- A OneXtel account with those channels enabled, and an API key — see
API keys.
- Pre-approved templates in OneXtel. WhatsApp and RCS templates in WebEngage must replicate an
approved OneXtel template — see RCS templates and
WhatsApp templates. SMS templates must be
DLT-registered — see DLT registration.
- The WebEngage tokens for delivery reports, which WebEngage issues per channel and data
centre. OneXtel cannot issue them on your behalf.
- Your WebEngage data centre — India, KSA or US. Delivery reports must go to the data centre
your account lives in.
Connector endpoints
Replace <dc> with your WebEngage data centre — in, ksa or us. It decides where the
connector sends each report, so it must match your account.
The host is wen.onexaura.com. An earlier build ran on we.onexaura.com, which still answers
for WhatsApp and RCS sends but carries none of the delivery-report routes. Point every
configuration and callback at wen.
Which OneXtel gateway a send uses comes from the region header — IN or GLOBAL — on the
send configuration, not from the recipient’s number. Without it, sends go to India. Set
region: GLOBAL if your account sends outside India.
Never save a OneXtel callback with an empty header row. OneXtel then sends a header with no
name, and the connector’s web server refuses the whole request. If the callback form insists on
a header, add one named callback with the callback URL as its value — the connector ignores it.
Set up
Get your OneXtel API key
Log in to OneXtel, go to the API section, and click Show API Key. If no key
exists, click Generate API Key. Copy it.
Open the WhatsApp integration
In WebEngage, go to Data Platform → Integrations, scroll down, and click
WhatsApp Setup (Configure).
Configure a Private WSP
Scroll down and click Private WSP, then fill in the configuration popup:Add custom headers:Copy and paste the key rather than typing it. Save the configuration.The connector also accepts the key as Authorization: Bearer <key>, or as ?apikey= on the
URL if a form cannot set headers.
Use the phone number, not the WABA ID. OneXtel finds your WhatsApp account from the
business number. A WABA ID in this field is rejected as an invalid sender, which WebEngage
shows as 2004.
Register the delivery callback in OneXtel
In the OneXtel portal, go to Configuration → Add New Callback and add a callback against
the same API key:The connector maps each report and forwards it to WebEngage’s tracking endpoint for that
data centre. Hand the WebEngage WhatsApp token to OneXtel
Send omni.tech@onextel.com the WhatsApp delivery-report
token WebEngage issued for your account and data centre. OneXtel configures it on the
connector. WebEngage refuses WhatsApp reports without it, so nothing reaches WebEngage until
it is in place. Create a matching template
On the WhatsApp integration page, scroll to the Template section and create a template
that replicates one already approved in your OneXtel instance — same name, language, type
and number of variables. Save it.
Create the campaign
Go to the Channels tab, select WhatsApp, and create a new campaign. In the
Message tab, select the template and fill in its variables. Under Custom Key–Value
Pairs, add campaignName with a campaign identifier, so the campaign can be filtered in
OneXtel reporting. Optionally add custref3, custref4 and custref5 to carry your own
identifiers through to OneXtel.
Test before going live
Run a test send and confirm the message renders correctly, and that its delivery status
appears in WebEngage, before triggering the live campaign.
If your account was set up with WebEngage’s webhook registered directly at OneXtel, reports
still arrive, but with OneXtel’s raw codes rather than WebEngage’s. Change that callback’s URL
to the connector’s, as above, to get mapped codes.
Get your OneXtel API key
As above — API → Show API Key in the OneXtel portal.
Open the RCS integration
In WebEngage, go to Data Platform → Integrations, scroll down, and click
RCS Setup (Configure).
Configure a Private RSP
Scroll down and click Private RSP, then fill in the configuration popup:Add two custom headers:Save the configuration.Because campaigntype is set on the configuration rather than per message, you need a
separate Private RSP configuration for each RCS message type you intend to send.
Register the delivery callback in OneXtel
In the OneXtel portal, go to Configuration → Add New Callback and add a callback against
the same API key:See RCS delivery notification for what
OneXtel sends. Hand the WebEngage RCS token to OneXtel
Send omni.tech@onextel.com the RCS delivery-report token
WebEngage issued for your account and data centre, if it issued one. OneXtel configures it on
the connector. Create a matching template
On the RCS integration page, scroll to the template section and create a template that
replicates one already approved in your OneXtel instance. Save it.
Create the campaign
Go to the Channels tab, select RCS, and create a new campaign. In the Message
tab, select the template and fill in its variables. Under Custom Key–Value Pairs, add
campaignName with a campaign identifier, so the campaign can be filtered in OneXtel
reporting. Optionally add customRef3, customRef4 and customRef5 to carry your own
identifiers through to OneXtel.
Test before going live
Run a test send and confirm the message renders correctly, and that its delivery status
appears in WebEngage, before triggering the live campaign.
SMS sends go to the connector, which checks the payload and forwards it to OneXtel’s own WebEngage
endpoint — WebEngage’s payload as it is, India DLT fields included. On the return leg the connector
maps each OneXtel delivery report onto WebEngage’s SMS codes and forwards it to WebEngage.Part A — Add OneXtel as a Private SSP
Get your OneXtel API key
In the OneXtel portal, go to API and click Show API Key. Use the key your DLT
sender and templates are registered under.
Open the SMS integration
In WebEngage, go to Data Platform → Integrations → SMS Setup, and select
Private SSP from the list of available SSPs.
Configure the Private SSP
Add a custom header:Save the configuration.If your account is already configured with …/api/we, it keeps working — that is the same
route under its original name.
Set the India DLT details
In WebEngage’s India DLT settings, enter your principal entity ID, and set each
template’s DLT template ID. Add your telemarketer ID too if your route needs one.
WebEngage then sends every SMS with the DLT fields OneXtel needs.Store recipient numbers in WebEngage with the country code — 91XXXXXXXXXX. A ten-digit
Indian number is completed for you; see Indian numbers. Part B — Register the SMS delivery callback
In the OneXtel portal, go to Configuration → Add New Callback and add a callback against the
same API key you put on the Private SSP:The URL suffix is the only way the connector learns your data centre for SMS. Without it,
reports go to the India data centre. A region header on this callback is not read.
Part C — Hand over the WebEngage SMS token
Send omni.tech@onextel.com the SMS delivery-report token
WebEngage issued for your account and data centre. OneXtel configures it on the connector, and
reports for your data centre are held back until it is in place.Part D — Create the campaign and test it
Create the campaign
Go to the Channels tab, select SMS, and create a campaign against the Private SSP
from Part A. Write the message exactly as registered on DLT, and pick the template that
carries its DLT template ID.
Send a test
Send to a device you control and confirm the SMS arrives.
Confirm the delivery report
The message shows as sent in WebEngage’s campaign report. A failure shows with a WebEngage
code — see Error code mapping. Indian numbers
The connector completes a ten-digit Indian number in the 6–9 series to 91XXXXXXXXXX before
sending, so the number and the gateway agree. Anything else India cannot dial is refused by the
connector before it reaches OneXtel, in the channel’s own code: WhatsApp 2003, RCS 2021,
SMS 2003.
Numbers outside India are passed through as stored — 8 to 15 digits, with reachability left to
Meta or the operator. Send region: GLOBAL for those accounts, since the gateway comes from that
header rather than from the number.
This replaces older behaviour where a number stored without its country code was treated as
international, sent to the global gateway and refused there as an authorisation failure.
Error code mapping
Every report the connector forwards carries a WebEngage statusCode. Failures also carry a
message (WhatsApp and RCS call it reason) that ends with OneXtel’s original code — for
example [onextel=131026] — so the raw value is never lost.
Delivery reportssent, delivered and read are forwarded as whatsapp_sent, whatsapp_delivered and
whatsapp_read with code 0. A failure is forwarded as whatsapp_failed with the code below.For what each Meta code means, see WhatsApp error codes.Send repliesThe send route answers WebEngage straight away, with a code and the matching HTTP status: Delivery reportsdelivered and read are forwarded as rcs_delivered and rcs_read with code 0. A failure
is forwarded as rcs_failed with the code below. The operator’s “sent” event is not forwarded:
WebEngage’s RCS reports cover delivered, read and failed only.A code not in the table is classified by the operator’s wording, because Jio and Vi reuse the
same numbers for different conditions: RCS disabled or invalid number → 1001; DND, opt-out or
blacklist → 2025; expired or timed out → 2007; rate limited → 2014; template → 2023;
unauthorised → 2005; anything else → 9988. For what each operator code means, see
RCS error codes.Send replies Send repliesThe connector checks each send before forwarding it to OneXtel, and answers WebEngage with a code
and the matching HTTP status:Delivery reportsA delivered report is forwarded as sms_sent with code 0; every failure is forwarded as
sms_failed with the code below. India and international codes are both handled — see
India SMS error codes and
International SMS error codes.Not every report is a failure.
111 (delivery awaited) is not forwarded — the final report follows it.112, 994 and 900124 mean no final receipt arrived in time. They are sent as 9988 with
outcome unknown in the message, because the SMS may still have been delivered.
UNDELIV becomes 2009, anything else 9988. Limitations
All channels
- Inbound messages are not supported. Customer replies do not appear in WebEngage. If
two-way conversation matters, use the WhatsApp or
RCS APIs directly.
- Callbacks time out after 5 seconds and are retried up to three times. If the connector
does not acknowledge within that window, the callback is dropped rather than queued for later
redelivery.
- Templates are duplicated, not synced. A template created in WebEngage must manually
replicate one approved in OneXtel. If either copy is edited, they drift apart.
- Personalization variables only. The connector supports personalization variables and no
other variable form.
- Variable ordering is assigned by the connector. WebEngage does not send a variable index,
so the connector assigns positions when building the OneXtel payload. Verify order-sensitive
templates with a test send before going live.
- Reports need WebEngage’s WhatsApp token. Until OneXtel has it, WhatsApp reports are held
back.
- Templates are duplicated, not synced. A template created in WebEngage must manually
replicate one approved in OneXtel.
- Only template names and parameters are passed to OneXtel — the template body itself is
resolved on the OneXtel side.
- One Private RSP per message type, because
campaigntype is set on the configuration.
- India DLT traffic. The Private SSP sends to OneXtel’s India platform. For other countries,
confirm with your OneXtel account team before you set up.
- Delivery awaited is not reported. WebEngage sees a message only once it has a final
outcome.
- The data centre comes from the callback URL. Register a separate callback for each
API key, with the right
in, ksa or us suffix.
