Service messages triggered by a customer action — order updates, payment confirmations, appointment reminders and account alerts.
SMS
02Live example
This is what transactional sms looks like when it lands on a customer’s phone.
Your payment of Rs.2,499 for order #4821 was received. Thank you for shopping with us.
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="payment_confirmed" \ -d entity_id="$ENTITY_ID" \ -d content.amount="2499"04When to use it
- Order confirmations and shipping updates
- Payment and refund confirmations
- Appointment and booking reminders
- Account alerts such as low balance or expiry notices
05What's required
- Registered principal entitySubject to operator DLT approval timelines
- Approved header and content templateSubject to operator DLT approval timelines
- TM chain bindingCompleted once entity, header and template are approved
06How to go live
Register
Entity, header and template submitted for DLT approval.
Approve
Template approved and bound to your entity via TM chain.
Integrate
Connect the send API with your order, payment or booking system.
Go live
Real-time delivery reports are retrievable over the API from day one.
07Related channels
08FAQ
Transactional messages are triggered by a customer's own action and can be sent any time. Promotional messages are marketing sends restricted to specific hours and require DND scrubbing.
Yes. Operator-end delivery reports are available over the API as soon as a message is delivered or fails.
Each approved template declares its variable positions up front — for example the amount or order number — which you then fill in per request.
Yes, including Hindi and other regional scripts. Unicode messages count as more segments than plain-English text, which affects the price per send.
Ready to send with Transactional SMS?
Talk to us, or start building against the sandbox today.