Step 1 of 4Pick the link domain you'll whitelist

Strait links in Indian SMS (TRAI DLT whitelisting)

After this guide, your DLT content templates carry your Strait link, operators let the messages through, and each tap shows up in Analytics under your SMS campaign.

On this page 6
  1. 1. Pick the link domain you'll whitelist
  2. 2. Whitelist the domain on your DLT portal
  3. 3. Put the link in a content template
  4. 4. Send one test SMS and tap it
  5. Common errors
  6. Next steps
Time
About 20 minutes, plus your operator's approval of the whitelist entry and the template
You need
A business registered as a sender on an Indian operator's DLT portal (or an SMS provider that manages DLT for you), an approved header, and a Strait secret key in your server's environment as SECRET_KEY
Works on
Any SMS provider in India. The links work for Android and iPhone users.

Every commercial SMS in India passes through the operators' DLT (Distributed Ledger Technology) system under TRAI's Telecom Commercial Communications Customer Preference Regulations, 2018. Since 1 October 2024, operators must not let through any message whose URL the sender hasn't whitelisted (TRAI direction of 30 August 2024; PIB, 26 September 2024). Senders who haven't whitelisted their links "will not be able to transmit any messages containing URL/APK/OTT links".

For a link with a changing part, TRAI's rule is that "the fixed part of URL is whitelisted" (its direction of 12 May 2023, quoted in the direction of 20 August 2024). A Strait link fits this: the fixed part is your workspace's own domain, and the slug is the part that changes.

Use your workspace's own domain, https://hilltop.strait.link/. You'll find it in Dashboard → Setup → Your keys, and the API returns it in every link's shortUrl. On Starter and up you can use a custom domain you own, like links.yourcompany.in, instead. Each domain is a separate whitelist entry, so send all your SMS links on one of them. If you switch domains later, whitelist the new one and update your templates before you send from it.

Don't put these in SMS:

  • The bare strait.link/<slug> address. Every Strait workspace shares it (Link domains), so it isn't yours to whitelist.
  • A public shortener such as bit.ly, or a link wrapped by another tracker. Thousands of senders post links on those domains. Since the 2025 amendment, a sender also gives an undertaking "that the whitelisted URLs/ APKs/ OTT links are not malicious" (TCCCPR Second Amendment Regulations, 2025). You can promise that for your own domain. You can't promise it for a domain anyone can post links on.

You should see: one domain written down, such as https://hilltop.strait.link/.

2. Whitelist the domain on your DLT portal

Sign in to the DLT portal of the operator where your business is registered as a sender, or ask your SMS provider if they handle DLT for you. Open the URL whitelisting section (portals call it "URL", "CTA" or "whitelisted content") and add the fixed part, https://hilltop.strait.link/, exactly as it will appear in your messages.

TRAI's 30 August 2024 direction describes operators exchanging whitelisted entries between themselves. In most cases you add the entry once, where you're registered.

You should see: the entry listed as approved or active on the portal. How long that takes depends on the operator.

The URL has to sit inside a registered content template. Write the fixed part as plain text and make the slug the template's variable (on most portals {#var#}):

Content template (service)
Hi {#var#}, your Diwali offer is live. Open it in the app: https://hilltop.strait.link/{#var#} - Hilltop Shoes

Pick the category that matches what the message says. TRAI tells operators to blacklist a template registered in the wrong category, and one template can be linked to only one header (20 August 2024 direction, paragraph 10). Since the 2025 amendment, the header that people see ends in -P, -S, -T or -G for promotional, service, transactional and government messages.

Then make the link, with an SMS tag on the destination so Analytics can tell the channel apart:

Terminal
curl https://strait.link/v1/links \
  -H "Authorization: Bearer $SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "diwali-sms",
    "longUrl": "https://shop.example.com/sale/diwali?utm_source=sms&utm_medium=sms&utm_campaign=diwali-2026"
  }'

Keep slugs short. A message over 160 characters goes out as two or more parts.

You should see: the template approved on the portal, and "shortUrl": "https://hilltop.strait.link/diwali-sms" from the API.

4. Send one test SMS and tap it

Send the template through your SMS provider to your own phone, with diwali-sms as the link variable. Tap it on an Android phone and on an iPhone, then read the taps per channel:

Terminal
curl "https://strait.link/v1/analytics?link=diwali-sms&group=channel" \
  -H "Authorization: Bearer $SECRET_KEY"

You should see: the SMS arrives from your header with its category suffix, the link opens your app (or the store when the app isn't installed), and the response has a row with "key": "sms".

Common errors

  • The SMS never arrives and your provider reports it as rejected or failed at scrubbing. The URL in the message doesn't match a whitelisted entry: usually a different domain (strait.link instead of hilltop.strait.link, an old custom domain) or a spelling that differs from the entry. Whitelist the exact fixed part and send again. Each provider uses its own error codes. A blocked message never reaches Strait, so it shows no tap.
  • The portal rejects the template. The URL in it isn't whitelisted yet, the category doesn't match the text, or the template is already linked to another header.
  • Taps show up as direct, not sms. The destination has no utm_source. Add it with PATCH /v1/links/{slug}; the link in your template stays the same.

Next steps