Quick Answer
SMS API integration means connecting your app, website or CRM to an SMS gateway so it can send messages programmatically. With SMSGatewayHub you integrate a single REST API over HTTP/HTTPS (or SMPP for high volume) to send transactional, OTP and promotional SMS, plus WhatsApp, voice, RCS and email. Authenticate with an API key, pass a DLT-registered header and template, and read delivery reports back - with ready code for PHP, Python, Node.js and C#, on Pay As You Go billing.
What you can integrate through one SMS API
A single account and API key covers every channel and operation - call only what you need.
| What you integrate | Method / endpoint | Typical use | Category |
|---|
| Send transactional SMS | HTTP GET/POST - SendSMS | OTP, alerts, confirmations | Transactional -T |
| Send OTP SMS | HTTP - OTP route | Login and payment verification | Transactional -T |
| Send promotional SMS | HTTP - SendSMS (promo route) | Offers and campaigns, with consent | Promotional -P |
| Bulk / personalised SMS | HTTP POST JSON - GroupSms | Different text per number | -T / -S / -P |
| Delivery reports (DLR) | HTTP - GetDelivery | Confirm handset delivery | Reporting |
| Balance check | HTTP - GetBalance | Monitor Pay As You Go balance | Account |
| High-volume binds | SMPP v3.4 | Millions of messages, low latency | All |
| WhatsApp / Voice / RCS / Email | HTTP APIs | Multi-channel from one account | Varies |
Full request parameters, responses and error codes are in the developer API docs and SMS API error codes.
Every API you can integrate with SMSGatewayHub
OTP SMS API
High-priority OTP route with optional WhatsApp fallback. OTP SMS.
WhatsApp API
Send template and session messages on the official WhatsApp Business API. WhatsApp.
Voice & IVR API
Trigger voice OTP and outbound calls programmatically. Voice SMS.
RCS API
Branded RCS with cards and buttons, SMS fallback. RCS messaging.
Email API & SMTP
Transactional and marketing email over API or SMTP relay. Bulk email.
Two-way / DLR
Receive replies and delivery reports back into your app. Two-way messaging.
Quickstart: send your first SMS
cURLcurl -G "https://www.smsgatewayhub.com/api/mt/SendSMS" \
--data-urlencode "APIKey=YOUR_API_KEY" \
--data-urlencode "senderid=YOURID" \
--data-urlencode "channel=2" \
--data-urlencode "DCS=0" \
--data-urlencode "flashsms=0" \
--data-urlencode "number=91XXXXXXXXXX" \
--data-urlencode "text=Your OTP is 4821. Do not share it." \
--data-urlencode "route=1" \
--data-urlencode "EntityId=YOUR_DLT_ENTITY_ID" \
--data-urlencode "dlttemplateid=YOUR_DLT_TEMPLATE_ID"
# Response: {"ErrorCode":"000","ErrorMessage":"Success","JobId":"20047", ...}
What to get right before you integrate
DLT registration
Register your entity, header and templates on DLT first. DLT registration.
Typed template variables
Use {#numeric#}, {#alphanumeric#}, {#url#} and {#cbn#} exactly as approved. Sample templates.
Header-based auth
Send the API key from your server, never from browser or app code, and whitelist your server IP.
Whitelisted links & numbers
URLs, APKs and callback numbers in the text must be whitelisted on DLT or the message is rejected.
Why SMSGatewayHub
Why developers integrate SMSGatewayHub
One integration, every channel, DLT-ready.
Ready code
Copy-paste samples in cURL, PHP, Python, Node.js and C# in the developer docs.
HTTP and SMPP
Start on REST, move heavy traffic to SMPP without changing providers.
Pay only for delivered
Delivery-report-based billing - failed messages are not charged.
DLT-compliant by design
Typed variables, header suffixes and whitelisting built into the flow.
Scales with you
From a few OTPs to millions of messages on the same account.
Developer support
Integration help 24/7 and a full error-code reference.
| Question to ask any SMS API provider | SMSGatewayHub |
|---|
| Do you offer both HTTP and SMPP? | Yes - REST API and SMPP v3.4 binds. |
| Is there code for my language? | cURL, PHP, Python, Node.js and C# samples. |
| Do you return delivery reports? | Yes - DLR API and optional webhooks. |
| Can OTP fall back to WhatsApp? | Yes - OTP SMS with WhatsApp fallback. |
| Is billing pay-per-delivered? | Yes - Pay As You Go on delivered messages. |
See the full reference in the developer API docs.
Integrate in four steps
Create an account & API key
Sign up and copy your API key from API Settings.
Register DLT header & template
Map your sender ID and templates - see DLT registration and sample templates.
Call the API from your server
Use the SendSMS endpoint with your key, header, EntityId and dlttemplateid.
Read delivery reports
Poll the DLR API or receive webhooks, and handle error codes in your code.
HTTP API vs SMPP: which to integrate
For most apps, websites and CRMs the HTTP/HTTPS REST API is the fastest way to integrate - a single authenticated request sends a message, and a second call returns its delivery report. It suits OTPs, alerts and campaigns up to high daily volumes.
If you push very large volumes or need the lowest latency and a persistent connection, integrate over SMPP v3.4 instead. The same account, headers and DLT templates apply, so you can start on HTTP and add an SMPP bind later. Compare both on the developer API docs and SMPP connectivity pages.
Frequently Asked Questions
What is SMS API integration?
SMS API integration is connecting your application, website or CRM to an SMS gateway so it can send and track messages automatically through code. With SMSGatewayHub you authenticate with an API key and call a REST endpoint over HTTP/HTTPS, or bind over SMPP, to send SMS, OTP and more.
How do I integrate an SMS API in India?
Create an SMSGatewayHub account, register your sender ID and templates on DLT, copy your API key, then call the SendSMS endpoint from your server with the header, EntityId and dlttemplateid. Ready code for cURL, PHP, Python, Node.js and C# is in the developer API docs.
Does SMSGatewayHub offer both HTTP and SMPP APIs?
Yes. You can integrate over the HTTP/HTTPS REST API for most use cases, and over SMPP v3.4 for high-volume, low-latency sending. The same account, headers and DLT templates work for both.
Which programming languages are supported for SMS API integration?
The SMSGatewayHub developer docs provide copy-paste examples in cURL, PHP, Python, Node.js and C#. Because it is a standard REST API, any language that can make an HTTPS request can integrate it.
Do I need DLT registration to integrate the SMS API?
Yes. Commercial SMS in India must use a DLT-registered header and template. Register your entity, header and templates first, then pass the EntityId and dlttemplateid in each API call. See the DLT registration guide.
How do I get delivery reports through the API?
After sending, call the DLR (GetDelivery) API with the JobId returned by the send response, or receive delivery webhooks. The report shows the operator delivery status for each message.
Can I integrate OTP SMS with a WhatsApp fallback?
Yes. SMSGatewayHub offers an OTP route with optional WhatsApp fallback, so if an OTP SMS is not delivered the code can also be sent on WhatsApp. Both are integrated from the same account.
How is the SMS API billed?
On Pay As You Go - you are billed for delivered messages only, and failed or undelivered messages are not charged. Check your balance any time with the GetBalance API.
Start integrating in minutes
Create your account, grab an API key and send your first SMS today.