Messente avatar logo

Top 5 Most Common Mistakes When Implementing SMS Messaging API

- 5 MIN READ - 20 Oct 2013

Implementing SMS messaging to your existing web app is always a hassle and takes some time to get everything right.

Spending days on implementing some appearantly simple API is not very interesting and this usually results in extra coffee break for the developer instead of adding one more "if-then-else" to the code.

Messente for example has multiple Helper Libraries for most popular programming languages that do the heavy-lifting for you to avoid some common mistakes but you should not overlook most common practices.

1. Check the Response Code and Act Accordingly

Usually developers check if the SMS was successfully sent to the service provider and if there is an error, the app tries to send the text again or just skips it.

When an error code is returned there should be at least two different processes implemented:

In either case, server administrator should be notified that an error occurred and someone should look into it, which lead us to the next point.

2. No Notification System in Case of an Error

When error code is returned for the message sending request, there could be dosens of reasons why it failed.

In every case, server administrator should be somehow notified that something unexpected happened with the SMS messaging service.

Having internal notification system will help you avoid most common causes like for example when the account runs out of credits.

3. Your IP Address has Changed

Messente has implemented IP-based filters for API calls to block requests from unwanted servers.

When possible, get your server a static IP address. You can also add a list multiple IP addresses in the API settings to allow requests to be made from multiple servers.

4. Incorrect Encoding of the Message Body

The most commonly used character encoding in the web is UTF-8, that supports all the characters from all alphabeths. This is also what Messente assumes you are using.

When testing out the API and everything seems to be working with simple “abc”, you might run into trouble when suddenly you need to send text with “ñ” character in it.

If you are using some other encoding like Western (ISO-8859-1) or Cryllic (KOI8-R), first convert the text to UTF-8.

Or when that is not possible, just let Messente know what encoding you will be using and it will take care of it.

5. Backup Route is Not Implemented

You are still able to send SMS messages even when the main server is having hickups by simply switching to a backup server.

It happens rarely that Messente’s main server is down, but when nature is having a bad day, nobody is safe.

What’s Next?

Stay tuned for next versions of API helper libraries by following us on Twitter or Facebook.

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