SMPP: definition and how it works
Published and updated
SMPP (Short Message Peer-to-Peer) is the binary, persistent-connection protocol that message centres, aggregators and high-volume senders use to exchange SMS with mobile networks.
How it works
Behind every HTTP SMS API there is usually SMPP. The protocol was defined by the SMS Forum in the late 1990s and connects external short message entities, such as an aggregator's platform or a large enterprise sender, to a message centre inside a carrier, or to an SMS gateway or hub in between. The reference site for the protocol lists version 3.4 from 1999 as the widely deployed one and version 5 from 2003 as the final release; the forum that maintained it has since disbanded.
SMPP is not HTTP. A client opens a long-lived TCP session, binds as a transmitter, receiver or transceiver, and then exchanges binary protocol data units: submit a message, get a message identifier back, receive delivery receipts and inbound messages on the same session. Throughput is measured in messages per second per bind, and windowing lets many submits be in flight at once. That is what makes it the wholesale protocol: it is efficient at volumes where HTTP request overhead would matter.
The cost is complexity. Encoding, concatenation and character sets are the sender's problem in SMPP, and every carrier interprets parts of the specification a little differently. Aggregators exist largely to absorb that complexity and to expose a simple HTTP API in front of it.
Developers should reach for SMPP only when they operate messaging infrastructure. For an application that sends notifications, an HTTP API over an existing gateway is the whole job.
- smpp.org describes the Short Message Peer-to-Peer Protocol as connecting External Short Message Entities, Routing Entities and Message Centres, and lists specifications v3.3 (1997), v3.4 (1999) and v5 (2003), the final version. smpp.org, checked on September 5, 2026
How this applies with textbee
textbee does not speak SMPP and does not need to. The phone hands each message to its SIM the way any handset does, and your code talks to textbee over HTTPS. The carrier connection is the SIM.
Related terms
- SMS gateway: An SMS gateway is the piece of software or hardware that takes a message from an application and hands it to a mobile network so it arrives as a text on a phone.
- SMS API: An SMS API is a programmatic interface, almost always HTTP, that lets software send text messages, read the ones that arrive, and check what happened to each one.
- SMS throughput: SMS throughput is the number of messages a sender can push into the network per unit of time, and it is set by the sender type: a handset, a long code, a short code or an SMPP bind each have their own ceiling.
- Delivery receipt: A delivery receipt is the network's report that an SMS reached the recipient's handset, or failed to, surfaced by a gateway as a status on the message.
Sources
- SMPP, smpp.org, checked on September 5, 2026