SMPP provider and gateway for high-volume A2P SMS
Connect your SMS platform, core system or SMPP client to BroadNet's A2P network over SMPP 3.4 with TLS. Binds are provisioned for your account, with sender IDs, delivery receipts and the same routes as our REST API.
# SMPP 3.4 transceiver bind (illustrative)
bind_type = bind_transceiver
host = issued with your account
port = TLS port issued with your account
tls = required
system_id = YOUR_SYSTEM_ID
password = YOUR_PASSWORD
interface_version = 0x34
registered_delivery = 1
source_ton_npi = 5/0 # alphanumeric sender ID
dest_ton_npi = 1/1 # international format
data_coding = 0 (GSM-7) | 8 (UCS-2, Arabic)Illustrative SMPP 3.4 bind settings. Host, port, credentials and limits are issued per account.
Short answer
Updated
OmniChannels.ai is the messaging platform of BroadNet, an SMPP provider with direct connections to more than 1,000 operators and aggregators. You get SMPP 3.4 binds over TLS, provisioned per account with your own system_id, agreed throughput and delivery receipts via deliver_sm. GSM-7, Unicode and Arabic are supported, and resellers can have dedicated binds.
What your SMPP account includes
SMPP 3.4 over TLS
Binds use SMPP v3.4 over an encrypted TLS connection. We also ask for the public IP addresses you will connect from when we provision the account.
Binds provisioned per account
You receive your own system_id, password, host and TLS port, the number of concurrent binds and the throughput agreed for your traffic.
Direct operator connectivity
Traffic runs on BroadNet's network of direct connections to more than 1,000 operators and aggregators, the same routes the REST API uses.
Delivery receipts on the session
Set registered_delivery and receive receipts as deliver_sm with standard states such as DELIVRD, UNDELIV, EXPIRED and REJECTD.
GSM-7, Unicode and Arabic
Send GSM-7 with data_coding 0 or UCS-2 with data_coding 8 for Arabic and other scripts, with concatenation for long messages.
Sender IDs registered for you
We register alphanumeric sender IDs in markets that require it, such as the UAE and Saudi Arabia, with the registration fee passed through at cost.
Dedicated binds for resellers
Resellers and wholesale partners can have dedicated binds, sub-accounts with their own credit and rate cards, and a white-label console.
REST alongside SMPP
Use SMPP for high-volume SMS and the REST API for HLR lookup, WhatsApp, RCS and the other channels, on the same account.
SMPP or REST API: which connection fits your traffic
You can use both on one account. Most aggregators and resellers run SMPP for SMS and REST for everything else.
| Item | Details |
|---|---|
| Channels | SMPP carries SMS only. The REST API covers SMS, WhatsApp, RCS, Messenger, Instagram, Telegram, email and push. |
| Connection | SMPP keeps one long-lived TLS session (a bind) open. REST sends one HTTPS request per call. |
| Throughput | SMPP is built for sustained high volume with many messages in flight; your per-bind limits are agreed for your account. REST suits most application traffic. |
| Delivery receipts | SMPP returns deliver_sm on the same session. REST posts statuses to your webhook in one normalised format. |
| Effort | SMPP needs an SMPP client library and connection management. REST works with any HTTP library or the TypeScript SDK. |
| Best for | SMPP: aggregators, resellers and enterprises that already run SMPP clients. REST: applications, OTP and multichannel use cases. |
How to get an SMPP account
SMPP access is set up by our team rather than self-served, so the bind matches your countries, sender IDs and volumes.
- 1
Tell us your traffic
Destination countries, message types, sender IDs, expected daily volume and peak throughput.
- 2
Share connection details
The public IP addresses you will connect from and the SMPP client you use.
- 3
Receive your bind
We issue host, TLS port, system_id and password, the number of binds and your agreed throughput.
- 4
Test to your own numbers
Bind as a transceiver, send to your verified test numbers and check the deliver_sm receipts.
- 5
Go live
Production routes are switched on once sender IDs and compliance checks are complete for each country.
When SMPP is the right connection
A good fit when
- You run your own SMS platform, SMSC or CPaaS and need a carrier-grade upstream.
- You send sustained high volumes of OTPs, alerts or campaigns and already operate an SMPP client.
- You are a reseller or aggregator who needs dedicated binds, sub-accounts and wholesale rates.
- You need Arabic and Unicode SMS to GCC and MENA operators with registered sender IDs.
Good to know before you start
- SMPP carries SMS only; WhatsApp, RCS and the other channels use the REST API.
- Accounts are provisioned by our team after review. There is no instant self-serve SMPP signup.
- Throughput is agreed per account. Keep a window of unacknowledged PDUs rather than waiting for each response, or throughput drops.
- Sender ID, content and sending-hour rules still apply per country, and unregistered sender IDs may be rejected.
SMPP account questions
What is an SMPP provider?
An SMPP provider gives you a direct protocol connection, called a bind, to its SMS network using Short Message Peer-to-Peer. Your system keeps a session open, submits messages with submit_sm and receives delivery receipts on the same connection. It suits platforms and enterprises sending SMS at high volume.
How do I get an SMPP account?
Request access with your destination countries, sender IDs, expected volumes and the public IP addresses you will connect from. Our team reviews the traffic, then issues your host, TLS port, system_id, password and agreed throughput. Testing goes to your own verified numbers before production.
Which SMPP version and security do you support?
We accept SMPP v3.4 binds over TLS. Use transceiver binds to submit messages and receive receipts on one session, or separate transmitter and receiver binds if your client requires them.
Can I send Arabic SMS over SMPP?
Yes. Set data_coding to 8 to send UCS-2, which covers Arabic, emoji and other scripts. A single Unicode message holds 70 characters, or 67 per part when concatenated. Long messages can be segmented with a User Data Header or sent in the message_payload TLV where enabled on your bind.
What throughput will my SMPP bind support?
Throughput is agreed for your account and confirmed with your credentials. To reach it, keep several submit_sm PDUs in flight instead of waiting for each response, and open additional binds up to the number agreed with you.
Can I resell SMS through an SMPP connection?
Yes. Resellers and wholesale partners can have dedicated binds, plus a white-label console, sub-accounts with their own credit and rate cards, and a reseller API. See the reseller and wholesale programmes for the commercial model.
How is SMPP SMS priced?
SMPP uses the same per-message rates as the REST API, set by destination country and operator. BroadNet's indicative list rates are on the SMS pricing pages; there is no setup fee and no monthly minimum, and your quote confirms the final rates.
Guides on this topic
- IntegrationSMS API vs SMPP: Which Connection Should You Use?12 min read
- SMS & OTPWhat Is A2P SMS? How Business Messages Reach the Handset8 min read
- MarketingSent vs Delivered vs Read vs Failed: Message Status Explained8 min read
Explore more of the platform
Request an SMPP account
Tell us your countries, sender IDs, volumes and connecting IP addresses. Our team will scope your bind and send test credentials for your own numbers.
Share your stack and what you want to connect. A solutions engineer will follow up.