SMSLane provides easy to integrate and easy to use Free SMS API (http API) for developers to integrate it in their CRM. We also have SAP integration guidelines. Read How to integrate SMS in SAP. Our API supports both GET and POST methods.
Use of http SMS API into your application requires a simple approval by your account manager. All you need is just send us an API activation request to support@smslane.com mentioning your username/email id.
SMSLane provides API for sending promotional and transactional SMS. API structure for promotional and transactional SMS are similar except one additional parameter (gwid=2) required in case of transactional SMS. Ignoring this parameter may result in sending the SMS via promotional gateway and you may also get an error of “Insufficient Balance” if you do not have sufficient promotional SMS balance in your SMSLane account.
API structure and Parameter details are explained in the following section:
Single Message
http://apps.smslane.com/vendorsms/pushsms.aspx?apikey=yourapikey&user=abc&password=xyz&msisdn=919898xxxxxx&sid=SenderId&msg=test%20message&fl=0
Multiple Messages
http://apps.smslane.com/vendorsms/pushsms.aspx?apikey=yourapikey&user=abc&password=xyz&msisdn=919898xxxxxx,919898xxxxxx&sid=SenderId&msg=test%20message&fl=0
We highly recommend reading transactional SMS guide before using transactional SMS
Note :
1) Add one additional parameter gwid=2 in existing API as per example given below.
2) Kindly make sure your Senderid (sid) id and templates (msg) are approved in message text.
3) Download file to check how to integrate template and replace variable in message text.
Single Message
http://apps.smslane.com/vendorsms/pushsms.aspx?apikey=yourapikey&user=abc&password=xyz&msisdn=919898xxxxxx&sid=SenderId&msg=test%20message&fl=0&gwid=2
Multiple Messages
http://apps.smslane.com/vendorsms/pushsms.aspx?apikey=yourapikey&user=abc&password=xyz&msisdn=919898xxxxxx,919898xxxxxx&sid=SenderId&msg=test%20message&fl=0&gwid=2
Parameter Details
user: Your login username.
password: Your API password. This is different from your login password. You can view this password in your profile section
msisdn: Single mobile number or multiple mobile numbers separated by comma(12 digits with 91 e.g 919898123456).
sid: Approved sender id(Only 6 characters).
msg: Your message content (Maximum 459 characters including space. Considered as 3 messages).
fl: if message to be delivered as Flash then pass the value as 1 else 0
gwid: Gateway id 1 of promotional (default) and 2 for Transactions route.
Note: Only 100 mobile numbers are allowed in every http request.
http://apps.smslane.com/vendorsms/pushsms.aspx?apikey=yourapikey&user=yourUserID&password=yourPassword&msisdn=919898xxxxxx&sid=SenderId&msg=test%20message&fl=0&schedtime=23-12-2017-14-50
DateTime formate will be 23-12-2017-14-50
DD-mm-yyyy-hh-mm
http://apps.smslane.com/vendorsms/pushsms.aspx?apikey=yourapikey&user=yourUserID&password=yourPassword&msisdn=919898xxxxxx&sid=SenderId&msg=test%20message&fl=0&groupid=###
groupid = Your group Id (Login to your account and click on Manage Groups to find your groupid)
http://apps.smslane.com/vendorsms/pushsms.aspx?apikey=yourapikey&user=yourUserID&password=yourPassword&msisdn=919898xxxxxx&sid=SenderId&msg=परीक्षण संदेश &fl=0&dc=8
dc=8 :- Kindly add this additional parameter for unicode message.
Check Delivery API :
http://apps.smslane.com/vendorsms/checkdelivery.aspx?user=demo&password=demo&messageid=messageid&type=1
Response : #DELIVRD
Delivery API with Date Time Stamp
http://smslane.com/vendorsms/checkdelivery.aspx?user=demo&password=demo&messageid=your-messageid&type=1
type=1 :- Kindly add this additional parameter for getting the Delivery Time of SMS.
Response : #DELIVRD | 3/9/2017 2:28:31 PM
Promotional: http://apps.smslane.com/vendorsms/CheckBalance.aspx?user=demo&password=demo
Transactional : http://apps.smslane.com/vendorsms/CheckBalance.aspx?user=demo&password=demo&gwid=2
Response : Success#177
Note: Only the above-defined validations are performed at the server side. All other validations for any parameter are required to be handled at the client side explicitly.