SMS Gateway API for OTPs, Alerts & Campaigns

It's a service that lets your website, app or software send SMS automatically through an HTTPS request. You send the phone number, your DLT template ID and variable values; the gateway delivers the SMS through telecom operators and reports back whether it was delivered.

Rates start at ₹0.18 per SMS for up to 10,000 credits, ₹0.14 per SMS for up to 5 lakh credits, and ₹0.09 per SMS at enterprise volume, plus 18% GST. There's no setup fee or monthly rental. Each 160-character part (70 for Unicode) uses one credit.

Yes. TRAI requires every business sending commercial SMS to register its entity, sender IDs (headers) and message templates on an operator's DLT platform. Messages that don't match a registered header and template are blocked. We help you register, at no extra charge from us.

Entity registration is usually approved in 1 to 3 working days, and headers and templates in a few hours to 2 days, depending on the operator portal and how well the templates are written. We help you avoid common rejections.

Transactional SMS (-T) are OTPs and alerts tied to a transaction the customer just made. Service SMS (-S) are updates to existing customers, such as order or booking messages. Both are delivered to DND numbers at any time. Promotional SMS (-P) are offers and marketing, sent only to non-DND or consenting numbers during daytime hours.

Yes. OTPs and other transactional and service messages registered in the right category reach DND numbers, 24×7. Promotional messages do not, unless the person has given consent.

It's the name shown as the sender, such as IBACTD. In the inbox it appears with an operator prefix and a category suffix, for example JM-IBACTD-T. Transactional and service headers are 6 letters, usually based on your brand name.

Under TRAI's November 2025 direction, templates must use typed variables such as {#numeric#}, {#alphanumeric#}, {#url#}, {#urlott#}, {#cbn#} and {#email#} instead of a generic {#var#}. After the transition, messages whose values don't match the tag type are rejected. We help convert your existing templates.

Yes, but every link must be whitelisted on DLT and use your own domain. Public URL shorteners are blocked. The same applies to app download links and call-back numbers.

One standard SMS holds 160 characters. Longer messages are split into parts of 153 characters each and joined on the phone. Messages in Hindi or other scripts, or with emojis, use Unicode: 70 characters in one SMS, or 67 per part. Each part is charged as one credit.

Yes. The API supports Unicode, so you can send in Hindi, Tamil, Telugu, Bengali, Kannada, Marathi and other languages. Register the template in the same language on DLT.

Each SMS gets a message ID. When the operator confirms delivery or failure, we post the status to your callback URL (webhook) and show it in the dashboard, with the operator's error code for failed messages.

Yes. SMPP is available on the Enterprise plan for high-volume senders and platforms that already use SMPP clients. REST and HTTP APIs are available on all plans.

Yes. You get sandbox access to test your integration before going live. Live sending starts after your DLT entity, header and templates are approved.

Most OTPs on the transactional route are delivered within a few seconds. Delivery time depends on the operator, the recipient's network and whether the phone is switched on and in coverage.

Yes. Any system that can make an HTTPS request can use the API, and we help connect common platforms such as WordPress and WooCommerce, Shopify, Zoho and custom CRMs for OTP login, order alerts and reminders.

Credit validity depends on your plan and is confirmed on your account. Ask us if you need long validity for low monthly volumes.

Yes, 18% GST is charged on SMS credits, and you get a GST invoice that registered businesses can use to claim input tax credit. DLT portal fees, if any, are charged by the operator.