Bulk SMS Gateway API Service


In computer programming, an application programming interface (API) specifies how some software components should interact with each other.In addition to accessing databases or computer hardware, such as hard disk drives or video cards, an API can be used to ease the work of programming graphical user interface components. In practice, many times an API comes in the form of a library that includes specifications for routines, data structures, object classes, and variables. In some other cases, notably for SOAP and REST services, an API comes as just a specification of remote calls exposed to the API consumers. An API specification can take many forms, including an International Standard such as POSIX, vendor documentation such as the Microsoft Windows API, the libraries of a programming language, e.g., Standard Template Library in C++ or Java API. Web APIs are also a vital component of today’s web fabric. An API differs from an application binary interface (ABI) in that an API is source code based while an ABI is a binary interface. For instance POSIX is an API, while the Linux Standard Base is an ABI.

Promotional SMS API :

Single Message


Multiple Messages


Note : For Promotional SMS your sid=WEBSMS….Always use sender id in capital.
Note : Add one additional parameter gwid=2 in existing API as per example given below.

Transactional SMS API :

Single Message


Multiple Messages

user: Your login username.
password: Your login password.
msisdn: Single mobile number or multiple mobile numbers separated by comma(10 digits or +91).
sid: Approved sender id(Only 6 characters).
msg: Your message content(Minimum 459 characters/3 messages). Note: If you are using template then edit only the dynamic part which is in ##Field##.
fl: if flash message then 1 or else 0
gwid: 2 (its for Transactions route.)
Note: Only 100 mobile numbers are allowed.

Message Response :

Single Message

{“ErrorCode”:”000″,”ErrorMessage”:”Success”,”JobId”:”381a8090-b230-42fa-ac04-157cc2142bfa”,”MessageData”:[{“MobileNumber”:”919898xxxxxx “,”MessageParts”:[{“MessageId”: “919898xxxxxx -67e3765cdf034f438a432eacb88d0c14″,”MessagePartId”:1,”MessageText”:”test message”}]}]}
Multiple Message

{“ErrorCode”:”000″,”ErrorMessage”:”Success”,”JobId”:”733956ef-f6ab-46fc-81cc-bd3be775c1b7″,”MessageData”:[{“MobileNumber”:”919898xxxxxx”,”MessageParts”: [{“MessageId”:”919898xxxxxx -3af24da377d645b9ab78c0e3ac176e32″,”MessagePartId”:1,”MessageText”:”test message”}]},{“MobileNumber”:”919898xxxxxx “,”MessageParts”:[{“MessageId”:”919898xxxxxx -f01df98db3ba4b39a8b0254277689939″,”MessagePartId”:1,”MessageText”:”test message”}]}]}


Schedule SMS :

http://login.smsgatewayindia.in/vendorsms/pushsms.aspx?user=yourUserID&password=yourPassword&msisdn=919898xxxxxx&sid=SenderId&msg=test%20message&fl=0&schedtime=2013/12/30 20:30:00 PM

DateTime formate will be
2014/10/06 20:30:00 PM
yyyy/mm/dd hh:mm:ss PM

Group SMS :


groupid = your group Id

For Unicode Message :

Promotional Unicode Message API

http://login.smsgatewayindia.in/vendorsms/pushsms.aspx?user=yourUserID&password=yourPassword&msisdn=919898xxxxxx&sid=SenderId&msg=परीक्षण संदेश &fl=0&dc=8

Transactional Unicode Message API

http://login.smsgatewayindia.in/vendorsms/pushsms.aspx?user=yourUserID&password=yourPassword&msisdn=919898xxxxxx&sid=SenderId&msg=परीक्षण संदेश &fl=0&dc=8&gwid=2

Check Delivery API :


Response : #DELIVRD

Credit Blance API :


Response : Success#Promotional:0|Transactoinal:95



Single Message

Multi Message

Transactional XML API
Kindly update  in xml for sending transactional message.

Error Message


ErrorCodeError Message
000Success (it means message is successfully submitted and you can check message parameter response to check message id and parts)
001Account details cannot be blank
002Username or password cannot be blank
003SenderId cannot be blank
004Message cannot be blank
005Message properties cannot be blank
006ServerError#Error message
007Invalid username or password
008Account inactive
009Account lock
010Unauthorized API access
011Unauthorized IP address
012Message length violation
013Invalid mobile numbers
014Account locked due to spam message contact support
015Invalid SednerId
016Transactional account not active
017Invalid groupid
018Cannot send multi message to group
019Invalid schedule date
020Message or mobile number cannot be blank
021Insufficient credits
022Invalid jobid
023Parameter missing
024Invalid template or template mismatch

Message Length – Multipart Messages :

Standard GSM 03.38 Character Set

Single text messages are limited to 160 characters, including spaces. The maximum length of two-part or three-part multipart text messages is 306 (2 x 153) and 459 (3 x 153) characters, respectively. You could send up to 1000 characters as multipart message which will be split into 7 messages internally. This refers only to messages that contain the standard GSM 03.38 character set.Each multipart text message is limited to 153 characters rather than 160 due to the need for user-data headers (UDHs) information. Mobile phones use UDH information to enable them to link long messages together so that they appear as single SMS messages in recipient’s phone inbox.

Number of SMSNumber of characters in the linked SMS
1160 characters
2306 characters (2 x 153)
3459 characters (3 x 153)
71000 characters (6 x 153) + (1 x 82)
Unicode Characters

Using Unicode, for languages such as Hindi, restricts your message to a maximum of 70 characters per SMS. You can, however, send longer text messages, with our system splitting them into two or at the three separate text messages. The maximum lengths of two-part and three-part multipart Unicode text messages are 134 (2 x 67) and 201 (3 x 67) characters, respectively. You could send up to 500 characters as multipart message which will be split into 8 messages internally.

Number of SMSNumber of characters in the linked SMS
170 characters
2134 characters (2 x 67)
3201 characters (3 x 67)
8500 characters (6 x 67) + (1 x 31)

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.