Configure CleverTap
Introduction
Unique Digital Outreach Pvt Ltd SMS can be integrated into CleverTap in about ten minutes, using CleverTap's own Other (Generic) provider option.
Once saved, every CleverTap campaign and journey that sends SMS routes through UDO automatically. Your segments, journeys and reporting stay exactly where they are — only the delivery layer changes.
Prerequisites
- A Unique Digital Outreach Pvt Ltd SMS account with credits in your account balance.
- Your API key, from the UDO dashboard.
- A CleverTap account with permission to edit engagement channels.
- Completed DLT registration for your sender header and templates. Our team handles this if it is not already done.
A correctly configured integration still fails on an empty account. If the test SMS in step 4 does not arrive, check credits before re-checking the configuration.
Configure Unique Digital Outreach Pvt Ltd as an SMS Provider
Four steps, each shown against the screen you will be looking at.
Open the SMS integration screen
In the CleverTap dashboard go to Settings → Channels → SMS, then Add SMS provider. Open the Provider dropdown and choose Other (Generic) — the last option, below Nexmo, Twilio, Exotel, Netcore and MSG91.
Set the protocol, endpoint and headers
Set Request Type to POST and enter the UDO SMS HTTP API endpoint. Then open the Headers tab and add two key/value pairs.
- Request type
POST- Endpoint
sms— appended to your UDO API base URL- Header
apikey: your UDO API key- Header
Content-Type:application/json
Map the request parameters
On the Parameters tab, select JSON and enter the body UDO expects. CleverTap substitutes its own values into these keys when a campaign fires, so map each one to the matching CleverTap field rather than hard-coding it.
The route and templateId values have to correspond to what is registered on the DLT portal. A mismatch here is the single most common cause of messages that report success and never arrive.
Send a test, then save
Use Send test SMS, enter a real number you are holding, and send. Once it arrives, click Save. CleverTap is now sending through UDO.
Not a test entry in your database. That one message confirms three things at once — the endpoint accepts the request, your API key authenticates, and your DLT header is approved. Only a delivered message proves all three.
Troubleshooting
| Symptom | Most likely cause |
|---|---|
| Test message never arrives | Empty account balance. Check credits before re-checking configuration. |
| Authentication rejected | API key copied with trailing whitespace, or placed in the wrong header field. |
| Request accepted, SMS not delivered | DLT template or route mismatch. Re-check the values from step 3. |
| 404 or endpoint not found | Endpoint entered as sms without the API base URL in front of it. |
| Works in test, fails in campaigns | Parameter keys mapped to literals rather than CleverTap fields. |
Still stuck? Contact the team with the exact error CleverTap returns and we will check it against our logs.
