SmartSMSSolutions Application Programme Interface (API)

SmartSMSSolutions offers you the opportunity to send SMS without visiting the website through its powerful Application Programme Interface (API). With the API you can send SMS from a Standalone Application, Web Application, Mobile Application, Website, etc. In addition you can check your SMS balance with the API.


SmartSMSSolutions Bulk SMS API Userguide for SPC 3 & 4

SmartSMSSolutions Bulk SMS API Userguide for SPC 3 & 4


SmartSMSSolutions Bulk SMS API Userguide for SPC 3 & 4

SmartSMSSolutions HTTP POST & GET Bulk SMS API Userguide



Below is the API configuration for SENDING SMS.,2348030000000&message=YourMessage

Below is the API cofiguration for CHECK SMS Balance.


Below is the explanation of the components of the API


Username: Your SmartSMSSolutions account username

Password: Your SmartSMSSolutions account password

Sender: The sender ID to show on the receipient's phone

Message: The text message to be sent

Recipient : The destination phone numbers. Separate multiple numbers with comma(,)

Balance: Set to "true" only when you want to check your credit balance

Schedule: Specify this parameter only when you are scheduling an SMS for future delivery. It should contain the date the message should be delivered. Supported format is "2011-10-01 12:30:00" i.e "YYYY-MM-DD HH:mm:ss"



Below is the list of the Server Responses and their meanings

2904=SMS Sending Failed
2905=Invalid username/password combination
2906=Credit exhausted
2907=Gateway unavailable
2908=Invalid schedule date format
2909=Unable to schedule
2910=Username is empty
2911=Password is empty
2912=Recipient is empty
2913=Message is empty
2914=Sender is empty
2915=One or more required fields are empty
2916=Sender ID not allowed


For instance, after sending a message, a response similar to the one below might be generated.

OK 21 08033333333,08022222222,08055555555

This means: OKno of sms credits usedgsm numbers that failed

where 21=no of sms credits used
and 08033333333,08022222222,08055555555 are the 3 numbers that failed

Note that it is of best practice to urlencode the API for successful delivery.