Top 3 useful tools for our SMS messaging API
Every now and then we get asked about tools which make our API easy to integrate. So we put together a short list of tools used the most by all the developers our integration team has worked with.
Here are the three medallists.
1) LibrariesMessente has a list of libraries that help developers integrate us and use our API. The list includes libraries for Ruby, PHP, .NET and more. Some of the libraries have been created by us for our partners to make use of them. Some have been created by our friends and long time customers willing to share their tools with others. So whenever you connect to Messente be sure to check the list if there is something that can save you some precious development time.
2) Delivery report APIIn order for you to get accurate statistics about the success rate which which your messages are being delivered we have created an API for delivery reports. Every time an SMS is sent out we get a status report from the network operator who receives the message and forwards it to your customer's phone. Messente in turn forwards this information to you using the delivery report API.
One reason why some of our customers really like this API is because it makes our service very transparent - after all you get real time information on how many of your messages have been delivered. However, there is another advantage of having this information. It allows you to see which phone numbers in your customer database might be outdated or unreachable at the moment.
3) Automatic character convertingLocalising your message text into different languages might mean using characters not belonging to the GSM alphabet - cyrillic for example. The problem with this is that while it's ok to use those any of those characters it reduces the the maximum length of text in one SMS. So if you have prepared a text which includes even one or two non-GSM ones the 160 characters long text will actually be sent out as multiple SMS messages attached together. This in turn multiplies the sending costs of such a message.
To avoid this we have an automatic character converting system usable both for web based sender and for the API. It simply substitutes all the characters found in your message text to the closest looking suitable alternatives. Using the substitutions is of course optional and can be configured to match your preferences.
Hopefully this list will help you to save both time and costs when connecting to Messente. If you have any more questions about some other developer tools and useful functionality just let us know and we'll guide you through everything we have.