MoEngage

​

Part A — Create the RCS sender and configure SMS

1

Get your OneXtel API key

In the OneXtel portal, go to API and click Show API Key. If no key exists, click Generate API Key. Copy it — you need it twice below.

2

Find your RCS sender profile

In OneXtel, go to Channels → RCS → Asset Management → Sender Profiles and note the sender profile you want to send from, along with its message type.

3

Add OneXtel as an RCS sender in MoEngage

In MoEngage, go to Settings → SMS & RCS, switch to the RCS tab, and click + Add RCS Sender.

Select OneXtel from the provider list.

4

Enter the sender details

Field	Value
Sender type	The message type this sender carries — Transactional or Promotional
Sender Name	Your sender name, suffixed with the message type
Sender ID	Your OneXtel sender profile, suffixed with the message type
API URL	https://mo.onexaura.com/moengage/rcs/outbound
Authorization	The API key from step 1. To add a TTL or SMS fallback, see the Authorization step below

MoEngage’s Sender type list offers a third option, OTP. RCS supports Promotional and Transactional only — do not create an OTP sender.

Both Sender Name and Sender ID must carry the message type as an underscore suffix:

Name_Promotional        SenderID_Promotional
Name_Transactional      SenderID_Transactional

Create one sender per message type. RCS templates in OneXtel are retrieved per message category, so you need a separate RCS sender for each message type you send — Promotional and Transactional. Each sender carries only the templates of its own type, which is why the type is encoded in the sender name.

Sender ID accepts either a single sender profile or a pool. A pool groups several sender profiles so OneXtel can distribute traffic across them.

If you use a pool, only templates assigned to that pool are available to it. Choosing a template that belongs to a different profile leaves the send with nothing to resolve against. Check which templates the pool carries before you build the campaign — see Sender profiles.

Save the sender. MoEngage then shows an Incoming Messages & Delivery callback URL — copy it, you paste it into OneXtel in Part D.

Copy this URL from your own provider screen. Do not retype it, and do not take it from a screenshot or another account’s setup. The host depends on which MoEngage region your account runs in — api-01, api-02, and so on. The screenshots in this guide show one region’s host, which will not be yours unless you happen to share it. A wrong region is accepted at save time and then silently never delivers a report.

Your host matches your dashboard. MoEngage runs six data centres, DC-01 to DC-06, and each pairs dashboard-0N.moengage.com with api-0N.moengage.com. An account that signs in at dashboard-03 has its callback URLs on api-03.

5

Create the fallback configuration in OneXtel (SMS fallback)

Go to the Fallback module, create a new configuration and give it a name. Add one fallback channel, SMS, with Mode Same Account. Leave its DLR URL at the default: the SMS receipt then follows the SMS callback on your API key (Part D). Save.

List only SMS. RCS is already the primary channel, so do not add RCS as a fallback channel. A configuration with RCS first and SMS second never reaches the SMS step: the failed RCS messages are marked failed and no SMS is sent, with no error anywhere.

OneXtel generates a Fallback ID — copy it, you need it in the next step.

6

Set the RCS sender Authorization value

The MoEngage RCS sender form has no fields for delivery or fallback settings, so everything beyond the API key is packed into its Authorization field as tilde-separated values. Use the shortest form that covers what you need:

You want	Authorization value
RCS only	<apikey>
RCS only, with a TTL	<apikey>~<ttl_Seconds>
RCS with SMS fallback	<apikey>~<ttl_Seconds>~<smsFallbackId>~<fallbackWaitTime_seconds>~<dltEntityId>

The fallback values are only needed when you want SMS fallback. Without it, <apikey>~<ttl_Seconds> is enough.For example, with SMS fallback:

QkLuVxXI~60s~0004d861-8a30-47c3-90d4-c06eb391ec3a~90~1101234567890123456

Value	What it is
apikey	The API key already configured for this provider
ttl_Seconds	How long operators keep trying to deliver the RCS message, in seconds with the s suffix — for example 60s. After this the message is marked failed. With fallback, see Choosing TTL and wait time
smsFallbackId	The Fallback ID from the previous step
fallbackWaitTime_seconds	How long OneXtel waits for an RCS delivery or failure report before sending the SMS, in seconds as a plain number — for example 90. Defaults to 30 if missing or not numeric
dltEntityId	The DLT principal entity ID the fallback SMS is registered under. Leave it off when template auto-match is enabled on the API key — see Template ID and entity ID

Why the entity ID goes here. MoEngage sends an RCS campaign’s fallback SMS inside the RCS request, and that request carries only the SMS sender, message, and DLT template ID. The request body you set on the SMS custom service provider, including its entityid, is not used for RCS fallback, and the RCS sender form has no other field that could carry it.

With fallback, the values must be in this order, separated by ~. There is no separate fallback section in the MoEngage form — this single field is the whole configuration, so a missing value or a wrong separator disables fallback silently. Only the last value, the entity ID, can be left off.

Template ID and entity ID. DLT-registered SMS in India needs both a template ID and an entity ID. You can leave both out only when template auto-match is enabled on your OneXtel API key: OneXtel then matches the SMS content against your registered DLT templates and fills in both IDs. In that case, drop the entity ID from the Authorization value and leave the SMS template ID empty in the campaign. Without auto-match, pass both, or the fallback SMS is rejected. Ask OneXtel support to enable auto-match for the API key.Choosing TTL and wait time. The two clocks start together at send time and do different jobs: TTL is the operator’s deadline to deliver the RCS message, and wait time is how long OneXtel waits for a delivery report before it sends the SMS. Fallback fires when the wait time runs out without a delivery report.

Setting	Example	What happens
TTL longer than wait time	90s TTL, 60 wait	The wait time overrides the TTL. The RCS attempt ends when fallback fires at 60 seconds, so the recipient does not get both the RCS message and the SMS
TTL at or below wait time	30s TTL, 60 wait	The RCS attempt stops at 30 seconds, but fallback still waits the full 60 seconds before the SMS goes out. The recipient waits for the whole wait time

With fallback, set the wait time to how long you are willing to wait for RCS. A TTL longer than that has no effect. See Fallback overview.

7

Add an SMS custom service provider in MoEngage (SMS fallback)

The campaign’s Use SMS as fallback option lists SMS senders from a separate MoEngage provider, so one must exist. Go to Settings → SMS & RCS, open the SMS tab, and click Add Custom Service Provider.

For RCS fallback, MoEngage does not call this provider or use its request body. The fallback SMS travels inside the RCS request, which is why its entity ID goes in the RCS sender Authorization value. The request body below applies to plain SMS campaigns sent through this provider.

Give it a name, and set Sender Name and Sender ID to match the values configured in OneXtel — the Sender ID must match exactly. Then set the API URL:

https://mo.onexaura.com/moengage/sms/outbound

8

Set the SMS provider request body (SMS fallback)

Set Method to POST, Body type to Raw, and paste:

{
  "key": "YOUR_API_KEY",
  "from": "YOUR_SENDER_ID",
  "to": "Moesms_destination",
  "body": "Moesms_message",
  "templateid": "Moesms_dltTemplateId",
  "entityid": "YOUR_DLT_ENTITY_ID"
}

The Moesms_ values are MoEngage macros and must be left exactly as written — MoEngage substitutes them at send time. Replace from with your OneXtel sender ID, and entityid with your DLT entity ID.If template auto-match is enabled on the API key, you can remove the templateid and entityid lines. OneXtel then matches the message content to your registered DLT template instead.

Save.

​

Part B — Create templates in MoEngage

Your money transfer of Rs. [custom_param] was successfully completed.
Transaction ID: [custom_param1]. Thank you for using our service.

Your money transfer of Rs. {{custom_param}} was successfully completed.
Transaction ID: {{custom_param1}}. Thank you for using our service.

​

Part C — Build the campaign

1

Create the campaign and select the template

Create or open the campaign in MoEngage and select your OneXtel RCS sender. Under Select template, choose the template you created in Part B. If the template has placeholders, MoEngage shows a field for each — fill them, using MoEngage personalization where the value varies per recipient. Media URLs can be personalised the same way.

2

Enable fallback on the campaign (SMS fallback)

Fallback is switched on per campaign, not globally. Tick Use SMS as fallback, then choose the SMS sender you created in Part A and enter the SMS template and message content. The DLT template ID can be left empty only if template auto-match is enabled on the API key.

3

Save without launching

Save the campaign, but do not launch it until the callbacks in Part D are in place — otherwise the delivery reports and button clicks from the first send never reach MoEngage.

​

Part D — Configure the callbacks before you send

1

Configure the delivery report callback

In OneXtel, go to Configuration → Add New Callback. Give it a title, set Channel to RCS and Callback Format Type to MoEngage, and select the same API key you used in MoEngage.Under Request Configuration, set Type to Delivery Notification and HTTP Method to POST, and enter this URL:

https://mo.onexaura.com/moengage/rcs/dlr

In the Header section, add the key callback with the MoEngage callback URL you copied in Part A as its value — the URL alone. Save.Do not paste the MoEngage URL into Callback URL directly. The report would bypass the connector, and you would have no record of what OneXtel sent.

2

Configure the button-click callback

Add a second callback with the same channel, format type, and API key. Set Type to Button click and HTTP Method to POST, and enter this URL:

https://mo.onexaura.com/moengage/rcs/inbound

In the Header section, add the key callback with your MoEngage DLR URL as the value — the same region-specific URL you copied from the sender screen, not one typed from this page.

3

Configure the SMS delivery callback (SMS fallback)

Add a callback with Channel SMS, the same API key and HTTP Method POST. The SMS callback form has no Callback Format field; it lists Default Parameters instead. The connector translates OneXtel’s SMS receipt into MoEngage’s format:

Field	Value
Callback URL	https://mo.onexaura.com/moengage/sms/dlr
Default Parameters	keep the defaults, and make sure custref1 is included
Header	key callback, value = the RCS callback URL from the RCS sender screen (Part A)

custref1 carries the reference of the RCS message the SMS replaced. Without it the connector cannot tell a fallback receipt from a plain SMS one, and the report never reaches the RCS campaign.

A fallback SMS is reported on MoEngage’s RCS contract, against the RCS message it replaced, so the header must carry the RCS callback URL — not the SMS provider’s. The connector recognises a fallback receipt by the reference it attached at send time and reports it as SMS_DELIVERED or SMS_DELIVERY_FAILED.

Plain SMS campaigns need the SMS provider’s URL in this same header. Because callbacks are set per API key, use separate API keys for RCS-with-fallback and for plain SMS campaigns.

​

Part E — Test, then launch

​

Part A — Add OneXtel as an SMS provider

1

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.

2

Add a custom service provider

In MoEngage, go to Settings → SMS & RCS, open the SMS tab, and click Add Custom Service Provider. Give it a name, and set Sender Name and Sender ID to match the values configured in OneXtel — the Sender ID must match exactly. Then set the API URL:

https://mo.onexaura.com/moengage/sms/outbound

3

Set the request body

Set Method to POST, Body type to Raw, and paste. MoEngage selects Form by default, so change it before you paste:

{
  "key": "YOUR_API_KEY",
  "from": "YOUR_SENDER_ID",
  "to": "Moesms_destination",
  "body": "Moesms_message",
  "templateid": "Moesms_dltTemplateId",
  "entityid": "YOUR_DLT_ENTITY_ID"
}

The Moesms_ values are MoEngage macros and must be left exactly as written — MoEngage substitutes them at send time. Replace key with your API key, from with your OneXtel sender ID, and entityid with your DLT entity ID.You can add these optional fields to the same body:

Field	Value	Notes
type	SI, OTP or SE	The DLT category your templates are registered under. Case-sensitive; defaults to SI
unicode	"1"	For messages with non-ASCII characters. Not detected for you
campaignName	"Moesms_campaignId"	Tags each SMS with the MoEngage campaign in OneXtel reporting
urlTracking	"1"	Turns click tracking on for this provider. Leave it out and your links are sent untouched

Keep every value in quotes. A DLT ID of 19 digits sent as a bare number is rounded before it arrives, so the connector refuses it with 7001 rather than send the wrong ID.

If template auto-match is enabled on the API key, you can remove the templateid and entityid lines. OneXtel then matches the message content to your registered DLT template instead.

The API key can go in an apikey header instead of the body, if your MoEngage form has a headers section. When both are set, the body wins.

4

Decide on click tracking

Click tracking is off by default. Your links are sent exactly as written unless you ask for tracking. Add "urlTracking": "1" to the request body to turn it on: OneXtel then rewrites every link in the SMS into its own short domain and counts the taps, which you see in OneXtel reporting.

Tracking is opt-in because the rewrite has consequences under DLT. Once it is on, the OneXtel short domain is the one that must be whitelisted on your DLT template, in place of your own link domain — so switching it on without updating the template registration gets the message rejected at scrubbing.

Values "1", "true", "yes" and "on" turn tracking on. Anything else, including a missing or misspelled value, leaves your links untouched. RCS messages and RCS fallback SMS are never shortened.

5

Tell MoEngage how to read the replies

In the provider’s delivery-tracking settings, map these attributes. MoEngage matches each delivery report to its message through the two ID fields, so both must be messageId:

MoEngage field	Value
Attribute storing unique ID of the sent response	messageId
Attribute storing Unique delivery ID field of delivery response	messageId
Attribute storing delivery status	status
Success values for delivery status	delivered
Attribute storing failure reason	errorCode

A send the connector or OneXtel refuses comes back as HTTP 401 or 400, with status set to failure and an errorCode from 7000 to 7004 — see Error code mapping.

6

Save, then copy the SMS delivery tracking URL

Save the provider. MoEngage then shows its SMS delivery tracking URL, of the form https://api-0N.moengage.com/sms/dlr/custom/<id>. Copy it — you paste it into OneXtel in Part B.

Copy this URL from your own provider screen. The api-0N host matches the data centre of your MoEngage dashboard, and the ID at the end belongs to the provider (connector): senders under one connector share it, but another connector in the same workspace has a different ID. A URL copied from another account or connector is accepted at save time and then silently never credits a report.

​

Part B — Configure the SMS delivery callback

​

Part C — Build the SMS campaign

​

Part D — Send a test SMS, then launch

• Inbound messages are not supported by MoEngage. Suggestion interaction callbacks are returned, but free-form customer replies cannot be surfaced in MoEngage.
• Only template names and parameters are passed to OneXtel — the template body itself is resolved on the OneXtel side.
• Audio and PDF are not supported by MoEngage on RCS.
• Carousel templates are not yet available — see Coming soon.

• Inbound SMS is not supported. Replies to an SMS are not relayed to MoEngage.
• India DLT traffic. The connector sends to OneXtel’s India platform. Numbers are passed as MoEngage supplies them, so store them with the country code — 91XXXXXXXXXX.
• unicode is not detected for you. Add it to the request body when your templates use non-ASCII characters.
• Delivery awaited is not reported. MoEngage sees a message only once it has a final outcome.
• Delivery reports go through the connector, never straight to MoEngage. OneXtel posts each receipt to https://mo.onexaura.com/moengage/sms/dlr, and the connector translates it and forwards it to the MoEngage URL in the callback’s callback header. A callback pointed at the MoEngage URL directly is accepted by MoEngage but never matched to a message.