Messente avatar logo

Why HTTP API is so much better compared to SMPP protocol

- 5 MIN READ - 12 Jan 2014

SMPP has long been industry standard for sending SMS over the Internet but HTTP API’s have quietly made it’s way to the top.

In Messente we clearly flavor HTTP API to SMPP for three main reasons – simplicity, speed and features.

Simplicity

Setting up SMPP connection requires you to have special knowledge about the protocol and the number of free software is also very limited. HTTP protocol tools on the other hand are freely available for almost all programming languages and they are extremely simple to use.

Developing your own SMPP client may take several months – using some free software may speed things up but will also have some limitations. Developing your own script for sending SMS messages over HTTP API takes just one day from scratch.

Messente also offers multiple HTTP API libraries in lots of flavors – starting with PHP library and ending with Microsoft.NET version. Make your pick.

Speed

SMPP had an edge over HTTP mostly when sending thousands of messages per day – but no more. Especially with the HTTP 1.1 persistent connections, protocol overheads have decreased significantly.

Quote from a study by W3 Consortium about the HTTP/1.1 pipelining (persistent connection):

HTTP/1.1 implemented with pipelining outperformed HTTP/1.0, even when the HTTP/1.0 implementation uses multiple connections in parallel, under all circumstances tested. In terms of packets transmitted, the savings are typically at least a factor of two, and often much more, for our tests. Elapsed time improvement is less dramatic, but significant.

HTTP/1.1 allows developers to use (multiple) persistent connections to achieve same speeds that only SMPP could deliver a few years ago. And keep in mind, that using HTTP API’s it significantly easier for developers.

More features

SMPP protocol is very strictly documented and there is not much you can do to add new features. HTTP API on the other hand is very flexible and new features can be added with ease.

Let’s say you wanted to schedule a text message – a reminder for example. You could not do that with SMPP but it is already built in to Messente’s HTTP API – just add one more parameter to your request and you are done.

Conclusion

SMPP protocol will stay for many years to come, but new users will mostly start implementing HTTP API’s just for the sheer simplicity it provides.

If you are starting with SMS messaging, there is no need for you to start with SMPP protocol – in my mind there is so much more to do with your time

Jaanus Rõõmus

Jaanus Rõõmus - CTO

Jaanus is co-founder and CTO of Messente and makes sure its wheels keep spinning and Messente always has a full tank of fuel.

Have you met 1oT? Mobile data connectivity for IoT companies.

24 Apr 2018

Last week, Lauri wrote a good piece about keeping things real, because businesses have simple business models at their core. As one of our values, simplicity has led Messente to build a reliable and powerful SMS API and user authentication API for businesses and brands to communicate with their customers globally.

While we pride ourselves in doing global A2P SMS and 2FA very well, one of our sister companies, 1oT, uses a similar methodology of simplicity to do global internet of things (IoT) and machine-to-machine (M2M) connectivity really well.

Yuriy Mikitchenko

Yuriy Mikitchenko

A note on keeping things real

17 Apr 2018

Over the years, I've had the good fortune of talking to and doing business with many entrepreneurs and CEOs from a variety of industries. Some are first-time founders of small startups, while others are amazingly experienced serial entrepreneurs. Many of them are extremely successful in what they do.

So naturally, while listening to them talk about their businesses, I've always tried to spot any fundamental takeaways –the small drops of universal business advice distilled from those hundreds of conversations.

And it seems to me that a lot of the most profound business truths seem to point to a direction that I would call, "keeping it real.”

Lauri Kinkar

Lauri Kinkar

Next-generation Omnichannel API is well underway

10 Apr 2018

Over the last few months we’ve been setting the direction of our Omnichannel messaging API and our development team has started working on it. Considering transparency, we wanted to share the progress we’ve made on the API and give our clients something to look forward to, as well as helping clients prepare their systems for the next generation of our A2P messaging API.

Uku Loskit

Uku Loskit

Start sending messages to

for € N/A

Contact us