One-time passwords delivered over DLT-registered routes for login, signup, password reset and payment confirmation.

SMS

02Live example

This is what otp sms looks like when it lands on a customer’s phone.

9:41
MSGBRGsms

482913 is your MsgBridge OTP. Valid for 5 minutes. Do not share this code with anyone.

9:41

03The API call

One request. Copy it, drop in your key, and send.

curl https://api.msgbridge.in/v1/sms/send \  -H "Authorization: Bearer $API_KEY" \  -d to="+91XXXXXXXXXX" \  -d template_id="otp_login" \  -d entity_id="$ENTITY_ID"

04When to use it

  • Login and signup verification
  • Password and PIN reset
  • Payment confirmation before a transaction completes
  • Two-factor authentication for account changes

05What's required

  • Registered principal entitySubject to operator DLT approval timelines
  • Approved 6-character headerSubject to operator DLT approval timelines
  • Approved content template with variablesSubject to operator DLT approval timelines
  • TM chain bindingCompleted once entity, header and template are approved

06How to go live

1

Register

Principal entity and sender header submitted to the DLT platform.

2

Approve

Content template drafted and approved, then bound to your entity.

3

Integrate

API access is typically ready within one working day once formalities and testing are complete.

4

Go live

Start sending OTPs with delivery reports over the API.

08FAQ

Delivery over transactional routes is typically fast, though exact timing depends on the recipient's operator and network conditions at the time.

For higher-stakes verification, MsgBridge Verify automatically falls back to WhatsApp and then a voice call until the code lands.

Your business needs a registered entity, header and template. We can complete this for you — see DLT Registration Assistance.

Yes, within DLT's template and variable rules. We help draft the template so it passes approval on the first attempt.

Ready to send with OTP SMS?

Talk to us, or start building against the sandbox today.