SMPP Connectivity
Connect your platform directly to our SMS infrastructure over SMPP 3.4 for high-throughput, low-latency messaging with persistent binds and carrier-grade reliability.
What you get with SMPP Connectivity
Use cases
What businesses send with SMPP Connectivity
SMS aggregators
Route traffic from your own customers through a single persistent SMPP bind with predictable throughput.
High-volume OTP
Sustain low-latency delivery for authentication traffic where every second counts.
Platform integrations
Wire your existing messaging stack straight into our infrastructure without rewriting to HTTP.
Bulk campaign engines
Push large campaigns at sustained rates over a connection built for continuous sending.
Two-way messaging
Receive inbound messages (MO) and delivery receipts on the same session in real time.
Failover routing
Run SMPP alongside our REST and XML APIs as a resilient, independent delivery path.
Frequently asked questions
Which SMPP version do you support?
We support SMPP 3.4 with transmitter, receiver, and transceiver bind modes.
How do I get SMPP credentials?
Contact our team to provision an SMPP account. We provide the host, port, system ID, and password, and whitelist your source IP for a secure bind.
How many binds can I open?
You can open multiple concurrent binds per account. Window size, throughput, and bind limits are set to match your plan and expected volume.
Do you send delivery receipts over SMPP?
Yes. Delivery receipts (DLRs) are returned on your receiver or transceiver session so you can track final message status in real time.
Do you support Unicode and long messages?
Yes. We support GSM 7-bit and Unicode (UCS-2), with automatic segmentation and concatenation of long messages.
Can I use SMPP and the HTTP API together?
Yes. SMPP and our REST (JSON) and XML APIs share the same account and reporting, so you can combine them or use SMPP as a failover path.
Ready to send with SMPP Connectivity?
Create your account, top up a bundle, and start sending in minutes.