Bulk SMS Mobile industry news

Working with customers and such a wide range of consumers with different needs, level of computer literacy etc., surely makes my life interesting. Besides just dealing with technical and customer service, it is a learning curve constantly reminding all of us that customer education is crucial - not just essential.

We so easily take knowledge for granted and if there is something someone could learn reading this blog, it makes my day. So, in an attempt not to use all the highly technical stuff, I always try to put things in simple words and language.

Today I decided to take a non-technical look at the HTTP api's which are required for customers to enable web based sms services on their web sites. I guess the technies will laugh at me but let's have some fun. Please feel free to comment or add anything that I post here.

So what is a http api?
Let's take a look at the webopedia definition:
Short for HyperText Transfer Protocol, the underlying protocol used by the World Wide Web. HTTP defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. For example, when you enter a URL in your browser, this actually sends an HTTP command to the Web server directing it to fetch and transmit the requested Web page.

This reminds me that computers are only as clever as the people that operate them. Same goes for the web. If you do not give the right command, then you will not be able to obtain the desired results.

The Streaming SMS and Bulk SMS industry use http api's using POST and GET commands to send and receive SMS, pictures, logos, concatenated messages, WAP bookmarks etc. from web sites.

So in short, the SMS company will supply the correct URL for clients to use in order to be able to send messages from their sites. As simple as that.

Tomorrow we will look at a sample http api

For more information in the mean time, please visit our HTTP API page if you are curious and requries more information.