API Reseller
SMS API
Transactional SMS delivery with the DLT registration that Indian regulation requires, including template and header management, plus delivery receipts per message.
What you get
- DLT-registered template and header management
- Per-message delivery receipts
- Unicode and regional language support
- Scheduled and bulk sending
- Delivery reporting by template and by day
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Templates
- DLT-registered template ID required per message. Unregistered sends are refused.
- Delivery
- Asynchronous. The submission response is acceptance, not delivery.
- Webhook
- Per-message delivery receipts, signed as above.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About sms api
Why was my message refused before it was sent?
Almost always an unregistered DLT template. Indian regulation requires the template to be registered against the sender before it can be delivered, so an unregistered send is refused at submission rather than accepted and silently dropped.
Does a successful submission mean the message arrived?
No. Submission is acceptance; delivery is reported separately by webhook. Treating the submission response as delivery is the most common integration error, and it hides every genuine delivery failure.