Standard SMPP 3.4
Transceiver, transmitter and receiver binds, submit_sm, deliver_sm, enquire_link and unbind, with optional TLVs. Works with any SMPP 3.4 client library.
IP-allowlisted binds, throughput set per account, and operator DLR pass-through - on the same routes that power our REST API. One host, three bind modes.
← TCP connected from an allowlisted IP → bind_transceiver system_id = "your_system_id" password = "••••••••" interface_version = 0x34 ← bind_transceiver_resp command_status = 0x00000000 ESME_ROK system_id = "ESMSAFRICA" → submit_sm source_addr = "eSMSCo" destination_addr = "+254712345678" data_coding = 0x00 GSM-7 registered_delivery = 0x01 request DLR short_message = "Your OTP is 482910. Valid 5 min." ← submit_sm_resp command_status = 0x00000000 ESME_ROK message_id = "8A2F91C4" ── 4.2 s later ───────────────────────────── ← deliver_sm DLR from operator SMSC short_message = "id:8A2F91C4 sub:001 dlvrd:001 submit date:2605030812 done date:2605030812 stat:DELIVRD err:000" → deliver_sm_resp command_status = 0x00000000 ESME_ROK → enquire_link keepalive every 30 s ← enquire_link_resp
Point your SMPP client at smpp.esmsafrica.io:2775. Connections are accepted only from the IP addresses on your bind's allowlist.
Send and receive on a single bind. Handles both submit_sm and deliver_sm - the right choice for most integrations.
Submit messages only. Use when you want to isolate outbound sending from inbound DLR reception.
Receive inbound messages and DLRs only. Pair with a TX bind for split-architecture deployments.
Transceiver, transmitter and receiver binds, submit_sm, deliver_sm, enquire_link and unbind, with optional TLVs. Works with any SMPP 3.4 client library.
Port 2775 is closed to the internet. It accepts connections only from the IP addresses on your bind's allowlist. TLS is not offered on the SMPP port; the HTTP API uses HTTPS (TLS 1.2 or 1.3).
Each system_id has its own limit, typically 100 messages per second. Higher limits are available on request, subject to route capacity.
UDH concatenation for multi-part messages. UCS-2 for Unicode (data_coding=8): 70 characters per single SMS, 67 per part. Binary payloads use data_coding=4.
Operator delivery receipts arrive verbatim via deliver_sm. Error codes and timestamps from the carrier SMSC are preserved.
If a destination route degrades, traffic can fail over to a backup route. enquire_link keeps idle binds alive; your client should rebind with back-off if the connection drops.
Every bind lands on our routing infrastructure, passes through licensed carrier routes, and delivers to the handset. No grey routes, no SIM farms.
← DLR returns the same path: operator deliver_sm → eSMS routing layer → your bind → deliver_sm PDU
Any SMPP 3.4 client library works. These snippets use the most popular open-source clients - swap in your credentials.
# pip install smpplib import smpplib.client, smpplib.gsm, smpplib.consts # Connect from an IP on your bind's allowlist client = smpplib.client.Client( 'smpp.esmsafrica.io', 2775, allow_unknown_opt_params=True, timeout=30, ) client.connect() client.bind_transceiver( system_id='YOUR_SYSTEM_ID', password='YOUR_PASSWORD', ) # Register DLR handler (deliver_sm callbacks) def dlr_received(pdu): msg = pdu.short_message if isinstance(msg, bytes): msg = msg.decode('latin-1') print(f"DLR: {msg}") client.set_message_received_handler(dlr_received) # Send a message (GSM-7, with DLR) parts, enc, msg_type = smpplib.gsm.make_parts('Your OTP is 482910') for part in parts: resp = client.send_message( source_addr_ton=smpplib.consts.SMPP_TON_ALNUM, source_addr_npi=smpplib.consts.SMPP_NPI_UNK, source_addr='eSMSCo', dest_addr_ton=smpplib.consts.SMPP_TON_INTL, dest_addr_npi=smpplib.consts.SMPP_NPI_ISDN, destination_addr='+254712345678', data_coding=enc, esm_class=msg_type, short_message=part, registered_delivery=1, ) print(f"Queued: {resp.message_id}") # Block and process inbound PDUs client.listen()
Python and Java bind examples in the SMPP credentials guide →
Bulk SMS, an SMS API and OTP to every African mobile network on direct routes.
Managed phone verification and OTP - generate, send, rate-limit and check codes in two API calls.
Dedicated or shared short codes to send and receive SMS, with signed webhooks and replies from your code.
Transactional and marketing email with a modern API, delivery reports and analytics.
Branded short links, QR codes and click analytics for your campaigns.
AI plus human customer-support chat you can add to any website.
The desktop app that brings Email, SMS and SMPP into one place.
We provision bind credentials and validate the connection on a test SMSC before you go live.