SMPP (Short Message Peer-to-Peer) is the binary telecom protocol carriers and aggregators use to exchange SMS at high volume; most application senders use an HTTP API instead.
SMPP is the wholesale protocol of the SMS world, an open industry specification of which version 3.4 is the one most deployments speak. A client, called an ESME in the specification, opens a persistent TCP session to a server and binds as a transmitter, a receiver or a transceiver. It then submits messages as protocol data units (submit_sm), receives delivery receipts and inbound messages over a bind (deliver_sm), and exchanges keep-alives (enquire_link) to hold the session open. It is efficient at thousands of messages per second, and it is what gateways and aggregators use between themselves and towards carriers.
For an application, SMPP is rarely the right interface. It needs a long-lived connection, custom encoding of every field, and a library that handles binds, windows and reconnects. The sender chooses the data coding, splits long texts and builds concatenation headers, and receipts arrive in a text format that varies by provider. An HTTP API with JSON, idempotency keys and webhooks gives the same outcome with far less to maintain, up to volumes that batch endpoints handle comfortably.
A hypothetical comparison: a bind with a window of 10 and a 50 ms round trip tops out near 200 submissions per second, and every extra bind is another connection to monitor. The same team calling an HTTP API can send 1,000 messages in a single batch request.
Common misconceptions: that SMPP delivers better, when delivery depends on the route from the provider to the operator rather than on the protocol between you and the provider; that it is faster, when either protocol adds milliseconds and the time spent in operator networks is longer; and that it is safer for retries. SMPP has no idempotency: if a submission times out, you cannot tell whether it was accepted.
At SMSMeteor: SMPP is not offered to accounts. The public interface is a REST API that accepts 50 requests per second per key, and a batch of up to 1,000 messages counts as one request. The guide SMPP vs HTTP API explains when a bind is actually justified.
