What is an SMS gateway? How it works, types and how to choose one

What is an SMS gateway?

An SMS gateway is a service that connects software to the mobile networks so that text messages can be sent and received automatically. Your application passes it a message and a phone number. The gateway validates the request, picks a route to the destination operator, hands the message over and reports back whether it was delivered.

The term covers a lot of ground. A cloud platform that sends a million one-time passwords an hour is an SMS gateway. So is the small box on an office shelf with a SIM card in it. They share the job but little else, and the difference between them is what most of this guide is about. If you only need the short version: for anything customer facing, use a cloud gateway reached through an HTTP API, on direct operator routes, with delivery receipts.

SMS itself is old, and still dependable. It needs no app and no data connection, and it reaches nearly every phone in use. That is why banks, logistics firms and e-commerce stores still rely on it for one-time passwords, transactional alerts and reminders. The SMS standard dates from the early 1990s, and the gateway is the modern layer that lets software use it.

How an SMS gateway works, step by step

Behind a single API call, five things happen in a few hundred milliseconds.

1. Your application sends a request. It calls the gateway's HTTP API or an SMPP connection with a destination number, the message text and a sender ID.
2. The gateway checks it. It validates the number format, checks your account balance and permissions, and tests the content against any registered templates or blocked terms.
3. It works out the segments. Long text is split into parts. A plain-text message fits 160 characters; one emoji or a Hindi character switches the encoding and cuts the limit to 70. Our guide to SMS segments, encoding and cost explains the arithmetic.
4. It routes the message. Based on destination, price, quality and current operator health, the gateway chooses a route and passes the message to the operator's short message service centre (SMSC).
5. The receipt returns. The operator reports a status such as delivered, failed or rejected. The gateway turns that into a delivery receipt and posts it to your webhook.

The last step is the one teams neglect. Without receipts you only know that the gateway accepted a request, not that a person received a text. Our reference for webhooks and the help article on delivery receipts and signatures show how to store and verify them.

The main types of SMS gateway

Gateways differ mostly in how you connect to them and how far the message travels on the provider's own infrastructure. Here are the four you are likely to meet.

1. HTTP or REST API gateways

You send a web request with your key and the message details, and receive JSON in reply. This is the right choice for almost every website, mobile backend and SaaS product. It is easy to test with a single command, works behind any firewall and needs no special libraries.

2. SMPP gateways

SMPP (Short Message Peer-to-Peer) is a protocol that holds a connection open and streams messages over it. It is how operators and aggregators talk to each other. You bind as a transmitter, receiver or transceiver and send at a set throughput. It suits very high volume or software that already speaks SMPP; see our SMPP documentation.

3. Email-to-SMS gateways

You email a specially formatted address and it becomes a text. It is a quick fix for legacy tools that can send mail but nothing else. Delivery tracking is thin and sender control is limited, so use it as a stopgap.

4. GSM modem or SIM-based gateways

A device that holds one or more SIM cards and sends messages as if from a phone. It is cheap to start and painful to scale: throughput is a few messages a minute, SIMs get blocked for commercial traffic and you get no real delivery data. Operators in many countries treat this as grey traffic. We do not recommend it for customer messages.

A and P: why application-to-person traffic is treated differently

Messages between two people are person-to-person (P2P). Messages sent by software to people are application-to-person (A2P) traffic. Operators charge for A2P, monitor it and, in many countries, regulate it. India's DLT framework, the US 10DLC rules and the UAE's sender registration are all A2P controls. A gateway that hides this from you is not helping; one that handles it for you is.

Sending your first message through an API

This is what a typical call looks like on our platform. The structure is similar for most gateways: an authenticated POST with a channel, a destination in international (E.164) format, a sender and either text or a registered template.

curl -X POST https://api.telnxo.com/v1/messages \
  -H "Authorization: Bearer $TELNXO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "sms",
    "to": "+919812345670",
    "sender": "TELNXO",
    "template": "otp",
    "variables": { "code": "482913" }
  }'

The response contains a message ID. Keep it: it is the key you will use to match the delivery receipt, answer support tickets and reconcile billing. The full field list is in the API reference, and you can check how many segments a message will use with the free SMS segment calculator.

The figures above are standard limits for the SMS format. Delivery time depends on the operator and the destination, which is why monitoring it matters.

What to check before choosing an SMS gateway

Price is the first thing people compare and the least useful. These are the questions that separate a dependable gateway from a problem you will meet in month three.

• Route quality. Does the provider connect directly to operators, or resell through several layers? Each layer adds delay and a point of failure.
• Delivery reporting. You want per-message status, error codes with real meaning and an export. Our list of error codes shows the level of detail to expect.
• Compliance support. Can the provider help with sender ID and template registration in the countries you send to? In India that means DLT; see our DLT registration checklist.
• Failover. What happens when an operator link degrades? A good gateway shifts traffic automatically and tells you.
• Security. Scoped API keys, signed webhooks and IP allow-listing should be standard, not extras.
• Limits. Know the per-second throughput and any daily caps. They are documented in our rate limits page.
• Fallback channels. If you also use WhatsApp or RCS, being able to fall back to SMS from one API saves a second integration.

A gateway that reports honestly on failures is worth more than one that promises every message arrives.

How much does an SMS gateway cost?

You pay per segment sent, and the rate depends on the destination. Domestic rates in large markets are a fraction of a rupee or cent; rates to some countries are many times higher. Three details change the total more than the headline number.

Our cost calculator lets you model monthly spend by country and volume, and the pricing page lists current rates.

Common problems and how to avoid them

Messages accepted but never delivered

The API call succeeded, so the gateway took the message. The failure happened later. Look at the receipt: a rejected status with a template or sender error points to registration; an undelivered status on a valid number points to the handset or operator. Our guide to why messages fail or arrive late walks through the causes in order.

Messages that cost more than expected

Almost always an encoding problem. One curly quote pasted from a document turns a 160-character message into a 70-character one. Run drafts through the Unicode checker before they go to a template.

OTP that arrives after the code expires

Verification traffic needs a fast route and a short retry rule. If you send one-time passwords, read our OTP best practices and consider a dedicated OTP product that handles expiry and fallback for you.

Wrong or missing sender ID

Some countries replace unregistered alphanumeric senders with a random number or block them. Use our sender ID checker for the rules by country, and confirm each one with the provider before launch.

Where SMS gateways are heading

SMS is not going away, but it is no longer alone. RCS adds branded, interactive messages on supported Android phones, and WhatsApp reaches people who prefer chat apps. Many businesses now send over several channels and fall back to SMS when the first one cannot deliver. If you are planning that, read our comparison of RCS and SMS and the overview of the WhatsApp Business API.

If you are moving from another provider, the migration guides for Twilio, MSG91 and Kaleyra list what maps across and what to test first.