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.

Startup Conferences: What’s the point? (Slush 2017)

20 Oct 2017

With Slush coming up in about a month, it’s a good time ponder the purpose of large startup conferences. Many entrepreneurs head to conferences, like Slush, around the world and throughout the year looking for investments from venture capitalists and angel investors, yet there’s a lot more to gain from startup conferences. Think about it: there will be over 17,000 motivated and creative people in one place at one time. Get creative and gain as much as you can out of the experience.

Yuriy Mikitchenko

Yuriy Mikitchenko

The economics behind undelivered, failed SMS messages    

17 Oct 2017

The cost and full impact of undelivered or failed messages isn’t immediately clear. The financial impact is not simply the combination of the failed SMS and the cost to resend the message, which isn’t very much at times. There are other indirect costs that result from undelivered SMS messages that matter from a financial perspective. Let’s take a deeper look into the ripple effect of undelivered messages, which make the reasons behind our focus on SMS delivery quality even more clear.

Here are a few examples.

Uku Tomikas

Uku Tomikas

Fraud and Security: 2FA Considerations for PSD2

10 Oct 2017

The second Payment Services Directive (PSD2) is less than three months away from enforcement. While the regulation’s text is lengthy, a key component of the law is its extended reach in comparison to the first directive. PSD2 applies to all payment service providers and affiliates, including account information service providers and payment initiation service providers. In addition, the law applies when at least one part of the transaction is in the European Union. This means that payment service providers and their affiliates outside of the EU must comply with the law when the payer is in the EU. The additional geographical reach guarantees the same level of security expectations for all EU residents regardless of the location of the payment service provider.

Raili Liiva

Raili Liiva

Start sending messages to

for € N/A

Contact us