SMS
Voicebip sends and receives SMS through persistent SMPP v3.4 sessions to all four Nigerian MNO SMSCs — MTN, Glo, Airtel, and 9mobile. Messages are routed by number prefix with automatic failover.
Sending an SMS
Send an outbound SMS via the unified messages endpoint:
Response:
The message is queued for delivery via the appropriate MNO SMPP session. You receive delivery status updates through webhooks.
Receiving Inbound SMS
When a user sends an SMS to one of your provisioned +234 numbers, Voicebip delivers a message.received webhook to your endpoint:
Your agent can process the inbound message and reply using the same POST /v1/messages endpoint.
Auto-Segmentation
SMS messages are automatically split into segments when they exceed character limits:
The segments field in the response tells you how many segments the message was split into. Each segment is billed independently.
Voicebip detects the required encoding automatically. If your message contains any non-GSM-7 character (emoji, accented characters, CJK), the entire message is encoded as UCS-2.
Delivery Receipts
Voicebip requests delivery receipts (DLRs) from the MNO for every outbound message. When the MNO confirms delivery, a message.dlr webhook is sent:
Possible DLR statuses: delivered, failed, rejected, expired.
STOP Opt-Out Handling
Voicebip includes built-in opt-out keyword handling to comply with messaging regulations. When a recipient replies with any of these keywords, they are automatically opted out:
- STOP
- UNSUBSCRIBE
- CANCEL
- END
- QUIT
Keyword matching is case-insensitive. Once a number is opted out, any attempt to send an SMS to that number returns a 422 error:
Opt-out state is tracked per agent. A recipient can opt back in by sending START or SUBSCRIBE.
MNO Routing
Voicebip routes each SMS to the correct MNO SMSC based on the recipient’s phone number prefix:
If the prefix is unrecognized, the message is routed to MTN as the default carrier.
Failover
If the primary MNO SMSC is unreachable, Voicebip fails over through the chain: MTN -> Glo -> Airtel -> 9mobile. Failover is automatic and transparent — the API response is the same regardless of which SMSC delivers the message.
SMPP Infrastructure
Voicebip maintains one persistent SMPP v3.4 session per MNO SMSC. Key details:
- Keep-alive:
ENQUIRE_LINKevery 30 seconds - Throughput: bounded by MNO-allocated TPS per session
- Connection recovery: automatic reconnect with exponential backoff on session loss
Sandbox Testing
Use a pk_test_ API key to send SMS in sandbox mode. Sandbox messages are not delivered to real MNO networks — synthetic NATS events simulate the full lifecycle (queued, delivered). Billing is NGN 0.
Sandbox numbers: +234800000xxxx (test mobile virtual).