SMPP for Sierra Leone
Already run an SMS platform? Bind it straight to Apphive over SMPP 3.4 and send to every network in Sierra Leone, with delivery receipts back on the same connection.
# smpp.apphivesl.com:3550 · TLS
→ bind_transceiver system_id=yourlogin
← bind_transceiver_resp ESME_ROK
→ submit_sm from=YOURBRAND to=23276123456
← submit_sm_resp ESME_ROK id=cd47fcd1…a921
← deliver_sm stat:DELIVRD id=cd47fcd1…a921
→ deliver_sm_resp ESME_ROK
Why connect over SMPP
The industry protocol for high-volume SMS. If your platform already speaks it, you're most of the way there.
Keep your existing software
Point your SMSC client, gateway or messaging platform at Apphive. No new API to integrate.
Built for volume
A persistent connection with a speed limit agreed for your account. One-time codes are detected and sent through our express lane automatically.
Delivery receipts included
Standard SMPP 3.4 receipts on the same bind. If you disconnect, they wait for you for 2 days.
One account, one wallet
Same prices and wallet as the API, and every SMPP message shows up in your MySierraBox history.
What your engineers need to know
The full details, error codes and receipt format are in the onboarding guide.
Connecting
Host smpp.apphivesl.com
- SMPP 3.4
- Port 3550 for SMPP over TLS 1.2/1.3 (recommended), or 2775 plain
- Transceiver bind, or a transmitter plus a receiver
- Connections accepted only from your registered IP addresses
-
enquire_linkevery 30 to 60 seconds when quiet
Sending and receipts
submit_sm in, deliver_sm out
- Your approved sender IDs, the same as for the API
- GSM 7-bit or UCS-2 (
data_coding0 or 8) - Long messages as UDH or SAR parts
- Receipts with
DELIVRD/UNDELIVandreceipted_message_id - Unacknowledged receipts kept for 2 days
Who it's for
Aggregators and wholesalers
International and regional SMS hubs that need a reliable route into Sierra Leone.
Banks and fintechs
Core banking and payment platforms with SMPP built in, sending alerts and one-time codes.
Platforms and resellers
Messaging, betting and CRM platforms that already route SMS through SMPP.
Going live
Usually the same day.
Tell us about your setup
Send us your servers' public IP addresses and the sender IDs you'll use.
Get your login
We create your SMPP setup and send the login and password separately.
Send a test
Bind from a registered IP and send one message to a phone you can see, with a delivery receipt.
Start your traffic
Send at or below your speed limit. Need more? Ask us to raise it.
Questions
SMPP 3.4. Bind as a transceiver (recommended), or as a transmitter to send plus a receiver to get delivery receipts.
Yes. Port 3550 is SMPP over TLS 1.2 or 1.3 with a public certificate for smpp.apphivesl.com, and no client certificate is needed. Port 2775 is plain SMPP; some accounts require TLS.
Yes. Receipts arrive as deliver_sm in the standard SMPP 3.4 format with DELIVRD or UNDELIV, plus receipted_message_id and message_state. If you are not bound, receipts wait for you for 2 days.
Yes. Send them as parts with UDH or the SAR fields. All parts must reach us within 2 minutes. The message is billed per segment, the same as the API.
The same way as the API: from your prepaid Apphive wallet, at your account's API rates. SMPP messages also appear in your MySierraBox history. See pricing.
Contact us with the public IP addresses of your servers and the sender IDs you will use. We create your SMPP setup and send the login and password separately.
Ready to bind?
SMPP setups are created by our team. Send us your IP addresses and sender IDs and we'll get you connected. Prefer HTTP? See the SMS API.