Skip to content
URBAN TECHNOLOGYURBAN TECHNOLOGY
UrbanSMPP · Messaging

An SMS gateway built for high volume.

UrbanSMPP is a professional SMS gateway built on the SMPP protocol and the open-source Jasmin engine. It is designed for critical transactional traffic — one-time codes, alerts, notifications — as much as for marketing campaigns.

Request test access →How it works
Protocol
SMPP 3.4
Engine
Jasmin (open source)

What is UrbanSMPP?

UrbanSMPP is a professional SMS gateway: your application connects to it once, and the gateway routes each message to the right operator. It relies on SMPP, the industry-standard protocol for exchanging SMS at volume, and on Jasmin, a proven open-source engine — a choice with a direct consequence for you: no proprietary format, no lock-in, a connection any technical team knows how to establish. You connect either over SMPP from your own system, or over HTTP if you prefer a simpler integration. The gateway handles queuing, retries and delivery receipts, so that a traffic spike does not turn into lost messages.

How does it differ from FasterMessage?

Both products send SMS, but they address different teams. UrbanSMPP is infrastructure: you connect your own system to it and drive everything through an API or an SMPP link. That is the right choice when sending is triggered by your application — a login code, an order confirmation, a threshold alert — and must go out within seconds, with no human involved. FasterMessage is a campaign platform: a management interface where a marketing team imports lists, writes a message, schedules a send and tracks results on a dashboard, without writing a line of code. Many organisations use both: the infrastructure for transactional traffic, the platform for campaigns.

How do you integrate UrbanSMPP into an existing application?

Two routes, depending on what your team has. The SMPP connection is the native route: you open a session to the gateway with a username and password, push your messages over that persistent link, and receive delivery receipts on the same session. It is the most efficient mode for sustained volume. The HTTP route suits you when you would rather not maintain a permanent session: you call an endpoint with the recipient number, the text and the sender ID, and you retrieve the status through a callback or by polling. In both cases, the sender ID — the name displayed instead of a number — must be registered beforehand with the relevant operators. We take care of that during onboarding.

Use cases

Who uses it, and for what

One-time authentication

Deliver a login code within seconds, with a delivery receipt: a code that arrives too late is a lost customer.

Transactional notifications

Confirm an order, a payment or an appointment, triggered directly by your application.

Critical alerts

Reach an on-call team or a network of field agents on a channel that works without mobile data or a smartphone.

Bulk campaigns

Broadcast to a large base, with a queue that absorbs the volume instead of dropping it.

Going further

Running a successful business SMS campaign: 7 mistakes to avoidBusiness SMS is read more than 90% of the time. You still have to avoid seven classic mistakes: here is how to get your campaigns right.Read the article →WhatsApp Business API or SMS: which one for your notifications?WhatsApp Business API or SMS for customer notifications? Cost, deliverability, message richness: the comparison to choose case by case.Read the article →SMS, WhatsApp or email: which channel for your critical messages?SMS, WhatsApp or email: how to pick the right channel to reach your customers in West Africa, based on purpose, cost and deliverability.Read the article →

Let's look at your volume together.

Tell us what you need to collect or send, and we come back with the operator coverage, the integration path and a price.

Request test access →