API VERSION 3.0
Introducing our new API V3 that is developed to enhance your messaging experience with reduced complexity.
This User Manual provides specifications of the API for the automated sending of SMS via the Internet. This guide is intended for the developers and clients alike who plan to integrate their systems with Bulk SMS service.
In order to use our API, you will need to have a system that has internet connectivity. This may be direct internet connectivity or via a firewall or proxy server. Additionally, should you wish to receive delivery reports (DLRs), you must have a web server that is able to receive incoming requests from the Internet. This web server does not necessarily have to be running on the same machine that is sending messages to us.
This is one of the simpler server-based method of communication. It can be used either in the form of a HTTP POST or HTTP GET. We recommend POST for larger data transfer and data security. All calls to the API must be URL-encoded. The parameter names are case sensitive.
Note: We recommend POST for larger data transfer and data security. All calls to the API must be URL encoded.
Our API supports both HTTP and HTTPS. Using HTTPS to encrypt all requests through SSL is recommended, but if you’re using a client and tool that’s not set up to make SSL requests, you can use HTTP. All requests are secured through BASIC authentication via the Working Key. An additional level of protection is provided where working key can be configured to accept requests from a specific IP Address only. Also, API usage with username & password combination is removed due to security concerns.
Please sign up for testing our SMS API via our complete document with SMS credits.