• here
  • Home
  • Developers API

About API

Developers API

BULK SMS – Founded in 2010 in headquarters in New Delhi India , MY SMS APP , we are unique by our one stop solutions Bulk SMS Services addressing customers of all sectors . We are involved in offering end to end Web , Data & Voice Communication solutions; may be its new setting or optimizing current operations , we provide better ways of working , we ensure that our solutions significantly influence bottom lines and help our customers lower their total cost of ownership.

Business enterprises looking for customized end-to-end and/or comprehensive software solutions, MY SMS APP is the answer. The uppermost priority in our minds is rationality of purpose for a client’s site. Web Technologies like Bulk SMS Services, Website Redesigning, Web Application Development, Portal Development, Flash Intros, SEO (Search Engine Optimization), Website Maintenance, Web Promotion, Website Designing(Commerce Website, Static Website, CMS, Dynamic Website, Personal Websites),are few of our services what we offer.

API REFERENCE

Overview

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.

Required Environment

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.

SSL Enabled API Triggering

This API has been designed to allow you to access it using an SSL Enabled connection for added security.

To trigger the API on an SSL enabled connection, enter the URL beginning with https:// instead of http://

Mobile Phone Number Format

All mobile phone numbers submitted via API should be a valid 10 digit mobile number starting from 7, 8 or 9. For example: 9xxxxxxxxx, 8xxxxxxxxx, 7xxxxxxxxx.If mobile number exceeds 10 digits the last 10 digits will be considered as a mobile number. For example: 919xxxxxxxxx will be considered as 9xxxxxxxxx

Security

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.

Output Restrictions

If the provider network is down, our Gateway Servers will retry your message up to six hours before giving up. Also, Duplicate messages in single request only are filtered by default. A “duplicate message” is defined as the same destination address, sender address and the message body. However, duplicate messages sent by different request are NOT filtered.

Input Restrictions

All the parameter passed must be provided in the URL encoded format. Also, recommended to use the POST method for error free submission due to URL limitations.

Sender ID Options

All text messages carry a sender ID. When you send a text message through API, you could use any of the approved sender IDs for your account. You can reach us for applying for a new sender ID.

Setting a Sender ID (Alphabetic Originator)

You can set the sender ID with your company name, or anything. So, this means that your recipients could see the name you want in the sender field rather than just a phone number. This alphabetic originator, or sender ID, can contain characters from a-z, A-Z. Other characters may cause messages to fail.

Supported Character Sets

GSM 03.38 Encoding

The standard SMS mobile-phone character set is used universally to send text messages. The standard character set allows few of the Roman alphabet and the most common accented forms, certain special characters, and few Greek alphabets that sum up to 160 characters. It includes the following characters:

@ £ \ $ ¥ è é ù ì ò Ç \ n Ø ø \ r Å å ? _ F ” ? O ? ? S T ? Æ æ ß É ! \ ” # ¤ % & ‘ ( ) * + , – ../ 0 1 2 3 4 5 6 7 8 9 : ; < = > ? ¡ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z ? Ö Ñ Ü § ¿ a b c d e f g h I j k l m n o p q r s t u v w x y z ö ñ ü à ä Ä { } \ ~ [ ]

Note: All extended characters will take two characters to send. Extended characters are: £ ¥ è é ù ì ò Ç Ø ø Å å Δ Φ Γ Λ Ω Π Ψ Σ Θ Ξ Æ æ ß É ¤ ¡ Ä Ö Ñ Ü § ¿ ä ö ñ ü à | \ { } ~ [ ] ^ Also, extended character like € takes three characters to send.

Unicode

When using non-GSM 03.38 characters SMS transmits as a Unicode message. The Unicode character support provides the ability to send a message in Hindi, Kannada, Tamil etc.

If the message to be transmitted is in Unicode format, the entire message has to be converted into Unicode. Also, Unicode transmission will charge double the credits, including plain English SMS sent in Unicode mode.

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
1upto 160 characters
2upto 306 characters (2 x 153)
3upto 459 characters (3 x 153)
4upto 612 characters (4 x 153)
5upto 765 characters (5 x 153)
6upto 918 characters (6 x 153)

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
1upto 70 characters
2upto 134 characters (2 x 67)
3upto 201 characters (3 x 67)
4upto 268 characters (4 x 67)
5upto 335 characters (5 x 67)
6upto 402 characters (6 x 67)
7upto 469 characters (7 x 67)
8upto 500 characters (7 x 67) + (1 x 31)

Successful Submission of SMS

For each successful submission of an SMS, the API would return a unique message ID for that transaction. The Client’s Application should capture the unique message ID and fetch a Delivery Report (DLR) against that corresponding message ID. This message ID then can be used to track the status of the message and receive the delivery report against this message ID through the delivery report URL specified by the client.

Response Formats

By default, the API URL generates responses in JSON format. You can also generate responses in XML, PHP, JSONP formats. All you need to do is add &format=php (for PHP format) or &format=xml (for XML format).

Response Parameters

The response parameters in case of error in API are tabulated below:

NameParameterDescriptionExpected Values
Response codestatusError code for your api callNumeric Value A401,E601 etc
Error MessagemessageError Message for API callString.Refer API Error codes section

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API in the below format are :

STATUSMESSAGE
A400Api file not found in project
A401AMethod Not Implemented.
A401BMethod Not Found
A402Api Key not found.
A403Api Signature not found
A404Your api account got suspended
A405Api secret not found.
A406Request is not allowed from this ip
A407Header misconfigured
A408Api Signature not equal

SMS Status Codes-HTTP API(On Submission)

When we receive an API call for sending SMS one of the following status code is attached at the application level. However, operator level status codes are tabulated next.

The common status codes received while using the API are:

AWAITED-DLRMobile number has been accepted and submitted to the operator. Awaiting delivery report from the operator
DNDNUMBMobile number is DND.
OPTOUT-REJOptout from subscription.
INVALID-NUMIn case any invalid number present along with the valid numbers.

SMS Status Codes-XML/JSON API(On Submission)

There could be one or more nodes in an XML API, each of those nodes could have a different status code on submission

The common status codes received while using the API are:

AWAITED-DLRMobile number has been accepted and submitted to the operator. Awaiting delivery report from the operator
DNDNUMBMobile number is DND.
OPTOUT-REJOptout from subscription.
INVALID-NUMIn case any invalid number present along with the valid numbers.
SENDER-ID-NOT-FOUNDIn case the sender ID given in any one of the nodes is not available
INV-TEMPLATE-MATCHIn case the message given in any one of the nodes does not match the template approved for the sender ID in the same node
MAX-LENGTHIn case the message given in any one of the nodes exceeds the maximum of 1000 characters

SMS Status Codes(Operator Level)

On submission of a message to operator, we associate one of the following status codes to every SMS in order to track the status

The common status codes received while using the API are

NO-CREDITSInsufficient credits.
SERIES-BLOCKMobile number series blocked.
INV-NUMBERInvalid number.
SERVER-ERRServer error
SPAMSpam SMS
SNDRID-NOT-ALLOTEDSender ID not allocated.
BLACKLISTBlacklisted number
TEMPLATE-NOT-FOUNDTemplate not mapped.
INV-TEMPLATE-MATCHTemplate not matching approved text.
SENDER-ID-NOT-FOUNDSender ID not found.
DNDNUMBDND registered number.
NOT-OPTINNot subscribed for opt-in group.
TIME-OUT-PROMTime out for promotional SMS.
DELIVRDSMS successfully delivered.
INVALID-SUBNumber does not exist. / Failed to locate the number in HLR database.
ABSENT-SUBTelecom services not providing service for the particular number. / Mobile Subscriber not reachable.
HANDSET-ERRProblem with Handset or handset failed to get the complete message. / Handset doesn't support the incoming messages.
BARREDEnd user has enabled message barring system. / Subscriber only accepts messages from Closed User Group [CUG].
NET-ERRSubscriber's operator not supported. / Gateway mobile switching error.
MEMEXECHandset memory full.
FAILEDSMS expired due to roaming limitation. / Failed to process the message at operator level.
MOB-OFFMobile handset in switched off mode.
HANDSET-BUSYSubscriber is in busy condition.
SERIES-BLKSeries blocked by the operator.
EXPIREDSMS expired after multiple re-try.
REJECTEDSMS Rejected as the number is blacklisted by operator.
OUTPUT-REJUnsubscribed from the group.
REJECTED-MULTIPARTValidation fail [SMS over 160 characters]
UNDELIVFailed due to network errors.
NO_DLR_OPTRIn case operator have not acknowledge on status report of the SMS.

Sending An SMS

HTTP API sends a text message using POST/GET and form-encoded data. The URL you use to send a text message has a required field called api_key, which is unique and assigned to your account.

The other required parameters for the Request are method,sender, to and message, which are used to define the destination phone number and the message body. If you want to send to multiple phone numbers, provide the numbers in comma separated format.

To send an SMS using the HTTP API, the following URL format is used:

https://www.mysmsapp.in/api/push.json?apikey=<apikey>&sender=<senderid>&mobileno=<mob>&text=<text>

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
delivery reports URLdlrurlThe URL to receive delivery reports. Spiffing custom is mandatory.delivery reports URL
Message IDcustomCustom message ID by customer, comma separatedAlphanumeric (max 40 char)
Schedule timetimeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM
unicodeunicodeTo specify that the message to be sent is in unicode format. Also can be used for automatic detection of unicode SMS.1 / 0 / auto
flashflashTo specify that the message is to be sent in the flash format1 or 0

Advanced Parameters(Optional)

The advanced parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
Callback function namecallbackCallback function for JSONP response format.String
Custom reference fieldscustom1 & custom2Custom reference fieldsAlphanumeric (max 40 char)
port numberportPort number to which SMS has to be sentValid integer port number above 2000

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send an SMS is in the below format :

ErrorCodeDescription
0NORMAL DELIVERED
1Source not found|EC_UNKNOWN_SUBSCRIBER
2Sink not found|EC_UNKNOWN_BASE_STATION
3Delivery zone not found|DND Fail
5Location not found|EC_UNIDENTIFIED_SUBSCRIBER
6Location blocked|Absent subscriber
7Reply path not found|UNKNOWN EQUIPMENT
8Message not submit|FSM TIMEOUT
9Unsupported number plan|EC_ILLEGAL_SUBSCRIBER
10Unsupported type of number|EC_BEARER_SERVICE_NOT_PROVISIONED
11Message not DELIVER or STATUS|EC_TELESERVICE_NOT_PROVISIONED
12Dialling zone not found|EC_ILLEGAL_EQUIPMENT
13Not home zone and IMSI not allowed|EC_CALL_BARRED
14Not home zone and IMSI fetch failed|Barred unauthorized message originator
15Screening block|CUG REJECT
18ESME error|message waiting for report expired'
19Originating location mismatch|SRIAck unsuccessful with any other error codes'
20Originating reservation failed|EC_SS_INCOMPATIBILITY
21Originating reservation denied subscription not found|EC_FACILITY_NOT_SUPPORTED
22Originating reservation denied subscription state illegal|Memory capacity exceeded
23Originating reservation denied call case blocked for subscription|Unknown Subscriber'
24Originating reservation denied call case blocked for subscription type|call forbidden'
25Originating reservation denied low balance|the network does not support SMS'
26'teleservice not supported'
27Absent subscriber
29'HLR:data error in route signal'
30Terminating reservation failed|HLR:data lacked'
31Terminating reservation denied subscription not found|EC_SUBSCRIBER_BUSY_FOR_MT_SMS
32Terminating reservation denied subscription state illegal|EC_SM_DELIVERY_FAILURE
33Terminating reservation denied call case blocked for subscription|EC_MESSAGE_WAITING_LIST_FULL
34Terminating reservation denied call case blocked for subscription type|EC_SYSTEM_FAILURE
35Terminating reservation denied low balance|EC_DATA_MISSING
36EC_UNEXPECTED_DATA_VALUE
37'Unmarked Subscriber'
38'failure because the subscriber is busy'
39'VMSC isolated'
40System is congested|VMSC:data lacked'
41Originating IMSI mismatch|VMSC:unexpected data'
42'MS error'
43Not Supported by equipment
44Illegal equipment
45Quarantine Add|Unspecific PID Error
46Quarantine Remove|Message Class Not Supported
47DCS error
48TPDU Not Supported
49Short message delivery failure with memory capacity exceeded
50Unexpected error from Store|UNKNOWN ERROR
51Direct delivery disabled from store|EC_RESOURCE_LIMITATION
53Message limit exceeded|Subscriber Busy For MT-SMS
54Retry scheme ended|Data Download Error
60Originator blocked|Absent subscriber
61Destination blocked|Absent subscriber
62Keyword blocked|Absent subscriber
63SC address blocked|Absent subscriber
64Blocked due to exceeded quota|Absent subscriber
65Loop detected|Absent subscriber
66Data coding scheme blocked|Absent subscriber over GPRS Page Fail
67Information element identifier blocked|Absent subscriber over GPRS Detached
68Country Code Validation Block|Absent subscriber over GPRS Deregistered
69Destination Flooding
70No ESME provider available|MS store is full'
71ESME account not connected|EC_UNKNOWN_ALPHABET
72No ESME sub account routing|EC_USSD_BUSY
74ESME local throttling - exceeded msg/s|INVALID HEADER IN MSG
80Home routing sender GT mismatch|PENDING DLR (Retry )
81Location mismatch between provided location and location known to HLR.|Service not supported
82IMSI mismatch between provided IMSI |Mistyped parameter
83Local throttling by sink|No response from the peer
84The IMSI could not be retrieved from the HSS|Resource limitation
85The IMEI of the UE is unknown|Initiating release
86The user location is unknown|Unrecognised error
87ESME router|Provider Error (In case of any failures observed in TCAP level this error will generate).
88Network fluctuation from far End Operator(Temporary Error)
89INVALID PACKET AT SMSC LEVEL
90USER-ABORT
91PROVIDER-ABORT
92MSC NUMBER MISSING
93Equipment protocol error
94Equipment not SM equipped
95Unknown service centre
96Service Centre congestion
97INVALID SCHEDULE DELIVERY TIME
98Subscriber not SC subscriber
99Invalid SME address
100Unidentified subscriber|no response from the called subscriber'
101Facility not supported|VMSC:the called MS poweroff'
102System failure|VMSC:limited due to MS roaming' / SENDER ID BLOCKED
103Unexpected data value|ROUTE NOT ACTIVE
104Data missing|OFF-NET NOT ACTIVE FOR ACCOUNT/ ON-NET ROUTES NOT DEFINED
105Equipment protocol error|MTP_FAILURE
106UNKNOWN service centre address|MS response is overtime'
107Service centre congestion|HLR:the subscriber is unregistered'
108Invalid short message entity address|ROUTE BLOCKED FOR THIS SERIES
109Subscriber not service centre subscriber|MSISDN SERIES NOT CONFIGURED
110Reject|NOT ABLE TO GET FINAL ROUTE
111Local cancel|Queue_Unvailable
112Abort|NOT A VALID TEMPLATE
113Exception|MANDATORY WORDS NOT FOUND
114UNKNOWN|DEFAULT ROUTE NOT FOUND IN CONFIGURED ROUTES
115ROUTE NOT CONFIGURED AT PLATFORM LEVEL
116Map Dialog P Abort Indication Provider Reason: Maintenance Activity
117Map Dialog P Abort Indication Provider Reason: Version Incompatibility
118Map Dialog P Abort Indication Provider Reason: Abnormal Dialogue
119MAP_DLGUA_UsrRsn_NTR_MapDlgUnavailable
120MAP_DLGUA_UsrRsn_NTR_MapNotConfigured
121MAP_DLGUA_UsrRsn_NTR_OtherErr
122MAP_DLGRJT_PrvRsn_NotSent
123INTERNATIONAL ROAMING
124EC_OR_appContextNotSupported
125EC_OR_invalidDestinationReference
126EC_OR_invalidOriginatingReference
127EC_OR_encapsulatedAC_NotSupported
128EC_OR_transportProtectionNotAdequate
129EC_OR_noReasonGiven
130EC_OR_potentialVersionIncompatibility
131EC_OR_remoteNodeNotReachable
132Map Dialog Rejected Refuse Reason: Application Context not supported
133Map Dialog Rejected Refuse Reason: Potential Version Incompatibility
134Map Dialog Rejected Refuse Reason: Remote Node not reachable
135Map Dialog Rejected Provider Reason: Provider malfunction
136Map Dialog Rejected Provider Reason: Transaction Released
137Map Dialog Rejected Provider Reason: Resource Limitation
138Map Dialog Rejected Provider Reason: Maintenance Activity
139Map Dialog Rejected Provider Reason: Version Incompatibility
140Map Dialog Rejected Provider Reason: Abnormal Dialogue
141Map Dialog User Abort Diagnostic Info: Short Term resource Limitation
142Map Dialog User Abort Diagnostic Info: Long term resource limitation
143Map Dialog User Abort Diagnostic Info: Handover cancellation
144Map Dialog User Abort Diagnostic Info: Radio Channel Release
145Map Dialog User Abort Diagnostic Info: Call Release
146Map Dialog User Abort Diagnostic Info: Network path Release
147Map Dialog User Abort Diagnostic Info: Associated Procedure release
148Map Dialog User Abort Diagnostic Info: Tandem Dialog Release
149Map Dialog User Abort Diagnostic Info: Remote Operation Failure
150UNKNOWN subscriber|Map Dialog User Abort User Reason: User specific reason
151Call barred|Map Dialog User Abort User Reason: User resource limitation
152Teleservice not provisioned|EC_NNR_noTranslationForAnAddressOfSuchNature
153Absent subscriber|EC_NNR_noTranslationForThisSpecificAddress
154Facility not supported|EC_NNR_subsystemCongestion
155System failure|EC_NNR_subsystemFailure
156Unexpected data value|EC_NNR_unequippedUser
157Data missing|EC_NNR_MTPfailure
158Memory capacity exceeded|EC_NNR_networkCongestion
159Mobile subscriber not reachable|EC_NNR_unqualified
160Reject|EC_NNR_errorInMessageTransportXUDT
161Local cancel|EC_NNR_errorInLocalProcessingXUDT
162Abort|EC_NNR_destinationCannotPerformReassemblyXUDT
163Exception|EC_NNR_SCCPfailure
164UNKNOWN|EC_NNR_hopCounterViolation
165EC_NNR_segmentationNotSupported
166EC_NNR_segmentationFailure
167USSD platform Unknown error
168DND Blocked
169MAP-P-Abort: Provider reasons
170MAP-P-Abort Provider reason: Malfunction
171MAP-P-Abort Provider reason: Dialog Released
172'waiting queue in destination subscriber table is full'
173MAP-P-Abort Provider reason: Abnormal Dialog
174MAP-P-Abort: Invalid PDU
175MAP-Open: Out of MAP dialogs
176Invalid Service code
177Subscriber MSISDN Blacklisted
178Subscriber IMSI Blacklisted
179Invalid Originating Address with Length greater than 20 chars
180MAP-Open Refuse reason: Node Not Reached
181'service barred'
182'operation barred'
183VLRBlackListed
184VLRWhiteListed
185MAP-Notice Problem: Message Cannot Be Delivered
186BILNG_SystemError
187MAP-Notice: Abnormal event detected by peer
188MAP-U-Abort: Error
189MAP-U-Abort User Reason: User Specific Reason
190MAP-U-Abort: User resource limitation
191MAP-U-Abort: Resource unavailable (short term)
192Unexpected session release from Servers/3rd party APP
193'unknServCent'
194'sc_Congestion'
195'invaSME_Add'
196'subsNotSC_Subsc'
197Application Specific Error from Client
198MAP-U-Abort: Application procedure cancellation (tandem dialogue released)
199MAP-U-Abort: Application procedure cancellation (remote operations failure)
200Unidentified subscriber|OPERATOR BLOCKED FOR ACCOUNT
201Absent subscriber IMSI detached|EC_unknown Subscriber
202Absent subscriber no page response|Unknown Base Station
203Subscriber busy for MT-SMS|Unknown MSC
205Illegal subscriber|EC_Unidentified Subscriber
206Illegal equipment|Absent Subscriber for SM
206Illegal equipment|Absent Subscriber for SM
207System failure|Unknown Equipment
208Unexpected data value|Roaming Not Allowed
209Data missing|Illegal Subscriber
210Memory capacity exceeded|Illegal SS Operation
211Equipment protocol error|SS Error Status
212Equipment not short message equipped|SS Not Available
213Reject|SS Subscription Violation
214Local cancel|SS Incompatible
215Abort|HLR:limited due to MS roaming'
216Exception|Internal IPC memory allocation Failure
217UNKNOWN|Internal IPC Router Failure
218'HLR:illegal subscriber'
219'HLR:subscriber absent'
220'HLR:the called MS poweroff'
221MSISDN BLOCKED
221Message List Full
222MESSAGE CONTENT IS BLACKLISTED/EC_Network System Failure
223Data Missing
224Unexpected Data
225MESSAGE CONTENT IS BLACKLISTED AT OPERATOR/ 'HLR:no response'
226'VMSC:no response'
227IN Subscriber not exist1
228'the destination subscriber PPS authentication overtime'
229'IN Invalid subscriber'
230Not Allowed
231ATI Not Allowed
232No Group Call Number Available
233Resource Limitation
234Unauthorized Requesting Network
235Unathorized LCS Client
236Position Method Failure
237Custom error 8
238Custom error 9
239Custom error 10
240Recipient Temporary Error
241Recipient Permanent Error
242Service Not configured/for a particular circle/subscriber. Or simply menu is incomplete or service i
243Terminating session due to invalid input
244Unspecific
245'HLR:the remote address not reachable' /'VMSC:Invalid Destination'
246Client Resource Not Available
247Unknown Alphabet
248EC_TIME_OUT
249EC_IMSI_BLACKLISTED
250Personal service barring|EC_DEST_ADDRESS_BLACKLISTED
251Personal service barring|EC_InvalidMscAddress
252Personal service barring|MESSAGE VALIDITY EXPIRED
253Personal service barring|the origination subscriber PPS authentication SCP connection broken'
254Personal service barring|any other error code other than 255
255Personal service barring|EC_UNKNOWN_ERROR
255Personal service barring|EC_UNKNOWN_ERROR
256Personal service barring|EC_SM_DF_memoryCapacityExceeded
257Personal service barring|EC_SM_DF_equipmentProtocolError
258EC_SM_DF_equipmentNotSM_Equipped
259EC_SM_DF_unknownServiceCentre
260EC_SM_DF_sc_Congestion
260'SMS not supported by MS'
261EC_SM_DF_invalidSME_Address
262EC_SM_DF_subscriberNotSC_Subscriber
263MO Handover: Destination SME Barred
264MO Handover: Duplicate Message Rejected
265MO Handover: Validity Period Format Unsupported
266MO Handover: Validity Period Unsupported
267MO Handover: Not Supported by equipment
268MO Handover: System Error
269MO Handover: Duplicated invoke id
270MO Handover: Service not supported
271MO Handover: Mistyped parameter
272MO Handover: No response from the peer
273MO Handover: Resource limitation
274MO Handover: Initiating release
275Error Gateway
276MO Handover: Unexpected error
277MO Handover: Unexpected response from the peer
278MO Handover: Unable to complete operation within timeout
279MO Handover: Invalid response received
280Error|MO Handover: TCAP error
281EC_UA_userSpecificReason
282EC_UA_userResourceLimitation
283EC_UA_resourceUnavailable
284EC_UA_applicationProcedureCancellation
285MO Handover: Unexpected Data Value
286MO Handover: Telematic Interworking not Supported
287MO Handover: FDA throttled
288MO Handover: SM decoding problem
300Invalid destination address|Provider Error Duplicate Invoke ID
301Invalid destination numbering plan|Provider Error Service Not Supported
302Invalid destination type of number|Provider Error Mistyped Paramter
303Invalid destination flag|Provider Error Resource Limitation
304Invalid number of destinations|Provider Error Initiating Release
305Provider Error Unexpected Response
306Provider Error Service Completion Failure
307EC_Provider No Response from Peer
308Provider Error Invalid Response
400EC_MAP_abort _error
401Stack/Sig Error Map User specific Reason
402Stack/Sig Error Map User Resource Limitation
403Stack/Sig Error Map Resource Unavailable
404Stack/Sig Error Map Application Procedure Cancellation
407EC_HLR/MSC Timeout
409Unknown Error
410EC_Cancelled
411EC_ValidityExpired
412EC_NotSubmittedToSmppChannel
413EC_DESTINATION_FLOODING
414EC_DESTINATION_TXT_FLOODING
415Stack/Sig Response Rejected By Peer
416Stack/Sig Abnormal Event Recieved From Peer
417Stack/Sig Cannot deliver Message
417Sig Error Map Invalid Response from peer
418Sig Error Map Dialogue Does not Exist
419Sig Error Map Max evoke reached
420Stack/Sig Invalid Origination Reference
420Stack/Sig Invalid Origination Reference
421Stack/Sig No Reson
421Stack/Sig No Reson
422Stack/Sig Remote Node Not Reachable
422Stack/Sig Remote Node Not Reachable
423Stack/Sig Map Potential Version Incompatibility
424Stack/Sig Secured Transport Not Possible
424Stack/Sig Secured Transport Not Possible
425Stack/Sig Usr Transport Protection Not Adequate
425Stack/Sig Usr Transport Protection Not Adequate
428Sig Error MAP Subsystem congested
428Sig Error MAP Subsystem congested
429Sig Error MAP Subsystem failure
429Sig Error MAP Subsystem failure
430Sig Error MAP Error in local processing CCIT92
430Sig Error MAP Error in local processing CCIT92
431Sig Error MAP Re assembly failure
431Sig Error MAP Re assembly failure
432Sig Error MAP SCCP failure
432Sig Error MAP SCCP failure
433Sig Error MAP HOP counter violation ITU
433Sig Error MAP HOP counter violation ITU
434Sig Error MAP segmentation not supported
434Sig Error MAP segmentation not supported
435Sig Error MAP Segmentation failure
435Sig Error MAP Segmentation failure
496EC_invalidPduFurmat
497EC_NotSubmittedToGMSC
500EC_PROVIDER_GENERAL_ERROR
501Insufficient Balance
502EC_NO_RESPONSE
503EC_SERVICE_COMPLETION_FAILURE
504EC_UNEXPECTED_RESPONSE_FROM_PEER
507EC_MISTYPED_PARAMETER
508EC_NOT_SUPPORTED_SERVICE
509EC_DUPLICATED_INVOKE_ID
510Temp_Fail
511SPAM_Fail
536EC_PA_providerMalfunction
537EC_PA_supportingDialogOrTransactionRealeased
538EC_PA_ressourceLimitation
539EC_PA_maintenanceActivity
540EC_PA_versionIncompatibility
541EC_PA_abnormalMapDialog
600Internal Error
601Timeout at SRI
602Absent subscriber
703Submit_SM_Timeout
715Expired at BMG
715Expired
792EC_NC_abnormalEventDetectedByPeer
793EC_NC_responseRejectedByPeer
794EC_NC_abnormalEventReceivedFromPeer
795EC_NC_messageCannotBeDeliveredToPeer
796EC_NC_providerOutOfInvoke
801EC_BLACKLISTED_MSISDN
1001No Response from far Network
1024EC_OR_appContextNotSupported
1025EC_OR_invalidDestinationReference
1026EC_OR_invalidOriginatingReference;
1027EC_OR_encapsulatedAC_NotSupported
1028EC_OR_transportProtectionNotAdequate
1029EC_OR_noReasonGiven
1030EC_OR_potentialVersionIncompatibility
1031EC_OR_remoteNodeNotReachable
1152EC_NNR_noTranslationForAnAddressOfSuchNatur
1153EC_NNR_noTranslationForThisSpecificAddress
1154EC_NNR_subsystemCongestion
1155EC_NNR_subsystemFailure
1156EC_NNR_unequippedUser
1157EC_NNR_MTPfailure
1158EC_NNR_networkCongestion
1159EC_NNR_unqualified
1160EC_NNR_errorInMessageTransportXUDT
1161EC_NNR_errorInLocalProcessingXUDT
1162EC_NNR_destinationCannotPerformReassemblyXUDT
1163EC_NNR_SCCPfailure
1164EC_NNR_hopCounterViolation
1165EC_NNR_segmentationNotSupported
1166EC_NNR_segmentationFailure
1281EC_UA_userSpecificReason
1282EC_UA_userResourceLimitation
1283EC_UA_resourceUnavailable
1284EC_UA_applicationProcedureCancellation
1536EC_PA_providerMalfunction
1537EC_PA_supportingDialogOrTransactionRealeased
1538EC_PA_ressourceLimitation
1539EC_PA_maintenanceActivity
1540EC_PA_versionIncompatibility
1541EC_PA_abnormalMapDialog
1793EC_NC_responseRejectedByPeer
1794EC_NC_abnormalEventReceivedFromPeer
1795EC_NC_messageCannotBeDeliveredToPeer
1796EC_NC_providerOutOfInvoke
2000Make_Call API Failure
2001Message too long
2002Command length is invalid
2003Command ID is invalid or not supported
2004Incorrect bind status for given command
2005Already bound
2006Invalid Priority Flag
2007Invalid registered delivery flag
2008System error
2010Invalid source address
2011Invalid destination address
2012Message ID is invalid
2013Bind failed
2014Invalid password
2015Invalid System ID
2017Cancelling message failed
2019Message recplacement failed
2020Message queue full
2021Invalid service type
2022Invalid services type
2048EC_TIME_OUT
2049EC_IMSI_BLACKLISTED
2050EC_DEST_ADDRESS_BLACKLISTED
2051EC_InvalidMscAddress
2052EC_BLACKLISTED_DESTINATIONADDRESS
2064Invalid destination flag
2066Invalid submit with replace request
2067Invalid esm class set
2068Invalid submit to ditribution list
2069Submitting message has failed
2072Invalid source address type of number ( TON )
2073Invalid source address numbering plan ( NPI )
2080Invalid destination address type of number ( TON )
2081Invalid destination address numbering plan ( NPI )
2083Invalid system type
2084Invalid replace_if_present flag
2085Invalid number of messages
2088Throttling error
2097Invalid scheduled delivery time
2098Invalid Validty Period value
2099Predefined message not found
2100ESME Receiver temporary error
2101ESME Receiver permanent error
2102ESME Receiver reject message error
2103Message query request failed
2168DND Block
2192Error in the optional part of the PDU body
2193TLV not allowed
2194Invalid parameter length
2195Expected TLV missing
2196Invalid TLV value
2254Transaction delivery failure
2255Unknown error
2256ESME not authorised to use specified servicetype
2257ESME prohibited from using specified operation
2258Specified servicetype is unavailable
2259Specified servicetype is denied
2260Invalid data coding scheme
2261Invalid source address subunit
2262Invalid destination address subunit
2300Incorrect destination address
2301Incorrect number of destination addresses
2302Syntax error in user data parameter
2303Incorrect bin/head/normal user data parameter combination
2304Incorrect dcs parameter usage
2305Incorrect validity period parameters usage
2306Incorrect originator address usage
2307Incorrect PID parameter usage
2308Incorrect first delivery parameter usage
2309Incorrect reply path usage
2310Incorrect status report request parameter usage
2311Incorrect cancel enabled parameter usage
2312Incorrect priority parameter usage
2313Incorrect tariff class parameter usage
2314Incorrect service description parameter usage
2315Incorrect transport type paramdeter usage
2316Incorrect message type parameter usage
2318Incorrect MMS parameter usage
2319Incorrect operation timer parameter usage
2320Incorrect dialogue ID parameter usage
2321Incorrect alpha originator address usage
2322Invalid data for alpha numeric originator
2323Online closed user group rejection
2324Licence exceeded
4000DLT_SCRUBBING_TIMEOUT
4001DLT_SCRUBBING_TIMEOUT
4096EC_InvalidPduFormat
4097EC_NotSubmittedToGMSC
4100EC_Cancelled
4101EC_ValidityExpired
4103EC_DESTINATION_FLOODING
4104EC_DESTINATION_TXT_FLOODING
4106BLOCKED_BY_DLT
4107DLT_SCRUBBING_TIMEOUT
4108SENDER_BLOCKED_BY_DLT
5000SCRUBBING_FAILED
5001SCRUBBING_FAILED
5101BLOCKED_BY_DLT
5102BLOCKED_BY_DLT
5103BLOCKED_BY_DLT
5104BLOCKED_BY_DLT
5105BLOCKED_BY_DLT
5106BLOCKED_BY_DLT
5107BLOCKED_BY_DLT
5108BLOCKED_BY_DLT
5201SENDER_BLOCKED_BY_DLT
5202SENDER_BLOCKED_BY_DLT
5203SENDER_MISMATCH_WITH_ENTITY
5204SENDER_BLOCKED_BY_DLT
5205Entity_ID_Not_Matched
5301TEMPLATE_ERROR
5302TEMPLATE_ERROR
5303TEMPLATE_ERROR
5304Content ID not in DB
5305TEMPLATE_ERROR
5306TEMPLATE_ERROR
5307TEMPLATE_ERROR
5308TEMPLATE_ERROR
5401TEMPLATE_ERROR
5402TEMPLATE_ERROR
5403TEMPLATE_ERROR
5404TEMPLATE_ERROR
5405TEMPLATE_ERROR
5406TEMPLATE_ERROR
5501CONSENT_FAILED
5502CONSENT_FAILED
5503CONSENT_FAILED
7001ENTITY_ID_ERROR
7002ENTITY_ID_ERROR
7003ENTITY_ID_ERROR
7004ENTITY_ID_ERROR
20ABearer Service Not Supported
20bTele Service Not Provisioned
20cError Equipment
20dCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21bAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21fSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Reply from Subscriber
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40aStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error MAP guard timer expired
41BSig Error MAP SPCAUSE mask
41cSig Error MAP No translation Based Address
41dSig Error MAP No translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig DlG Invalid Destination Reference
42aSig Error MAP unequipped user
42bSig Error MAP network failure
42cSig Error MAP network congestion
42dSig Error MAP unqualified
42ESig Error MAP HOP Counter violation ANS92
42FSig Error MAP Error in message transport CCIT92
20ABearer Service Not Supported
20BTele Service Not Provisioned
20CError Equipment
20DCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21BAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21FSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Subscriber Reply
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40AStack/Sig Error Map Provider Malfunction
40AStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error Map guard Timer Expired
41BSig Error Map SPCAUSE mask
41CSig Error MAP No Translation Basd Address
41DSig Error MAP No Translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig Dlg Invalid Destination Reference
42ASig Error MAP Un Equipped User
42ASig Error MAP Un Equipped User
42BSig Error MAP Network Failure
42BSig Error MAP Network Failure
42CSig Error MAP Network Conjestion
42CSig Error MAP Network Conjestion
42DSig Error MAP un Qualified
42DSig Error MAP un Qualified
42ESig Error MAP HOP Counter violaion ANS92
42ESig Error MAP HOP Counter violaion ANS92
42FSig Error MAP Error in message transport CCIT92
42FSig Error MAP Error in message transport CCIT92

Sending a Unicode SMS

To send a unicode SMS using the HTTP API, the following URL format is used:

https://www.mysmsapp.in/api/push.json?apikey=<apikey>&sender=<senderid>&mobileno=<mob>&text=<text>

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
delivery reports URLdlrurlThe URL to receive delivery reports. Spiffing custom is mandatory.delivery reports URL
Message IDcustomCustom message ID by customer, comma separatedAlphanumeric (max 40 char)
Schedule timetimeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM
unicodeunicodeTo specify that the message to be sent is in unicode format. Also can be used for automatic detection of unicode SMS.1 / 0 / auto
flashflashTo specify that the message is to be sent in the flash format1 or 0

Advanced Parameters(Optional)

The advanced parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
Callback function namecallbackCallback function for JSONP response format.String
Custom reference fieldscustom1 & custom2Custom reference fieldsAlphanumeric (max 40 char)
port numberportPort number to which SMS has to be sentValid integer port number above 2000

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send an SMS is in the below format :

ErrorCodeDescription
0NORMAL DELIVERED
1Source not found|EC_UNKNOWN_SUBSCRIBER
2Sink not found|EC_UNKNOWN_BASE_STATION
3Delivery zone not found|DND Fail
5Location not found|EC_UNIDENTIFIED_SUBSCRIBER
6Location blocked|Absent subscriber
7Reply path not found|UNKNOWN EQUIPMENT
8Message not submit|FSM TIMEOUT
9Unsupported number plan|EC_ILLEGAL_SUBSCRIBER
10Unsupported type of number|EC_BEARER_SERVICE_NOT_PROVISIONED
11Message not DELIVER or STATUS|EC_TELESERVICE_NOT_PROVISIONED
12Dialling zone not found|EC_ILLEGAL_EQUIPMENT
13Not home zone and IMSI not allowed|EC_CALL_BARRED
14Not home zone and IMSI fetch failed|Barred unauthorized message originator
15Screening block|CUG REJECT
18ESME error|message waiting for report expired'
19Originating location mismatch|SRIAck unsuccessful with any other error codes'
20Originating reservation failed|EC_SS_INCOMPATIBILITY
21Originating reservation denied subscription not found|EC_FACILITY_NOT_SUPPORTED
22Originating reservation denied subscription state illegal|Memory capacity exceeded
23Originating reservation denied call case blocked for subscription|Unknown Subscriber'
24Originating reservation denied call case blocked for subscription type|call forbidden'
25Originating reservation denied low balance|the network does not support SMS'
26'teleservice not supported'
27Absent subscriber
29'HLR:data error in route signal'
30Terminating reservation failed|HLR:data lacked'
31Terminating reservation denied subscription not found|EC_SUBSCRIBER_BUSY_FOR_MT_SMS
32Terminating reservation denied subscription state illegal|EC_SM_DELIVERY_FAILURE
33Terminating reservation denied call case blocked for subscription|EC_MESSAGE_WAITING_LIST_FULL
34Terminating reservation denied call case blocked for subscription type|EC_SYSTEM_FAILURE
35Terminating reservation denied low balance|EC_DATA_MISSING
36EC_UNEXPECTED_DATA_VALUE
37'Unmarked Subscriber'
38'failure because the subscriber is busy'
39'VMSC isolated'
40System is congested|VMSC:data lacked'
41Originating IMSI mismatch|VMSC:unexpected data'
42'MS error'
43Not Supported by equipment
44Illegal equipment
45Quarantine Add|Unspecific PID Error
46Quarantine Remove|Message Class Not Supported
47DCS error
48TPDU Not Supported
49Short message delivery failure with memory capacity exceeded
50Unexpected error from Store|UNKNOWN ERROR
51Direct delivery disabled from store|EC_RESOURCE_LIMITATION
53Message limit exceeded|Subscriber Busy For MT-SMS
54Retry scheme ended|Data Download Error
60Originator blocked|Absent subscriber
61Destination blocked|Absent subscriber
62Keyword blocked|Absent subscriber
63SC address blocked|Absent subscriber
64Blocked due to exceeded quota|Absent subscriber
65Loop detected|Absent subscriber
66Data coding scheme blocked|Absent subscriber over GPRS Page Fail
67Information element identifier blocked|Absent subscriber over GPRS Detached
68Country Code Validation Block|Absent subscriber over GPRS Deregistered
69Destination Flooding
70No ESME provider available|MS store is full'
71ESME account not connected|EC_UNKNOWN_ALPHABET
72No ESME sub account routing|EC_USSD_BUSY
74ESME local throttling - exceeded msg/s|INVALID HEADER IN MSG
80Home routing sender GT mismatch|PENDING DLR (Retry )
81Location mismatch between provided location and location known to HLR.|Service not supported
82IMSI mismatch between provided IMSI |Mistyped parameter
83Local throttling by sink|No response from the peer
84The IMSI could not be retrieved from the HSS|Resource limitation
85The IMEI of the UE is unknown|Initiating release
86The user location is unknown|Unrecognised error
87ESME router|Provider Error (In case of any failures observed in TCAP level this error will generate).
88Network fluctuation from far End Operator(Temporary Error)
89INVALID PACKET AT SMSC LEVEL
90USER-ABORT
91PROVIDER-ABORT
92MSC NUMBER MISSING
93Equipment protocol error
94Equipment not SM equipped
95Unknown service centre
96Service Centre congestion
97INVALID SCHEDULE DELIVERY TIME
98Subscriber not SC subscriber
99Invalid SME address
100Unidentified subscriber|no response from the called subscriber'
101Facility not supported|VMSC:the called MS poweroff'
102System failure|VMSC:limited due to MS roaming' / SENDER ID BLOCKED
103Unexpected data value|ROUTE NOT ACTIVE
104Data missing|OFF-NET NOT ACTIVE FOR ACCOUNT/ ON-NET ROUTES NOT DEFINED
105Equipment protocol error|MTP_FAILURE
106UNKNOWN service centre address|MS response is overtime'
107Service centre congestion|HLR:the subscriber is unregistered'
108Invalid short message entity address|ROUTE BLOCKED FOR THIS SERIES
109Subscriber not service centre subscriber|MSISDN SERIES NOT CONFIGURED
110Reject|NOT ABLE TO GET FINAL ROUTE
111Local cancel|Queue_Unvailable
112Abort|NOT A VALID TEMPLATE
113Exception|MANDATORY WORDS NOT FOUND
114UNKNOWN|DEFAULT ROUTE NOT FOUND IN CONFIGURED ROUTES
115ROUTE NOT CONFIGURED AT PLATFORM LEVEL
116Map Dialog P Abort Indication Provider Reason: Maintenance Activity
117Map Dialog P Abort Indication Provider Reason: Version Incompatibility
118Map Dialog P Abort Indication Provider Reason: Abnormal Dialogue
119MAP_DLGUA_UsrRsn_NTR_MapDlgUnavailable
120MAP_DLGUA_UsrRsn_NTR_MapNotConfigured
121MAP_DLGUA_UsrRsn_NTR_OtherErr
122MAP_DLGRJT_PrvRsn_NotSent
123INTERNATIONAL ROAMING
124EC_OR_appContextNotSupported
125EC_OR_invalidDestinationReference
126EC_OR_invalidOriginatingReference
127EC_OR_encapsulatedAC_NotSupported
128EC_OR_transportProtectionNotAdequate
129EC_OR_noReasonGiven
130EC_OR_potentialVersionIncompatibility
131EC_OR_remoteNodeNotReachable
132Map Dialog Rejected Refuse Reason: Application Context not supported
133Map Dialog Rejected Refuse Reason: Potential Version Incompatibility
134Map Dialog Rejected Refuse Reason: Remote Node not reachable
135Map Dialog Rejected Provider Reason: Provider malfunction
136Map Dialog Rejected Provider Reason: Transaction Released
137Map Dialog Rejected Provider Reason: Resource Limitation
138Map Dialog Rejected Provider Reason: Maintenance Activity
139Map Dialog Rejected Provider Reason: Version Incompatibility
140Map Dialog Rejected Provider Reason: Abnormal Dialogue
141Map Dialog User Abort Diagnostic Info: Short Term resource Limitation
142Map Dialog User Abort Diagnostic Info: Long term resource limitation
143Map Dialog User Abort Diagnostic Info: Handover cancellation
144Map Dialog User Abort Diagnostic Info: Radio Channel Release
145Map Dialog User Abort Diagnostic Info: Call Release
146Map Dialog User Abort Diagnostic Info: Network path Release
147Map Dialog User Abort Diagnostic Info: Associated Procedure release
148Map Dialog User Abort Diagnostic Info: Tandem Dialog Release
149Map Dialog User Abort Diagnostic Info: Remote Operation Failure
150UNKNOWN subscriber|Map Dialog User Abort User Reason: User specific reason
151Call barred|Map Dialog User Abort User Reason: User resource limitation
152Teleservice not provisioned|EC_NNR_noTranslationForAnAddressOfSuchNature
153Absent subscriber|EC_NNR_noTranslationForThisSpecificAddress
154Facility not supported|EC_NNR_subsystemCongestion
155System failure|EC_NNR_subsystemFailure
156Unexpected data value|EC_NNR_unequippedUser
157Data missing|EC_NNR_MTPfailure
158Memory capacity exceeded|EC_NNR_networkCongestion
159Mobile subscriber not reachable|EC_NNR_unqualified
160Reject|EC_NNR_errorInMessageTransportXUDT
161Local cancel|EC_NNR_errorInLocalProcessingXUDT
162Abort|EC_NNR_destinationCannotPerformReassemblyXUDT
163Exception|EC_NNR_SCCPfailure
164UNKNOWN|EC_NNR_hopCounterViolation
165EC_NNR_segmentationNotSupported
166EC_NNR_segmentationFailure
167USSD platform Unknown error
168DND Blocked
169MAP-P-Abort: Provider reasons
170MAP-P-Abort Provider reason: Malfunction
171MAP-P-Abort Provider reason: Dialog Released
172'waiting queue in destination subscriber table is full'
173MAP-P-Abort Provider reason: Abnormal Dialog
174MAP-P-Abort: Invalid PDU
175MAP-Open: Out of MAP dialogs
176Invalid Service code
177Subscriber MSISDN Blacklisted
178Subscriber IMSI Blacklisted
179Invalid Originating Address with Length greater than 20 chars
180MAP-Open Refuse reason: Node Not Reached
181'service barred'
182'operation barred'
183VLRBlackListed
184VLRWhiteListed
185MAP-Notice Problem: Message Cannot Be Delivered
186BILNG_SystemError
187MAP-Notice: Abnormal event detected by peer
188MAP-U-Abort: Error
189MAP-U-Abort User Reason: User Specific Reason
190MAP-U-Abort: User resource limitation
191MAP-U-Abort: Resource unavailable (short term)
192Unexpected session release from Servers/3rd party APP
193'unknServCent'
194'sc_Congestion'
195'invaSME_Add'
196'subsNotSC_Subsc'
197Application Specific Error from Client
198MAP-U-Abort: Application procedure cancellation (tandem dialogue released)
199MAP-U-Abort: Application procedure cancellation (remote operations failure)
200Unidentified subscriber|OPERATOR BLOCKED FOR ACCOUNT
201Absent subscriber IMSI detached|EC_unknown Subscriber
202Absent subscriber no page response|Unknown Base Station
203Subscriber busy for MT-SMS|Unknown MSC
205Illegal subscriber|EC_Unidentified Subscriber
206Illegal equipment|Absent Subscriber for SM
206Illegal equipment|Absent Subscriber for SM
207System failure|Unknown Equipment
208Unexpected data value|Roaming Not Allowed
209Data missing|Illegal Subscriber
210Memory capacity exceeded|Illegal SS Operation
211Equipment protocol error|SS Error Status
212Equipment not short message equipped|SS Not Available
213Reject|SS Subscription Violation
214Local cancel|SS Incompatible
215Abort|HLR:limited due to MS roaming'
216Exception|Internal IPC memory allocation Failure
217UNKNOWN|Internal IPC Router Failure
218'HLR:illegal subscriber'
219'HLR:subscriber absent'
220'HLR:the called MS poweroff'
221MSISDN BLOCKED
221Message List Full
222MESSAGE CONTENT IS BLACKLISTED/EC_Network System Failure
223Data Missing
224Unexpected Data
225MESSAGE CONTENT IS BLACKLISTED AT OPERATOR/ 'HLR:no response'
226'VMSC:no response'
227IN Subscriber not exist1
228'the destination subscriber PPS authentication overtime'
229'IN Invalid subscriber'
230Not Allowed
231ATI Not Allowed
232No Group Call Number Available
233Resource Limitation
234Unauthorized Requesting Network
235Unathorized LCS Client
236Position Method Failure
237Custom error 8
238Custom error 9
239Custom error 10
240Recipient Temporary Error
241Recipient Permanent Error
242Service Not configured/for a particular circle/subscriber. Or simply menu is incomplete or service i
243Terminating session due to invalid input
244Unspecific
245'HLR:the remote address not reachable' /'VMSC:Invalid Destination'
246Client Resource Not Available
247Unknown Alphabet
248EC_TIME_OUT
249EC_IMSI_BLACKLISTED
250Personal service barring|EC_DEST_ADDRESS_BLACKLISTED
251Personal service barring|EC_InvalidMscAddress
252Personal service barring|MESSAGE VALIDITY EXPIRED
253Personal service barring|the origination subscriber PPS authentication SCP connection broken'
254Personal service barring|any other error code other than 255
255Personal service barring|EC_UNKNOWN_ERROR
255Personal service barring|EC_UNKNOWN_ERROR
256Personal service barring|EC_SM_DF_memoryCapacityExceeded
257Personal service barring|EC_SM_DF_equipmentProtocolError
258EC_SM_DF_equipmentNotSM_Equipped
259EC_SM_DF_unknownServiceCentre
260EC_SM_DF_sc_Congestion
260'SMS not supported by MS'
261EC_SM_DF_invalidSME_Address
262EC_SM_DF_subscriberNotSC_Subscriber
263MO Handover: Destination SME Barred
264MO Handover: Duplicate Message Rejected
265MO Handover: Validity Period Format Unsupported
266MO Handover: Validity Period Unsupported
267MO Handover: Not Supported by equipment
268MO Handover: System Error
269MO Handover: Duplicated invoke id
270MO Handover: Service not supported
271MO Handover: Mistyped parameter
272MO Handover: No response from the peer
273MO Handover: Resource limitation
274MO Handover: Initiating release
275Error Gateway
276MO Handover: Unexpected error
277MO Handover: Unexpected response from the peer
278MO Handover: Unable to complete operation within timeout
279MO Handover: Invalid response received
280Error|MO Handover: TCAP error
281EC_UA_userSpecificReason
282EC_UA_userResourceLimitation
283EC_UA_resourceUnavailable
284EC_UA_applicationProcedureCancellation
285MO Handover: Unexpected Data Value
286MO Handover: Telematic Interworking not Supported
287MO Handover: FDA throttled
288MO Handover: SM decoding problem
300Invalid destination address|Provider Error Duplicate Invoke ID
301Invalid destination numbering plan|Provider Error Service Not Supported
302Invalid destination type of number|Provider Error Mistyped Paramter
303Invalid destination flag|Provider Error Resource Limitation
304Invalid number of destinations|Provider Error Initiating Release
305Provider Error Unexpected Response
306Provider Error Service Completion Failure
307EC_Provider No Response from Peer
308Provider Error Invalid Response
400EC_MAP_abort _error
401Stack/Sig Error Map User specific Reason
402Stack/Sig Error Map User Resource Limitation
403Stack/Sig Error Map Resource Unavailable
404Stack/Sig Error Map Application Procedure Cancellation
407EC_HLR/MSC Timeout
409Unknown Error
410EC_Cancelled
411EC_ValidityExpired
412EC_NotSubmittedToSmppChannel
413EC_DESTINATION_FLOODING
414EC_DESTINATION_TXT_FLOODING
415Stack/Sig Response Rejected By Peer
416Stack/Sig Abnormal Event Recieved From Peer
417Stack/Sig Cannot deliver Message
417Sig Error Map Invalid Response from peer
418Sig Error Map Dialogue Does not Exist
419Sig Error Map Max evoke reached
420Stack/Sig Invalid Origination Reference
420Stack/Sig Invalid Origination Reference
421Stack/Sig No Reson
421Stack/Sig No Reson
422Stack/Sig Remote Node Not Reachable
422Stack/Sig Remote Node Not Reachable
423Stack/Sig Map Potential Version Incompatibility
424Stack/Sig Secured Transport Not Possible
424Stack/Sig Secured Transport Not Possible
425Stack/Sig Usr Transport Protection Not Adequate
425Stack/Sig Usr Transport Protection Not Adequate
428Sig Error MAP Subsystem congested
428Sig Error MAP Subsystem congested
429Sig Error MAP Subsystem failure
429Sig Error MAP Subsystem failure
430Sig Error MAP Error in local processing CCIT92
430Sig Error MAP Error in local processing CCIT92
431Sig Error MAP Re assembly failure
431Sig Error MAP Re assembly failure
432Sig Error MAP SCCP failure
432Sig Error MAP SCCP failure
433Sig Error MAP HOP counter violation ITU
433Sig Error MAP HOP counter violation ITU
434Sig Error MAP segmentation not supported
434Sig Error MAP segmentation not supported
435Sig Error MAP Segmentation failure
435Sig Error MAP Segmentation failure
496EC_invalidPduFurmat
497EC_NotSubmittedToGMSC
500EC_PROVIDER_GENERAL_ERROR
501Insufficient Balance
502EC_NO_RESPONSE
503EC_SERVICE_COMPLETION_FAILURE
504EC_UNEXPECTED_RESPONSE_FROM_PEER
507EC_MISTYPED_PARAMETER
508EC_NOT_SUPPORTED_SERVICE
509EC_DUPLICATED_INVOKE_ID
510Temp_Fail
511SPAM_Fail
536EC_PA_providerMalfunction
537EC_PA_supportingDialogOrTransactionRealeased
538EC_PA_ressourceLimitation
539EC_PA_maintenanceActivity
540EC_PA_versionIncompatibility
541EC_PA_abnormalMapDialog
600Internal Error
601Timeout at SRI
602Absent subscriber
703Submit_SM_Timeout
715Expired at BMG
715Expired
792EC_NC_abnormalEventDetectedByPeer
793EC_NC_responseRejectedByPeer
794EC_NC_abnormalEventReceivedFromPeer
795EC_NC_messageCannotBeDeliveredToPeer
796EC_NC_providerOutOfInvoke
801EC_BLACKLISTED_MSISDN
1001No Response from far Network
1024EC_OR_appContextNotSupported
1025EC_OR_invalidDestinationReference
1026EC_OR_invalidOriginatingReference;
1027EC_OR_encapsulatedAC_NotSupported
1028EC_OR_transportProtectionNotAdequate
1029EC_OR_noReasonGiven
1030EC_OR_potentialVersionIncompatibility
1031EC_OR_remoteNodeNotReachable
1152EC_NNR_noTranslationForAnAddressOfSuchNatur
1153EC_NNR_noTranslationForThisSpecificAddress
1154EC_NNR_subsystemCongestion
1155EC_NNR_subsystemFailure
1156EC_NNR_unequippedUser
1157EC_NNR_MTPfailure
1158EC_NNR_networkCongestion
1159EC_NNR_unqualified
1160EC_NNR_errorInMessageTransportXUDT
1161EC_NNR_errorInLocalProcessingXUDT
1162EC_NNR_destinationCannotPerformReassemblyXUDT
1163EC_NNR_SCCPfailure
1164EC_NNR_hopCounterViolation
1165EC_NNR_segmentationNotSupported
1166EC_NNR_segmentationFailure
1281EC_UA_userSpecificReason
1282EC_UA_userResourceLimitation
1283EC_UA_resourceUnavailable
1284EC_UA_applicationProcedureCancellation
1536EC_PA_providerMalfunction
1537EC_PA_supportingDialogOrTransactionRealeased
1538EC_PA_ressourceLimitation
1539EC_PA_maintenanceActivity
1540EC_PA_versionIncompatibility
1541EC_PA_abnormalMapDialog
1793EC_NC_responseRejectedByPeer
1794EC_NC_abnormalEventReceivedFromPeer
1795EC_NC_messageCannotBeDeliveredToPeer
1796EC_NC_providerOutOfInvoke
2000Make_Call API Failure
2001Message too long
2002Command length is invalid
2003Command ID is invalid or not supported
2004Incorrect bind status for given command
2005Already bound
2006Invalid Priority Flag
2007Invalid registered delivery flag
2008System error
2010Invalid source address
2011Invalid destination address
2012Message ID is invalid
2013Bind failed
2014Invalid password
2015Invalid System ID
2017Cancelling message failed
2019Message recplacement failed
2020Message queue full
2021Invalid service type
2022Invalid services type
2048EC_TIME_OUT
2049EC_IMSI_BLACKLISTED
2050EC_DEST_ADDRESS_BLACKLISTED
2051EC_InvalidMscAddress
2052EC_BLACKLISTED_DESTINATIONADDRESS
2064Invalid destination flag
2066Invalid submit with replace request
2067Invalid esm class set
2068Invalid submit to ditribution list
2069Submitting message has failed
2072Invalid source address type of number ( TON )
2073Invalid source address numbering plan ( NPI )
2080Invalid destination address type of number ( TON )
2081Invalid destination address numbering plan ( NPI )
2083Invalid system type
2084Invalid replace_if_present flag
2085Invalid number of messages
2088Throttling error
2097Invalid scheduled delivery time
2098Invalid Validty Period value
2099Predefined message not found
2100ESME Receiver temporary error
2101ESME Receiver permanent error
2102ESME Receiver reject message error
2103Message query request failed
2168DND Block
2192Error in the optional part of the PDU body
2193TLV not allowed
2194Invalid parameter length
2195Expected TLV missing
2196Invalid TLV value
2254Transaction delivery failure
2255Unknown error
2256ESME not authorised to use specified servicetype
2257ESME prohibited from using specified operation
2258Specified servicetype is unavailable
2259Specified servicetype is denied
2260Invalid data coding scheme
2261Invalid source address subunit
2262Invalid destination address subunit
2300Incorrect destination address
2301Incorrect number of destination addresses
2302Syntax error in user data parameter
2303Incorrect bin/head/normal user data parameter combination
2304Incorrect dcs parameter usage
2305Incorrect validity period parameters usage
2306Incorrect originator address usage
2307Incorrect PID parameter usage
2308Incorrect first delivery parameter usage
2309Incorrect reply path usage
2310Incorrect status report request parameter usage
2311Incorrect cancel enabled parameter usage
2312Incorrect priority parameter usage
2313Incorrect tariff class parameter usage
2314Incorrect service description parameter usage
2315Incorrect transport type paramdeter usage
2316Incorrect message type parameter usage
2318Incorrect MMS parameter usage
2319Incorrect operation timer parameter usage
2320Incorrect dialogue ID parameter usage
2321Incorrect alpha originator address usage
2322Invalid data for alpha numeric originator
2323Online closed user group rejection
2324Licence exceeded
4000DLT_SCRUBBING_TIMEOUT
4001DLT_SCRUBBING_TIMEOUT
4096EC_InvalidPduFormat
4097EC_NotSubmittedToGMSC
4100EC_Cancelled
4101EC_ValidityExpired
4103EC_DESTINATION_FLOODING
4104EC_DESTINATION_TXT_FLOODING
4106BLOCKED_BY_DLT
4107DLT_SCRUBBING_TIMEOUT
4108SENDER_BLOCKED_BY_DLT
5000SCRUBBING_FAILED
5001SCRUBBING_FAILED
5101BLOCKED_BY_DLT
5102BLOCKED_BY_DLT
5103BLOCKED_BY_DLT
5104BLOCKED_BY_DLT
5105BLOCKED_BY_DLT
5106BLOCKED_BY_DLT
5107BLOCKED_BY_DLT
5108BLOCKED_BY_DLT
5201SENDER_BLOCKED_BY_DLT
5202SENDER_BLOCKED_BY_DLT
5203SENDER_MISMATCH_WITH_ENTITY
5204SENDER_BLOCKED_BY_DLT
5205Entity_ID_Not_Matched
5301TEMPLATE_ERROR
5302TEMPLATE_ERROR
5303TEMPLATE_ERROR
5304Content ID not in DB
5305TEMPLATE_ERROR
5306TEMPLATE_ERROR
5307TEMPLATE_ERROR
5308TEMPLATE_ERROR
5401TEMPLATE_ERROR
5402TEMPLATE_ERROR
5403TEMPLATE_ERROR
5404TEMPLATE_ERROR
5405TEMPLATE_ERROR
5406TEMPLATE_ERROR
5501CONSENT_FAILED
5502CONSENT_FAILED
5503CONSENT_FAILED
7001ENTITY_ID_ERROR
7002ENTITY_ID_ERROR
7003ENTITY_ID_ERROR
7004ENTITY_ID_ERROR
20ABearer Service Not Supported
20bTele Service Not Provisioned
20cError Equipment
20dCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21bAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21fSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Reply from Subscriber
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40aStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error MAP guard timer expired
41BSig Error MAP SPCAUSE mask
41cSig Error MAP No translation Based Address
41dSig Error MAP No translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig DlG Invalid Destination Reference
42aSig Error MAP unequipped user
42bSig Error MAP network failure
42cSig Error MAP network congestion
42dSig Error MAP unqualified
42ESig Error MAP HOP Counter violation ANS92
42FSig Error MAP Error in message transport CCIT92
20ABearer Service Not Supported
20BTele Service Not Provisioned
20CError Equipment
20DCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21BAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21FSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Subscriber Reply
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40AStack/Sig Error Map Provider Malfunction
40AStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error Map guard Timer Expired
41BSig Error Map SPCAUSE mask
41CSig Error MAP No Translation Basd Address
41DSig Error MAP No Translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig Dlg Invalid Destination Reference
42ASig Error MAP Un Equipped User
42ASig Error MAP Un Equipped User
42BSig Error MAP Network Failure
42BSig Error MAP Network Failure
42CSig Error MAP Network Conjestion
42CSig Error MAP Network Conjestion
42DSig Error MAP un Qualified
42DSig Error MAP un Qualified
42ESig Error MAP HOP Counter violaion ANS92
42ESig Error MAP HOP Counter violaion ANS92
42FSig Error MAP Error in message transport CCIT92
42FSig Error MAP Error in message transport CCIT92

Scheduling SMS

To schedule an SMS using the HTTP API, the following URL format is used:

https://www.mysmsapp.in/api/push.json?apikey=<apikey>&sender=<senderid>&mobileno=<mob>&text=<text>&schedule=<schedule>

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)
Schedule time timeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM

Advanced Parameters(Optional)

The advanced parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
Callback function namecallbackCallback function for JSONP response format.String
Custom reference fieldscustom1 & custom2Custom reference fieldsAlphanumeric (max 40 char)
port numberportPort number to which SMS has to be sentValid integer port number above 2000

Example Response

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send an SMS is in the below format :

ErrorCodeDescription
0NORMAL DELIVERED
1Source not found|EC_UNKNOWN_SUBSCRIBER
2Sink not found|EC_UNKNOWN_BASE_STATION
3Delivery zone not found|DND Fail
5Location not found|EC_UNIDENTIFIED_SUBSCRIBER
6Location blocked|Absent subscriber
7Reply path not found|UNKNOWN EQUIPMENT
8Message not submit|FSM TIMEOUT
9Unsupported number plan|EC_ILLEGAL_SUBSCRIBER
10Unsupported type of number|EC_BEARER_SERVICE_NOT_PROVISIONED
11Message not DELIVER or STATUS|EC_TELESERVICE_NOT_PROVISIONED
12Dialling zone not found|EC_ILLEGAL_EQUIPMENT
13Not home zone and IMSI not allowed|EC_CALL_BARRED
14Not home zone and IMSI fetch failed|Barred unauthorized message originator
15Screening block|CUG REJECT
18ESME error|message waiting for report expired'
19Originating location mismatch|SRIAck unsuccessful with any other error codes'
20Originating reservation failed|EC_SS_INCOMPATIBILITY
21Originating reservation denied subscription not found|EC_FACILITY_NOT_SUPPORTED
22Originating reservation denied subscription state illegal|Memory capacity exceeded
23Originating reservation denied call case blocked for subscription|Unknown Subscriber'
24Originating reservation denied call case blocked for subscription type|call forbidden'
25Originating reservation denied low balance|the network does not support SMS'
26'teleservice not supported'
27Absent subscriber
29'HLR:data error in route signal'
30Terminating reservation failed|HLR:data lacked'
31Terminating reservation denied subscription not found|EC_SUBSCRIBER_BUSY_FOR_MT_SMS
32Terminating reservation denied subscription state illegal|EC_SM_DELIVERY_FAILURE
33Terminating reservation denied call case blocked for subscription|EC_MESSAGE_WAITING_LIST_FULL
34Terminating reservation denied call case blocked for subscription type|EC_SYSTEM_FAILURE
35Terminating reservation denied low balance|EC_DATA_MISSING
36EC_UNEXPECTED_DATA_VALUE
37'Unmarked Subscriber'
38'failure because the subscriber is busy'
39'VMSC isolated'
40System is congested|VMSC:data lacked'
41Originating IMSI mismatch|VMSC:unexpected data'
42'MS error'
43Not Supported by equipment
44Illegal equipment
45Quarantine Add|Unspecific PID Error
46Quarantine Remove|Message Class Not Supported
47DCS error
48TPDU Not Supported
49Short message delivery failure with memory capacity exceeded
50Unexpected error from Store|UNKNOWN ERROR
51Direct delivery disabled from store|EC_RESOURCE_LIMITATION
53Message limit exceeded|Subscriber Busy For MT-SMS
54Retry scheme ended|Data Download Error
60Originator blocked|Absent subscriber
61Destination blocked|Absent subscriber
62Keyword blocked|Absent subscriber
63SC address blocked|Absent subscriber
64Blocked due to exceeded quota|Absent subscriber
65Loop detected|Absent subscriber
66Data coding scheme blocked|Absent subscriber over GPRS Page Fail
67Information element identifier blocked|Absent subscriber over GPRS Detached
68Country Code Validation Block|Absent subscriber over GPRS Deregistered
69Destination Flooding
70No ESME provider available|MS store is full'
71ESME account not connected|EC_UNKNOWN_ALPHABET
72No ESME sub account routing|EC_USSD_BUSY
74ESME local throttling - exceeded msg/s|INVALID HEADER IN MSG
80Home routing sender GT mismatch|PENDING DLR (Retry )
81Location mismatch between provided location and location known to HLR.|Service not supported
82IMSI mismatch between provided IMSI |Mistyped parameter
83Local throttling by sink|No response from the peer
84The IMSI could not be retrieved from the HSS|Resource limitation
85The IMEI of the UE is unknown|Initiating release
86The user location is unknown|Unrecognised error
87ESME router|Provider Error (In case of any failures observed in TCAP level this error will generate).
88Network fluctuation from far End Operator(Temporary Error)
89INVALID PACKET AT SMSC LEVEL
90USER-ABORT
91PROVIDER-ABORT
92MSC NUMBER MISSING
93Equipment protocol error
94Equipment not SM equipped
95Unknown service centre
96Service Centre congestion
97INVALID SCHEDULE DELIVERY TIME
98Subscriber not SC subscriber
99Invalid SME address
100Unidentified subscriber|no response from the called subscriber'
101Facility not supported|VMSC:the called MS poweroff'
102System failure|VMSC:limited due to MS roaming' / SENDER ID BLOCKED
103Unexpected data value|ROUTE NOT ACTIVE
104Data missing|OFF-NET NOT ACTIVE FOR ACCOUNT/ ON-NET ROUTES NOT DEFINED
105Equipment protocol error|MTP_FAILURE
106UNKNOWN service centre address|MS response is overtime'
107Service centre congestion|HLR:the subscriber is unregistered'
108Invalid short message entity address|ROUTE BLOCKED FOR THIS SERIES
109Subscriber not service centre subscriber|MSISDN SERIES NOT CONFIGURED
110Reject|NOT ABLE TO GET FINAL ROUTE
111Local cancel|Queue_Unvailable
112Abort|NOT A VALID TEMPLATE
113Exception|MANDATORY WORDS NOT FOUND
114UNKNOWN|DEFAULT ROUTE NOT FOUND IN CONFIGURED ROUTES
115ROUTE NOT CONFIGURED AT PLATFORM LEVEL
116Map Dialog P Abort Indication Provider Reason: Maintenance Activity
117Map Dialog P Abort Indication Provider Reason: Version Incompatibility
118Map Dialog P Abort Indication Provider Reason: Abnormal Dialogue
119MAP_DLGUA_UsrRsn_NTR_MapDlgUnavailable
120MAP_DLGUA_UsrRsn_NTR_MapNotConfigured
121MAP_DLGUA_UsrRsn_NTR_OtherErr
122MAP_DLGRJT_PrvRsn_NotSent
123INTERNATIONAL ROAMING
124EC_OR_appContextNotSupported
125EC_OR_invalidDestinationReference
126EC_OR_invalidOriginatingReference
127EC_OR_encapsulatedAC_NotSupported
128EC_OR_transportProtectionNotAdequate
129EC_OR_noReasonGiven
130EC_OR_potentialVersionIncompatibility
131EC_OR_remoteNodeNotReachable
132Map Dialog Rejected Refuse Reason: Application Context not supported
133Map Dialog Rejected Refuse Reason: Potential Version Incompatibility
134Map Dialog Rejected Refuse Reason: Remote Node not reachable
135Map Dialog Rejected Provider Reason: Provider malfunction
136Map Dialog Rejected Provider Reason: Transaction Released
137Map Dialog Rejected Provider Reason: Resource Limitation
138Map Dialog Rejected Provider Reason: Maintenance Activity
139Map Dialog Rejected Provider Reason: Version Incompatibility
140Map Dialog Rejected Provider Reason: Abnormal Dialogue
141Map Dialog User Abort Diagnostic Info: Short Term resource Limitation
142Map Dialog User Abort Diagnostic Info: Long term resource limitation
143Map Dialog User Abort Diagnostic Info: Handover cancellation
144Map Dialog User Abort Diagnostic Info: Radio Channel Release
145Map Dialog User Abort Diagnostic Info: Call Release
146Map Dialog User Abort Diagnostic Info: Network path Release
147Map Dialog User Abort Diagnostic Info: Associated Procedure release
148Map Dialog User Abort Diagnostic Info: Tandem Dialog Release
149Map Dialog User Abort Diagnostic Info: Remote Operation Failure
150UNKNOWN subscriber|Map Dialog User Abort User Reason: User specific reason
151Call barred|Map Dialog User Abort User Reason: User resource limitation
152Teleservice not provisioned|EC_NNR_noTranslationForAnAddressOfSuchNature
153Absent subscriber|EC_NNR_noTranslationForThisSpecificAddress
154Facility not supported|EC_NNR_subsystemCongestion
155System failure|EC_NNR_subsystemFailure
156Unexpected data value|EC_NNR_unequippedUser
157Data missing|EC_NNR_MTPfailure
158Memory capacity exceeded|EC_NNR_networkCongestion
159Mobile subscriber not reachable|EC_NNR_unqualified
160Reject|EC_NNR_errorInMessageTransportXUDT
161Local cancel|EC_NNR_errorInLocalProcessingXUDT
162Abort|EC_NNR_destinationCannotPerformReassemblyXUDT
163Exception|EC_NNR_SCCPfailure
164UNKNOWN|EC_NNR_hopCounterViolation
165EC_NNR_segmentationNotSupported
166EC_NNR_segmentationFailure
167USSD platform Unknown error
168DND Blocked
169MAP-P-Abort: Provider reasons
170MAP-P-Abort Provider reason: Malfunction
171MAP-P-Abort Provider reason: Dialog Released
172'waiting queue in destination subscriber table is full'
173MAP-P-Abort Provider reason: Abnormal Dialog
174MAP-P-Abort: Invalid PDU
175MAP-Open: Out of MAP dialogs
176Invalid Service code
177Subscriber MSISDN Blacklisted
178Subscriber IMSI Blacklisted
179Invalid Originating Address with Length greater than 20 chars
180MAP-Open Refuse reason: Node Not Reached
181'service barred'
182'operation barred'
183VLRBlackListed
184VLRWhiteListed
185MAP-Notice Problem: Message Cannot Be Delivered
186BILNG_SystemError
187MAP-Notice: Abnormal event detected by peer
188MAP-U-Abort: Error
189MAP-U-Abort User Reason: User Specific Reason
190MAP-U-Abort: User resource limitation
191MAP-U-Abort: Resource unavailable (short term)
192Unexpected session release from Servers/3rd party APP
193'unknServCent'
194'sc_Congestion'
195'invaSME_Add'
196'subsNotSC_Subsc'
197Application Specific Error from Client
198MAP-U-Abort: Application procedure cancellation (tandem dialogue released)
199MAP-U-Abort: Application procedure cancellation (remote operations failure)
200Unidentified subscriber|OPERATOR BLOCKED FOR ACCOUNT
201Absent subscriber IMSI detached|EC_unknown Subscriber
202Absent subscriber no page response|Unknown Base Station
203Subscriber busy for MT-SMS|Unknown MSC
205Illegal subscriber|EC_Unidentified Subscriber
206Illegal equipment|Absent Subscriber for SM
206Illegal equipment|Absent Subscriber for SM
207System failure|Unknown Equipment
208Unexpected data value|Roaming Not Allowed
209Data missing|Illegal Subscriber
210Memory capacity exceeded|Illegal SS Operation
211Equipment protocol error|SS Error Status
212Equipment not short message equipped|SS Not Available
213Reject|SS Subscription Violation
214Local cancel|SS Incompatible
215Abort|HLR:limited due to MS roaming'
216Exception|Internal IPC memory allocation Failure
217UNKNOWN|Internal IPC Router Failure
218'HLR:illegal subscriber'
219'HLR:subscriber absent'
220'HLR:the called MS poweroff'
221MSISDN BLOCKED
221Message List Full
222MESSAGE CONTENT IS BLACKLISTED/EC_Network System Failure
223Data Missing
224Unexpected Data
225MESSAGE CONTENT IS BLACKLISTED AT OPERATOR/ 'HLR:no response'
226'VMSC:no response'
227IN Subscriber not exist1
228'the destination subscriber PPS authentication overtime'
229'IN Invalid subscriber'
230Not Allowed
231ATI Not Allowed
232No Group Call Number Available
233Resource Limitation
234Unauthorized Requesting Network
235Unathorized LCS Client
236Position Method Failure
237Custom error 8
238Custom error 9
239Custom error 10
240Recipient Temporary Error
241Recipient Permanent Error
242Service Not configured/for a particular circle/subscriber. Or simply menu is incomplete or service i
243Terminating session due to invalid input
244Unspecific
245'HLR:the remote address not reachable' /'VMSC:Invalid Destination'
246Client Resource Not Available
247Unknown Alphabet
248EC_TIME_OUT
249EC_IMSI_BLACKLISTED
250Personal service barring|EC_DEST_ADDRESS_BLACKLISTED
251Personal service barring|EC_InvalidMscAddress
252Personal service barring|MESSAGE VALIDITY EXPIRED
253Personal service barring|the origination subscriber PPS authentication SCP connection broken'
254Personal service barring|any other error code other than 255
255Personal service barring|EC_UNKNOWN_ERROR
255Personal service barring|EC_UNKNOWN_ERROR
256Personal service barring|EC_SM_DF_memoryCapacityExceeded
257Personal service barring|EC_SM_DF_equipmentProtocolError
258EC_SM_DF_equipmentNotSM_Equipped
259EC_SM_DF_unknownServiceCentre
260EC_SM_DF_sc_Congestion
260'SMS not supported by MS'
261EC_SM_DF_invalidSME_Address
262EC_SM_DF_subscriberNotSC_Subscriber
263MO Handover: Destination SME Barred
264MO Handover: Duplicate Message Rejected
265MO Handover: Validity Period Format Unsupported
266MO Handover: Validity Period Unsupported
267MO Handover: Not Supported by equipment
268MO Handover: System Error
269MO Handover: Duplicated invoke id
270MO Handover: Service not supported
271MO Handover: Mistyped parameter
272MO Handover: No response from the peer
273MO Handover: Resource limitation
274MO Handover: Initiating release
275Error Gateway
276MO Handover: Unexpected error
277MO Handover: Unexpected response from the peer
278MO Handover: Unable to complete operation within timeout
279MO Handover: Invalid response received
280Error|MO Handover: TCAP error
281EC_UA_userSpecificReason
282EC_UA_userResourceLimitation
283EC_UA_resourceUnavailable
284EC_UA_applicationProcedureCancellation
285MO Handover: Unexpected Data Value
286MO Handover: Telematic Interworking not Supported
287MO Handover: FDA throttled
288MO Handover: SM decoding problem
300Invalid destination address|Provider Error Duplicate Invoke ID
301Invalid destination numbering plan|Provider Error Service Not Supported
302Invalid destination type of number|Provider Error Mistyped Paramter
303Invalid destination flag|Provider Error Resource Limitation
304Invalid number of destinations|Provider Error Initiating Release
305Provider Error Unexpected Response
306Provider Error Service Completion Failure
307EC_Provider No Response from Peer
308Provider Error Invalid Response
400EC_MAP_abort _error
401Stack/Sig Error Map User specific Reason
402Stack/Sig Error Map User Resource Limitation
403Stack/Sig Error Map Resource Unavailable
404Stack/Sig Error Map Application Procedure Cancellation
407EC_HLR/MSC Timeout
409Unknown Error
410EC_Cancelled
411EC_ValidityExpired
412EC_NotSubmittedToSmppChannel
413EC_DESTINATION_FLOODING
414EC_DESTINATION_TXT_FLOODING
415Stack/Sig Response Rejected By Peer
416Stack/Sig Abnormal Event Recieved From Peer
417Stack/Sig Cannot deliver Message
417Sig Error Map Invalid Response from peer
418Sig Error Map Dialogue Does not Exist
419Sig Error Map Max evoke reached
420Stack/Sig Invalid Origination Reference
420Stack/Sig Invalid Origination Reference
421Stack/Sig No Reson
421Stack/Sig No Reson
422Stack/Sig Remote Node Not Reachable
422Stack/Sig Remote Node Not Reachable
423Stack/Sig Map Potential Version Incompatibility
424Stack/Sig Secured Transport Not Possible
424Stack/Sig Secured Transport Not Possible
425Stack/Sig Usr Transport Protection Not Adequate
425Stack/Sig Usr Transport Protection Not Adequate
428Sig Error MAP Subsystem congested
428Sig Error MAP Subsystem congested
429Sig Error MAP Subsystem failure
429Sig Error MAP Subsystem failure
430Sig Error MAP Error in local processing CCIT92
430Sig Error MAP Error in local processing CCIT92
431Sig Error MAP Re assembly failure
431Sig Error MAP Re assembly failure
432Sig Error MAP SCCP failure
432Sig Error MAP SCCP failure
433Sig Error MAP HOP counter violation ITU
433Sig Error MAP HOP counter violation ITU
434Sig Error MAP segmentation not supported
434Sig Error MAP segmentation not supported
435Sig Error MAP Segmentation failure
435Sig Error MAP Segmentation failure
496EC_invalidPduFurmat
497EC_NotSubmittedToGMSC
500EC_PROVIDER_GENERAL_ERROR
501Insufficient Balance
502EC_NO_RESPONSE
503EC_SERVICE_COMPLETION_FAILURE
504EC_UNEXPECTED_RESPONSE_FROM_PEER
507EC_MISTYPED_PARAMETER
508EC_NOT_SUPPORTED_SERVICE
509EC_DUPLICATED_INVOKE_ID
510Temp_Fail
511SPAM_Fail
536EC_PA_providerMalfunction
537EC_PA_supportingDialogOrTransactionRealeased
538EC_PA_ressourceLimitation
539EC_PA_maintenanceActivity
540EC_PA_versionIncompatibility
541EC_PA_abnormalMapDialog
600Internal Error
601Timeout at SRI
602Absent subscriber
703Submit_SM_Timeout
715Expired at BMG
715Expired
792EC_NC_abnormalEventDetectedByPeer
793EC_NC_responseRejectedByPeer
794EC_NC_abnormalEventReceivedFromPeer
795EC_NC_messageCannotBeDeliveredToPeer
796EC_NC_providerOutOfInvoke
801EC_BLACKLISTED_MSISDN
1001No Response from far Network
1024EC_OR_appContextNotSupported
1025EC_OR_invalidDestinationReference
1026EC_OR_invalidOriginatingReference;
1027EC_OR_encapsulatedAC_NotSupported
1028EC_OR_transportProtectionNotAdequate
1029EC_OR_noReasonGiven
1030EC_OR_potentialVersionIncompatibility
1031EC_OR_remoteNodeNotReachable
1152EC_NNR_noTranslationForAnAddressOfSuchNatur
1153EC_NNR_noTranslationForThisSpecificAddress
1154EC_NNR_subsystemCongestion
1155EC_NNR_subsystemFailure
1156EC_NNR_unequippedUser
1157EC_NNR_MTPfailure
1158EC_NNR_networkCongestion
1159EC_NNR_unqualified
1160EC_NNR_errorInMessageTransportXUDT
1161EC_NNR_errorInLocalProcessingXUDT
1162EC_NNR_destinationCannotPerformReassemblyXUDT
1163EC_NNR_SCCPfailure
1164EC_NNR_hopCounterViolation
1165EC_NNR_segmentationNotSupported
1166EC_NNR_segmentationFailure
1281EC_UA_userSpecificReason
1282EC_UA_userResourceLimitation
1283EC_UA_resourceUnavailable
1284EC_UA_applicationProcedureCancellation
1536EC_PA_providerMalfunction
1537EC_PA_supportingDialogOrTransactionRealeased
1538EC_PA_ressourceLimitation
1539EC_PA_maintenanceActivity
1540EC_PA_versionIncompatibility
1541EC_PA_abnormalMapDialog
1793EC_NC_responseRejectedByPeer
1794EC_NC_abnormalEventReceivedFromPeer
1795EC_NC_messageCannotBeDeliveredToPeer
1796EC_NC_providerOutOfInvoke
2000Make_Call API Failure
2001Message too long
2002Command length is invalid
2003Command ID is invalid or not supported
2004Incorrect bind status for given command
2005Already bound
2006Invalid Priority Flag
2007Invalid registered delivery flag
2008System error
2010Invalid source address
2011Invalid destination address
2012Message ID is invalid
2013Bind failed
2014Invalid password
2015Invalid System ID
2017Cancelling message failed
2019Message recplacement failed
2020Message queue full
2021Invalid service type
2022Invalid services type
2048EC_TIME_OUT
2049EC_IMSI_BLACKLISTED
2050EC_DEST_ADDRESS_BLACKLISTED
2051EC_InvalidMscAddress
2052EC_BLACKLISTED_DESTINATIONADDRESS
2064Invalid destination flag
2066Invalid submit with replace request
2067Invalid esm class set
2068Invalid submit to ditribution list
2069Submitting message has failed
2072Invalid source address type of number ( TON )
2073Invalid source address numbering plan ( NPI )
2080Invalid destination address type of number ( TON )
2081Invalid destination address numbering plan ( NPI )
2083Invalid system type
2084Invalid replace_if_present flag
2085Invalid number of messages
2088Throttling error
2097Invalid scheduled delivery time
2098Invalid Validty Period value
2099Predefined message not found
2100ESME Receiver temporary error
2101ESME Receiver permanent error
2102ESME Receiver reject message error
2103Message query request failed
2168DND Block
2192Error in the optional part of the PDU body
2193TLV not allowed
2194Invalid parameter length
2195Expected TLV missing
2196Invalid TLV value
2254Transaction delivery failure
2255Unknown error
2256ESME not authorised to use specified servicetype
2257ESME prohibited from using specified operation
2258Specified servicetype is unavailable
2259Specified servicetype is denied
2260Invalid data coding scheme
2261Invalid source address subunit
2262Invalid destination address subunit
2300Incorrect destination address
2301Incorrect number of destination addresses
2302Syntax error in user data parameter
2303Incorrect bin/head/normal user data parameter combination
2304Incorrect dcs parameter usage
2305Incorrect validity period parameters usage
2306Incorrect originator address usage
2307Incorrect PID parameter usage
2308Incorrect first delivery parameter usage
2309Incorrect reply path usage
2310Incorrect status report request parameter usage
2311Incorrect cancel enabled parameter usage
2312Incorrect priority parameter usage
2313Incorrect tariff class parameter usage
2314Incorrect service description parameter usage
2315Incorrect transport type paramdeter usage
2316Incorrect message type parameter usage
2318Incorrect MMS parameter usage
2319Incorrect operation timer parameter usage
2320Incorrect dialogue ID parameter usage
2321Incorrect alpha originator address usage
2322Invalid data for alpha numeric originator
2323Online closed user group rejection
2324Licence exceeded
4000DLT_SCRUBBING_TIMEOUT
4001DLT_SCRUBBING_TIMEOUT
4096EC_InvalidPduFormat
4097EC_NotSubmittedToGMSC
4100EC_Cancelled
4101EC_ValidityExpired
4103EC_DESTINATION_FLOODING
4104EC_DESTINATION_TXT_FLOODING
4106BLOCKED_BY_DLT
4107DLT_SCRUBBING_TIMEOUT
4108SENDER_BLOCKED_BY_DLT
5000SCRUBBING_FAILED
5001SCRUBBING_FAILED
5101BLOCKED_BY_DLT
5102BLOCKED_BY_DLT
5103BLOCKED_BY_DLT
5104BLOCKED_BY_DLT
5105BLOCKED_BY_DLT
5106BLOCKED_BY_DLT
5107BLOCKED_BY_DLT
5108BLOCKED_BY_DLT
5201SENDER_BLOCKED_BY_DLT
5202SENDER_BLOCKED_BY_DLT
5203SENDER_MISMATCH_WITH_ENTITY
5204SENDER_BLOCKED_BY_DLT
5205Entity_ID_Not_Matched
5301TEMPLATE_ERROR
5302TEMPLATE_ERROR
5303TEMPLATE_ERROR
5304Content ID not in DB
5305TEMPLATE_ERROR
5306TEMPLATE_ERROR
5307TEMPLATE_ERROR
5308TEMPLATE_ERROR
5401TEMPLATE_ERROR
5402TEMPLATE_ERROR
5403TEMPLATE_ERROR
5404TEMPLATE_ERROR
5405TEMPLATE_ERROR
5406TEMPLATE_ERROR
5501CONSENT_FAILED
5502CONSENT_FAILED
5503CONSENT_FAILED
7001ENTITY_ID_ERROR
7002ENTITY_ID_ERROR
7003ENTITY_ID_ERROR
7004ENTITY_ID_ERROR
20ABearer Service Not Supported
20bTele Service Not Provisioned
20cError Equipment
20dCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21bAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21fSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Reply from Subscriber
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40aStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error MAP guard timer expired
41BSig Error MAP SPCAUSE mask
41cSig Error MAP No translation Based Address
41dSig Error MAP No translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig DlG Invalid Destination Reference
42aSig Error MAP unequipped user
42bSig Error MAP network failure
42cSig Error MAP network congestion
42dSig Error MAP unqualified
42ESig Error MAP HOP Counter violation ANS92
42FSig Error MAP Error in message transport CCIT92
20ABearer Service Not Supported
20BTele Service Not Provisioned
20CError Equipment
20DCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21BAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21FSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Subscriber Reply
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40AStack/Sig Error Map Provider Malfunction
40AStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error Map guard Timer Expired
41BSig Error Map SPCAUSE mask
41CSig Error MAP No Translation Basd Address
41DSig Error MAP No Translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig Dlg Invalid Destination Reference
42ASig Error MAP Un Equipped User
42ASig Error MAP Un Equipped User
42BSig Error MAP Network Failure
42BSig Error MAP Network Failure
42CSig Error MAP Network Conjestion
42CSig Error MAP Network Conjestion
42DSig Error MAP un Qualified
42DSig Error MAP un Qualified
42ESig Error MAP HOP Counter violaion ANS92
42ESig Error MAP HOP Counter violaion ANS92
42FSig Error MAP Error in message transport CCIT92
42FSig Error MAP Error in message transport CCIT92

Sending SMS To An Optin Group

The URL for sending an SMS to an optin group is in the following format:

https://www.mysmsapp.in/api/push.json? method=optin&api_key=Ad9e5XXXXXXXX&sender=INFXXX&message=testing&format=json&name=keyword777

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
delivery reports URLdlrurlThe URL to receive delivery reports. Spiffing custom is mandatory.delivery reports URL
Message IDcustomCustom message ID by customer, comma separatedAlphanumeric (max 40 char)
Schedule timetimeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM
unicodeunicodeTo specify that the message to be sent is in unicode format. Also can be used for automatic detection of unicode SMS.1 / 0 / auto
flashflashTo specify that the message is to be sent in the flash format1 or 0

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the Optin API to send an SMS is in the below format :

ErrorCodeDescription
0NORMAL DELIVERED
1Source not found|EC_UNKNOWN_SUBSCRIBER
2Sink not found|EC_UNKNOWN_BASE_STATION
3Delivery zone not found|DND Fail
5Location not found|EC_UNIDENTIFIED_SUBSCRIBER
6Location blocked|Absent subscriber
7Reply path not found|UNKNOWN EQUIPMENT
8Message not submit|FSM TIMEOUT
9Unsupported number plan|EC_ILLEGAL_SUBSCRIBER
10Unsupported type of number|EC_BEARER_SERVICE_NOT_PROVISIONED
11Message not DELIVER or STATUS|EC_TELESERVICE_NOT_PROVISIONED
12Dialling zone not found|EC_ILLEGAL_EQUIPMENT
13Not home zone and IMSI not allowed|EC_CALL_BARRED
14Not home zone and IMSI fetch failed|Barred unauthorized message originator
15Screening block|CUG REJECT
18ESME error|message waiting for report expired'
19Originating location mismatch|SRIAck unsuccessful with any other error codes'
20Originating reservation failed|EC_SS_INCOMPATIBILITY
21Originating reservation denied subscription not found|EC_FACILITY_NOT_SUPPORTED
22Originating reservation denied subscription state illegal|Memory capacity exceeded
23Originating reservation denied call case blocked for subscription|Unknown Subscriber'
24Originating reservation denied call case blocked for subscription type|call forbidden'
25Originating reservation denied low balance|the network does not support SMS'
26'teleservice not supported'
27Absent subscriber
29'HLR:data error in route signal'
30Terminating reservation failed|HLR:data lacked'
31Terminating reservation denied subscription not found|EC_SUBSCRIBER_BUSY_FOR_MT_SMS
32Terminating reservation denied subscription state illegal|EC_SM_DELIVERY_FAILURE
33Terminating reservation denied call case blocked for subscription|EC_MESSAGE_WAITING_LIST_FULL
34Terminating reservation denied call case blocked for subscription type|EC_SYSTEM_FAILURE
35Terminating reservation denied low balance|EC_DATA_MISSING
36EC_UNEXPECTED_DATA_VALUE
37'Unmarked Subscriber'
38'failure because the subscriber is busy'
39'VMSC isolated'
40System is congested|VMSC:data lacked'
41Originating IMSI mismatch|VMSC:unexpected data'
42'MS error'
43Not Supported by equipment
44Illegal equipment
45Quarantine Add|Unspecific PID Error
46Quarantine Remove|Message Class Not Supported
47DCS error
48TPDU Not Supported
49Short message delivery failure with memory capacity exceeded
50Unexpected error from Store|UNKNOWN ERROR
51Direct delivery disabled from store|EC_RESOURCE_LIMITATION
53Message limit exceeded|Subscriber Busy For MT-SMS
54Retry scheme ended|Data Download Error
60Originator blocked|Absent subscriber
61Destination blocked|Absent subscriber
62Keyword blocked|Absent subscriber
63SC address blocked|Absent subscriber
64Blocked due to exceeded quota|Absent subscriber
65Loop detected|Absent subscriber
66Data coding scheme blocked|Absent subscriber over GPRS Page Fail
67Information element identifier blocked|Absent subscriber over GPRS Detached
68Country Code Validation Block|Absent subscriber over GPRS Deregistered
69Destination Flooding
70No ESME provider available|MS store is full'
71ESME account not connected|EC_UNKNOWN_ALPHABET
72No ESME sub account routing|EC_USSD_BUSY
74ESME local throttling - exceeded msg/s|INVALID HEADER IN MSG
80Home routing sender GT mismatch|PENDING DLR (Retry )
81Location mismatch between provided location and location known to HLR.|Service not supported
82IMSI mismatch between provided IMSI |Mistyped parameter
83Local throttling by sink|No response from the peer
84The IMSI could not be retrieved from the HSS|Resource limitation
85The IMEI of the UE is unknown|Initiating release
86The user location is unknown|Unrecognised error
87ESME router|Provider Error (In case of any failures observed in TCAP level this error will generate).
88Network fluctuation from far End Operator(Temporary Error)
89INVALID PACKET AT SMSC LEVEL
90USER-ABORT
91PROVIDER-ABORT
92MSC NUMBER MISSING
93Equipment protocol error
94Equipment not SM equipped
95Unknown service centre
96Service Centre congestion
97INVALID SCHEDULE DELIVERY TIME
98Subscriber not SC subscriber
99Invalid SME address
100Unidentified subscriber|no response from the called subscriber'
101Facility not supported|VMSC:the called MS poweroff'
102System failure|VMSC:limited due to MS roaming' / SENDER ID BLOCKED
103Unexpected data value|ROUTE NOT ACTIVE
104Data missing|OFF-NET NOT ACTIVE FOR ACCOUNT/ ON-NET ROUTES NOT DEFINED
105Equipment protocol error|MTP_FAILURE
106UNKNOWN service centre address|MS response is overtime'
107Service centre congestion|HLR:the subscriber is unregistered'
108Invalid short message entity address|ROUTE BLOCKED FOR THIS SERIES
109Subscriber not service centre subscriber|MSISDN SERIES NOT CONFIGURED
110Reject|NOT ABLE TO GET FINAL ROUTE
111Local cancel|Queue_Unvailable
112Abort|NOT A VALID TEMPLATE
113Exception|MANDATORY WORDS NOT FOUND
114UNKNOWN|DEFAULT ROUTE NOT FOUND IN CONFIGURED ROUTES
115ROUTE NOT CONFIGURED AT PLATFORM LEVEL
116Map Dialog P Abort Indication Provider Reason: Maintenance Activity
117Map Dialog P Abort Indication Provider Reason: Version Incompatibility
118Map Dialog P Abort Indication Provider Reason: Abnormal Dialogue
119MAP_DLGUA_UsrRsn_NTR_MapDlgUnavailable
120MAP_DLGUA_UsrRsn_NTR_MapNotConfigured
121MAP_DLGUA_UsrRsn_NTR_OtherErr
122MAP_DLGRJT_PrvRsn_NotSent
123INTERNATIONAL ROAMING
124EC_OR_appContextNotSupported
125EC_OR_invalidDestinationReference
126EC_OR_invalidOriginatingReference
127EC_OR_encapsulatedAC_NotSupported
128EC_OR_transportProtectionNotAdequate
129EC_OR_noReasonGiven
130EC_OR_potentialVersionIncompatibility
131EC_OR_remoteNodeNotReachable
132Map Dialog Rejected Refuse Reason: Application Context not supported
133Map Dialog Rejected Refuse Reason: Potential Version Incompatibility
134Map Dialog Rejected Refuse Reason: Remote Node not reachable
135Map Dialog Rejected Provider Reason: Provider malfunction
136Map Dialog Rejected Provider Reason: Transaction Released
137Map Dialog Rejected Provider Reason: Resource Limitation
138Map Dialog Rejected Provider Reason: Maintenance Activity
139Map Dialog Rejected Provider Reason: Version Incompatibility
140Map Dialog Rejected Provider Reason: Abnormal Dialogue
141Map Dialog User Abort Diagnostic Info: Short Term resource Limitation
142Map Dialog User Abort Diagnostic Info: Long term resource limitation
143Map Dialog User Abort Diagnostic Info: Handover cancellation
144Map Dialog User Abort Diagnostic Info: Radio Channel Release
145Map Dialog User Abort Diagnostic Info: Call Release
146Map Dialog User Abort Diagnostic Info: Network path Release
147Map Dialog User Abort Diagnostic Info: Associated Procedure release
148Map Dialog User Abort Diagnostic Info: Tandem Dialog Release
149Map Dialog User Abort Diagnostic Info: Remote Operation Failure
150UNKNOWN subscriber|Map Dialog User Abort User Reason: User specific reason
151Call barred|Map Dialog User Abort User Reason: User resource limitation
152Teleservice not provisioned|EC_NNR_noTranslationForAnAddressOfSuchNature
153Absent subscriber|EC_NNR_noTranslationForThisSpecificAddress
154Facility not supported|EC_NNR_subsystemCongestion
155System failure|EC_NNR_subsystemFailure
156Unexpected data value|EC_NNR_unequippedUser
157Data missing|EC_NNR_MTPfailure
158Memory capacity exceeded|EC_NNR_networkCongestion
159Mobile subscriber not reachable|EC_NNR_unqualified
160Reject|EC_NNR_errorInMessageTransportXUDT
161Local cancel|EC_NNR_errorInLocalProcessingXUDT
162Abort|EC_NNR_destinationCannotPerformReassemblyXUDT
163Exception|EC_NNR_SCCPfailure
164UNKNOWN|EC_NNR_hopCounterViolation
165EC_NNR_segmentationNotSupported
166EC_NNR_segmentationFailure
167USSD platform Unknown error
168DND Blocked
169MAP-P-Abort: Provider reasons
170MAP-P-Abort Provider reason: Malfunction
171MAP-P-Abort Provider reason: Dialog Released
172'waiting queue in destination subscriber table is full'
173MAP-P-Abort Provider reason: Abnormal Dialog
174MAP-P-Abort: Invalid PDU
175MAP-Open: Out of MAP dialogs
176Invalid Service code
177Subscriber MSISDN Blacklisted
178Subscriber IMSI Blacklisted
179Invalid Originating Address with Length greater than 20 chars
180MAP-Open Refuse reason: Node Not Reached
181'service barred'
182'operation barred'
183VLRBlackListed
184VLRWhiteListed
185MAP-Notice Problem: Message Cannot Be Delivered
186BILNG_SystemError
187MAP-Notice: Abnormal event detected by peer
188MAP-U-Abort: Error
189MAP-U-Abort User Reason: User Specific Reason
190MAP-U-Abort: User resource limitation
191MAP-U-Abort: Resource unavailable (short term)
192Unexpected session release from Servers/3rd party APP
193'unknServCent'
194'sc_Congestion'
195'invaSME_Add'
196'subsNotSC_Subsc'
197Application Specific Error from Client
198MAP-U-Abort: Application procedure cancellation (tandem dialogue released)
199MAP-U-Abort: Application procedure cancellation (remote operations failure)
200Unidentified subscriber|OPERATOR BLOCKED FOR ACCOUNT
201Absent subscriber IMSI detached|EC_unknown Subscriber
202Absent subscriber no page response|Unknown Base Station
203Subscriber busy for MT-SMS|Unknown MSC
205Illegal subscriber|EC_Unidentified Subscriber
206Illegal equipment|Absent Subscriber for SM
206Illegal equipment|Absent Subscriber for SM
207System failure|Unknown Equipment
208Unexpected data value|Roaming Not Allowed
209Data missing|Illegal Subscriber
210Memory capacity exceeded|Illegal SS Operation
211Equipment protocol error|SS Error Status
212Equipment not short message equipped|SS Not Available
213Reject|SS Subscription Violation
214Local cancel|SS Incompatible
215Abort|HLR:limited due to MS roaming'
216Exception|Internal IPC memory allocation Failure
217UNKNOWN|Internal IPC Router Failure
218'HLR:illegal subscriber'
219'HLR:subscriber absent'
220'HLR:the called MS poweroff'
221MSISDN BLOCKED
221Message List Full
222MESSAGE CONTENT IS BLACKLISTED/EC_Network System Failure
223Data Missing
224Unexpected Data
225MESSAGE CONTENT IS BLACKLISTED AT OPERATOR/ 'HLR:no response'
226'VMSC:no response'
227IN Subscriber not exist1
228'the destination subscriber PPS authentication overtime'
229'IN Invalid subscriber'
230Not Allowed
231ATI Not Allowed
232No Group Call Number Available
233Resource Limitation
234Unauthorized Requesting Network
235Unathorized LCS Client
236Position Method Failure
237Custom error 8
238Custom error 9
239Custom error 10
240Recipient Temporary Error
241Recipient Permanent Error
242Service Not configured/for a particular circle/subscriber. Or simply menu is incomplete or service i
243Terminating session due to invalid input
244Unspecific
245'HLR:the remote address not reachable' /'VMSC:Invalid Destination'
246Client Resource Not Available
247Unknown Alphabet
248EC_TIME_OUT
249EC_IMSI_BLACKLISTED
250Personal service barring|EC_DEST_ADDRESS_BLACKLISTED
251Personal service barring|EC_InvalidMscAddress
252Personal service barring|MESSAGE VALIDITY EXPIRED
253Personal service barring|the origination subscriber PPS authentication SCP connection broken'
254Personal service barring|any other error code other than 255
255Personal service barring|EC_UNKNOWN_ERROR
255Personal service barring|EC_UNKNOWN_ERROR
256Personal service barring|EC_SM_DF_memoryCapacityExceeded
257Personal service barring|EC_SM_DF_equipmentProtocolError
258EC_SM_DF_equipmentNotSM_Equipped
259EC_SM_DF_unknownServiceCentre
260EC_SM_DF_sc_Congestion
260'SMS not supported by MS'
261EC_SM_DF_invalidSME_Address
262EC_SM_DF_subscriberNotSC_Subscriber
263MO Handover: Destination SME Barred
264MO Handover: Duplicate Message Rejected
265MO Handover: Validity Period Format Unsupported
266MO Handover: Validity Period Unsupported
267MO Handover: Not Supported by equipment
268MO Handover: System Error
269MO Handover: Duplicated invoke id
270MO Handover: Service not supported
271MO Handover: Mistyped parameter
272MO Handover: No response from the peer
273MO Handover: Resource limitation
274MO Handover: Initiating release
275Error Gateway
276MO Handover: Unexpected error
277MO Handover: Unexpected response from the peer
278MO Handover: Unable to complete operation within timeout
279MO Handover: Invalid response received
280Error|MO Handover: TCAP error
281EC_UA_userSpecificReason
282EC_UA_userResourceLimitation
283EC_UA_resourceUnavailable
284EC_UA_applicationProcedureCancellation
285MO Handover: Unexpected Data Value
286MO Handover: Telematic Interworking not Supported
287MO Handover: FDA throttled
288MO Handover: SM decoding problem
300Invalid destination address|Provider Error Duplicate Invoke ID
301Invalid destination numbering plan|Provider Error Service Not Supported
302Invalid destination type of number|Provider Error Mistyped Paramter
303Invalid destination flag|Provider Error Resource Limitation
304Invalid number of destinations|Provider Error Initiating Release
305Provider Error Unexpected Response
306Provider Error Service Completion Failure
307EC_Provider No Response from Peer
308Provider Error Invalid Response
400EC_MAP_abort _error
401Stack/Sig Error Map User specific Reason
402Stack/Sig Error Map User Resource Limitation
403Stack/Sig Error Map Resource Unavailable
404Stack/Sig Error Map Application Procedure Cancellation
407EC_HLR/MSC Timeout
409Unknown Error
410EC_Cancelled
411EC_ValidityExpired
412EC_NotSubmittedToSmppChannel
413EC_DESTINATION_FLOODING
414EC_DESTINATION_TXT_FLOODING
415Stack/Sig Response Rejected By Peer
416Stack/Sig Abnormal Event Recieved From Peer
417Stack/Sig Cannot deliver Message
417Sig Error Map Invalid Response from peer
418Sig Error Map Dialogue Does not Exist
419Sig Error Map Max evoke reached
420Stack/Sig Invalid Origination Reference
420Stack/Sig Invalid Origination Reference
421Stack/Sig No Reson
421Stack/Sig No Reson
422Stack/Sig Remote Node Not Reachable
422Stack/Sig Remote Node Not Reachable
423Stack/Sig Map Potential Version Incompatibility
424Stack/Sig Secured Transport Not Possible
424Stack/Sig Secured Transport Not Possible
425Stack/Sig Usr Transport Protection Not Adequate
425Stack/Sig Usr Transport Protection Not Adequate
428Sig Error MAP Subsystem congested
428Sig Error MAP Subsystem congested
429Sig Error MAP Subsystem failure
429Sig Error MAP Subsystem failure
430Sig Error MAP Error in local processing CCIT92
430Sig Error MAP Error in local processing CCIT92
431Sig Error MAP Re assembly failure
431Sig Error MAP Re assembly failure
432Sig Error MAP SCCP failure
432Sig Error MAP SCCP failure
433Sig Error MAP HOP counter violation ITU
433Sig Error MAP HOP counter violation ITU
434Sig Error MAP segmentation not supported
434Sig Error MAP segmentation not supported
435Sig Error MAP Segmentation failure
435Sig Error MAP Segmentation failure
496EC_invalidPduFurmat
497EC_NotSubmittedToGMSC
500EC_PROVIDER_GENERAL_ERROR
501Insufficient Balance
502EC_NO_RESPONSE
503EC_SERVICE_COMPLETION_FAILURE
504EC_UNEXPECTED_RESPONSE_FROM_PEER
507EC_MISTYPED_PARAMETER
508EC_NOT_SUPPORTED_SERVICE
509EC_DUPLICATED_INVOKE_ID
510Temp_Fail
511SPAM_Fail
536EC_PA_providerMalfunction
537EC_PA_supportingDialogOrTransactionRealeased
538EC_PA_ressourceLimitation
539EC_PA_maintenanceActivity
540EC_PA_versionIncompatibility
541EC_PA_abnormalMapDialog
600Internal Error
601Timeout at SRI
602Absent subscriber
703Submit_SM_Timeout
715Expired at BMG
715Expired
792EC_NC_abnormalEventDetectedByPeer
793EC_NC_responseRejectedByPeer
794EC_NC_abnormalEventReceivedFromPeer
795EC_NC_messageCannotBeDeliveredToPeer
796EC_NC_providerOutOfInvoke
801EC_BLACKLISTED_MSISDN
1001No Response from far Network
1024EC_OR_appContextNotSupported
1025EC_OR_invalidDestinationReference
1026EC_OR_invalidOriginatingReference;
1027EC_OR_encapsulatedAC_NotSupported
1028EC_OR_transportProtectionNotAdequate
1029EC_OR_noReasonGiven
1030EC_OR_potentialVersionIncompatibility
1031EC_OR_remoteNodeNotReachable
1152EC_NNR_noTranslationForAnAddressOfSuchNatur
1153EC_NNR_noTranslationForThisSpecificAddress
1154EC_NNR_subsystemCongestion
1155EC_NNR_subsystemFailure
1156EC_NNR_unequippedUser
1157EC_NNR_MTPfailure
1158EC_NNR_networkCongestion
1159EC_NNR_unqualified
1160EC_NNR_errorInMessageTransportXUDT
1161EC_NNR_errorInLocalProcessingXUDT
1162EC_NNR_destinationCannotPerformReassemblyXUDT
1163EC_NNR_SCCPfailure
1164EC_NNR_hopCounterViolation
1165EC_NNR_segmentationNotSupported
1166EC_NNR_segmentationFailure
1281EC_UA_userSpecificReason
1282EC_UA_userResourceLimitation
1283EC_UA_resourceUnavailable
1284EC_UA_applicationProcedureCancellation
1536EC_PA_providerMalfunction
1537EC_PA_supportingDialogOrTransactionRealeased
1538EC_PA_ressourceLimitation
1539EC_PA_maintenanceActivity
1540EC_PA_versionIncompatibility
1541EC_PA_abnormalMapDialog
1793EC_NC_responseRejectedByPeer
1794EC_NC_abnormalEventReceivedFromPeer
1795EC_NC_messageCannotBeDeliveredToPeer
1796EC_NC_providerOutOfInvoke
2000Make_Call API Failure
2001Message too long
2002Command length is invalid
2003Command ID is invalid or not supported
2004Incorrect bind status for given command
2005Already bound
2006Invalid Priority Flag
2007Invalid registered delivery flag
2008System error
2010Invalid source address
2011Invalid destination address
2012Message ID is invalid
2013Bind failed
2014Invalid password
2015Invalid System ID
2017Cancelling message failed
2019Message recplacement failed
2020Message queue full
2021Invalid service type
2022Invalid services type
2048EC_TIME_OUT
2049EC_IMSI_BLACKLISTED
2050EC_DEST_ADDRESS_BLACKLISTED
2051EC_InvalidMscAddress
2052EC_BLACKLISTED_DESTINATIONADDRESS
2064Invalid destination flag
2066Invalid submit with replace request
2067Invalid esm class set
2068Invalid submit to ditribution list
2069Submitting message has failed
2072Invalid source address type of number ( TON )
2073Invalid source address numbering plan ( NPI )
2080Invalid destination address type of number ( TON )
2081Invalid destination address numbering plan ( NPI )
2083Invalid system type
2084Invalid replace_if_present flag
2085Invalid number of messages
2088Throttling error
2097Invalid scheduled delivery time
2098Invalid Validty Period value
2099Predefined message not found
2100ESME Receiver temporary error
2101ESME Receiver permanent error
2102ESME Receiver reject message error
2103Message query request failed
2168DND Block
2192Error in the optional part of the PDU body
2193TLV not allowed
2194Invalid parameter length
2195Expected TLV missing
2196Invalid TLV value
2254Transaction delivery failure
2255Unknown error
2256ESME not authorised to use specified servicetype
2257ESME prohibited from using specified operation
2258Specified servicetype is unavailable
2259Specified servicetype is denied
2260Invalid data coding scheme
2261Invalid source address subunit
2262Invalid destination address subunit
2300Incorrect destination address
2301Incorrect number of destination addresses
2302Syntax error in user data parameter
2303Incorrect bin/head/normal user data parameter combination
2304Incorrect dcs parameter usage
2305Incorrect validity period parameters usage
2306Incorrect originator address usage
2307Incorrect PID parameter usage
2308Incorrect first delivery parameter usage
2309Incorrect reply path usage
2310Incorrect status report request parameter usage
2311Incorrect cancel enabled parameter usage
2312Incorrect priority parameter usage
2313Incorrect tariff class parameter usage
2314Incorrect service description parameter usage
2315Incorrect transport type paramdeter usage
2316Incorrect message type parameter usage
2318Incorrect MMS parameter usage
2319Incorrect operation timer parameter usage
2320Incorrect dialogue ID parameter usage
2321Incorrect alpha originator address usage
2322Invalid data for alpha numeric originator
2323Online closed user group rejection
2324Licence exceeded
4000DLT_SCRUBBING_TIMEOUT
4001DLT_SCRUBBING_TIMEOUT
4096EC_InvalidPduFormat
4097EC_NotSubmittedToGMSC
4100EC_Cancelled
4101EC_ValidityExpired
4103EC_DESTINATION_FLOODING
4104EC_DESTINATION_TXT_FLOODING
4106BLOCKED_BY_DLT
4107DLT_SCRUBBING_TIMEOUT
4108SENDER_BLOCKED_BY_DLT
5000SCRUBBING_FAILED
5001SCRUBBING_FAILED
5101BLOCKED_BY_DLT
5102BLOCKED_BY_DLT
5103BLOCKED_BY_DLT
5104BLOCKED_BY_DLT
5105BLOCKED_BY_DLT
5106BLOCKED_BY_DLT
5107BLOCKED_BY_DLT
5108BLOCKED_BY_DLT
5201SENDER_BLOCKED_BY_DLT
5202SENDER_BLOCKED_BY_DLT
5203SENDER_MISMATCH_WITH_ENTITY
5204SENDER_BLOCKED_BY_DLT
5205Entity_ID_Not_Matched
5301TEMPLATE_ERROR
5302TEMPLATE_ERROR
5303TEMPLATE_ERROR
5304Content ID not in DB
5305TEMPLATE_ERROR
5306TEMPLATE_ERROR
5307TEMPLATE_ERROR
5308TEMPLATE_ERROR
5401TEMPLATE_ERROR
5402TEMPLATE_ERROR
5403TEMPLATE_ERROR
5404TEMPLATE_ERROR
5405TEMPLATE_ERROR
5406TEMPLATE_ERROR
5501CONSENT_FAILED
5502CONSENT_FAILED
5503CONSENT_FAILED
7001ENTITY_ID_ERROR
7002ENTITY_ID_ERROR
7003ENTITY_ID_ERROR
7004ENTITY_ID_ERROR
20ABearer Service Not Supported
20bTele Service Not Provisioned
20cError Equipment
20dCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21bAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21fSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Reply from Subscriber
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40aStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error MAP guard timer expired
41BSig Error MAP SPCAUSE mask
41cSig Error MAP No translation Based Address
41dSig Error MAP No translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig DlG Invalid Destination Reference
42aSig Error MAP unequipped user
42bSig Error MAP network failure
42cSig Error MAP network congestion
42dSig Error MAP unqualified
42ESig Error MAP HOP Counter violation ANS92
42FSig Error MAP Error in message transport CCIT92
20ABearer Service Not Supported
20BTele Service Not Provisioned
20CError Equipment
20DCall Barred
20EError Forward Violation
20FError CUG Reject
21ASubsequent Handover Failure
21BAbsent Subscriber for MT
21CIncompatible Terminal
21DShort Term Denial
21ELong Term Denial
21FSubscriber Busy for MT
22CNumber of PW attempts Violation
22DBusy Subscriber
22ENo Subscriber Reply
22FForwarding Failed
23AUnknown or Unreachable LCS Client
40AStack/Sig Error Map Provider Malfunction
40AStack/Sig Error Map Provider Malfunction
40BStack/Sig Error Map Unrecognised Transaction ID
40BStack/Sig Error Map Unrecognised Transaction ID
40CStack/Sig Error Dialog Resource Limitation
40CStack/Sig Error Dialog Resource Limitation
40DStack/Sig Error Map Maintenance Activity
40DStack/Sig Error Map Maintenance Activity
40EStack/Sig Error Map Version Incompatibility
40EStack/Sig Error Map Version Incompatibility
40FStack/Sig Error Abnormal Map Dialogue
40FStack/Sig Error Abnormal Map Dialogue
41ASig Error Map guard Timer Expired
41BSig Error Map SPCAUSE mask
41CSig Error MAP No Translation Basd Address
41DSig Error MAP No Translation specific address
41EStack/Sig Application Context Not Supported
41FStack/Sig Dlg Invalid Destination Reference
42ASig Error MAP Un Equipped User
42ASig Error MAP Un Equipped User
42BSig Error MAP Network Failure
42BSig Error MAP Network Failure
42CSig Error MAP Network Conjestion
42CSig Error MAP Network Conjestion
42DSig Error MAP un Qualified
42DSig Error MAP un Qualified
42ESig Error MAP HOP Counter violaion ANS92
42ESig Error MAP HOP Counter violaion ANS92
42FSig Error MAP Error in message transport CCIT92
42FSig Error MAP Error in message transport CCIT92

Sending A Port SMS

Using the below API we can send a normal or unicode SMS to a particular port Application port numbers can be used in SMS messages to deliver a particular SMS to an application on a mobile phone. If any application is present and running in that particular port, the text is received as port SMS else the message will hit the native inbox of the mobile

NOTE:The API tries to hit the application(port) for 10 seconds, if unsuccessful the message is delivered on the native inbox

To send a port SMS using the HTTP API, the following URL format is used:

https://www.mysmsapp.in/api/push.json?method=sms&api_key=Ad9e5XXXXXXXXXXXXX&to=997XXXXXXX,997XXXXXXX&sender=INFXXX&message=testing&format=json&port=8090

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)

Optional Parameters

NameParameterDescriptionExpected Values
delivery reports URLdlrurlThe URL to receive delivery reports. Spiffing custom is mandatory.delivery reports URL
Message IDcustomCustom message ID by customer, comma separatedAlphanumeric (max 40 char)
Schedule timetimeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM
unicodeunicodeTo specify that the message to be sent is in unicode format. Also can be used for automatic detection of unicode SMS.1 / 0 / auto
flashflashTo specify that the message is to be sent in the flash format1 or 0

Advanced Parameters(Optional)

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
Callback function namecallbackCallback function for JSONP response format.String
Custom reference fieldscustom1 & custom2Custom reference fieldsAlphanumeric (max 40 char)
port numberportPort number to which SMS has to be sentValid integer port number above 2000

Message Length - Multipart Port Messages

Standard GSM 03.38 Character Set

You could send up to 1000 characters as multipart message which will be split into 7 messages internally.

Number of SMSNumber of characters in the linked SMS
1146 characters
2292 characters (2 x 146)
3438 characters (3 x 146)
..........
6upto 918 characters (6 x 153)
71000 characters (6 x 146) + 124

Unicode

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
164 characters
2128 characters (2 x 64)
3192 characters (3 x 64)
.......
6upto 918 characters (6 x 153)
7500 characters (7 x 64) + 52

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send an SMS is in the below format :

STATUSMESSAGE
A400Api file not found in project
A401AMethod Not Implemented.
A401BMethod Not Found
A402Api Key not found.
A403Api Signature not found
A404Your api account got suspended
A405Api secret not found.
A406Request is not allowed from this ip
A407Header misconfigured
A408Api Signature not equal

Adding Contacts to a Group

The URL for adding contacts to a group is in the following format:

https://www.mysmsapp.in/api/push.json?method=groups.register&api_key=Ad9e5XXXXXXXXXXXXX&name=friends&number=91XXXXXXXXXX&fullname=John&email=abc@gmail.com&format=xml

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
contact namefullnamename of the contactname of the contact
email addressemailemail of the contactemail of the contact
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
add/delete actionaction. Add is DefaultFlag to specify the actionadd/delete

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to create a contact group is in the below format :

STATUSMESSAGE
A420Group name/id missing
A421Group is empty/Invalid group
A422Invalid mobile number
A423Group name/number missing
A424Group Name does not exist!
A425Number does not Exist

Sending Message to a group

The URL for sending a simple message to a group is in the following format:

https://www.mysmsapp.in/api/push.json?method=groups&api_key=Ad9e5XXXXXXXXXXXXX&name=MYGROUP&sender=INFXXX&message=testing

The URL for sending a customized message to a group is in the following format:

https://www.mysmsapp.in/api/push.json?
method=groups&api_key=Ad9e5XXXXXXXXXXXXX&name=MYGROUP&sender=INFXXX&message=Dear {name}, Your email is {email}

Here {name} and {email} are variables and picked up from the group MYGROUP corresponding to each mobile number.

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)
Schedule time timeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Schedule timetimeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM
unicodeunicodeTo specify that the message to be sent is in unicode format. Also can be used for automatic detection of unicode SMS.1 / 0 / auto
flashflashTo specify that the message is to be sent in the flash format1 or 0

Advanced Parameters(Optional)

The advanced parameters in the HTTP API are tabulated below :

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
Callback function namecallbackCallback function for JSONP response formatString

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send message to a contact group is in the below format :

STATUSMESSAGE
A420Group name/id missing
A421Group is empty/Invalid group
A422Invalid mobile number
A423Group name/number missing
A424Group Name does not exist!
A425Number does not Exist

Delete Schedule

The URL for deleting an SMS slot that is scheduled is in the following format:

In order to delete a scheduled slot,there should a minimum gap of 15mins before its execution 

https://www.mysmsapp.in/api/push.json? method=sms.schedule&api_key=Ad9e5XXXXXXXXXXXXX&groupid=121&format=xml

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms.schedule
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
group IDgroupidgroup id that has to be deletedgroup id that has to be deleted

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to delete an SMS schedule is in the below format :

STATUSMESSAGE
A431Invalid Group ID
A434Campaign within next 5 minutes cannot be modified/canceled.

Edit Schedule

The URL for editing an SMS slot that is scheduled is in the following format:

In order to edit a scheduled slot,there should a minimum gap of 5mins before its execution

https://www.mysmsapp.in/api/push.json? method=sms.schedule&api_key=Ad9e5XXXXXXXXXXXXX&groupid=121&format=xml&task=modify&time=24 dec 2014 9:00pm

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)
Schedule time timeDate and time for scheduling an SMSEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PM

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to Edit an SMS schedule is in the below format :

STATUSMESSAGE
A431Invalid Group ID
A434Campaign within next 5 minutes cannot be modified/canceled.

Credits Availability Check

The URL for checking the credits in your account is in the following format:

https://www.mysmsapp.in/api/creditstatus?apikey=<apikey>

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
dataAll the response is wrapped in side data
creditsDisplays the credits available in the account

Checking SMS Status -PULL

The URL for checking the credits in your account is in the following format:

https://www.mysmsapp.in/api/creditstatus?apikey=<apikey>

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
message ididMessage ID, comma separatedmessage id of messages sent in the last 3 days

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
service provider and location flagnumber infoFlag to query service provider and location data1 or 0

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
custom1Custom message id 1 if you provide one
custom2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message
customCustom message id if you provide one
senttimemessage sent time
dlrtimemessage delivered time
providerprovider of the mobile numer
locationRegistered location of the mobile number

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to check sms status is in the below format :

STATUSMESSAGE
A419Invalid Group ID/Campaign

Checking Group Status -PULL

The URL for checking group status is in the following format:

https://www.mysmsapp.in/api/push.json?method=sms.groupstatus&api_key=Ad9e5XXXXXXXXXXXXX&format=json&groupid=2191&numberinfo=1

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
group idgroupidCustom group ID by customer, comma separatedgroup id of campaign sent in the last 3 days

Optional Parameters

The optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformaOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
service provider and location flagnumberinfoFlag to query service provider and location data1 or 0

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to check group status is in the below format :

STATUSMESSAGE
A419Invalid Group ID/Campaign

Checking SMS Status -PUSH

The URL for pushing the status of an SMS is in the following format:

https://www.mysmsapp.in/api/push.json?method=sms&api_key=Ad9e5XXXXXXXXXXXXX&to=997XXXXXXX&sender=INFXXX&message=testing&format=json&custom=1&custom1=11&custom2=22&dlrurl=DLRURL

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Sender IDsenderSender ID assigned to your accountSender ID
Mobile numbertoMobile number to which the SMS is to be sent.The destination mobile number can be with or without 91. Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)
MessagemessageMessage to be sentMessage text which is URL encoded(1000 char for normal, 500 for unicode)
message idcustommessage id provided for Smsmessage id provided for Sms
delivery reports URLdlrurlThe URL to receive delivery reports. Spiffing custom is mandatory.delivery reports URL

Optional Parameters

Value within the dlrurl should always be url encoded

http://mysmsapp.in/dlr/trigger.php?sent={sent}&delivered={delivered}&custom={custom}&sid={sid}&status={status}&reference={reference}&custom1={custom1}&custom2={custom2}

Response as seen in DLR URL

2015-07-13 13:50:58 54.254.218.30
{“sent”:”2015-07-13 19:20:46″,”delivered”:”2015-07-13 19:20:57″,”custom”:”1″,”sid”:”1406368098-1″ ,”status”:”DELIVRD”,”reference”:”1″,”custom1″:”11″, “custom2″:”22″,”msgid”:”1″}

Custom Flags in DLRURL

We have few custom flags supported in DLR URL in order to get the additional values. In case one wants to build the URL in above format, the following flags can be used.

NameParameter
{custom} (alias-{reference}/{msgid})Message ID provided by user
{sent}Sent time in YYYY-MM-DD HH:MM:SS format
{delivered}Delivered time in YYYY-MM-DD HH:MM:SS format
{status}SMS status code
{custom1}Custom Flag 1 associated with the message provided by the user
{custom2}Custom Flag 2 associated with the message provided by the user
A405Api secret not found.
A406Request is not allowed from this ip
A407Header misconfigured
A408Api Signature not equal

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send an SMS is in the below format :

STATUSMESSAGE
A411Port number must be numeric
A415Invalid xml/Invalid Json
A416Invalid Message ID/Mobile
A417Invalid Message ID/Mobile
A418Invalid Group ID/Campaign
A419Invalid Group ID/Campaign
A430Invalid Group ID
A431Invalid Group ID
A432Campaign already completed/Campaign already cancelled
A433Schedule time already passed
A434Campaign within next 5 minutes cannot be modified/canceled.
A434Invalid schedule time. Minimum 5 min time gap is required.
E601Missing receipent
E603Missing message
E602Missing senderid
E604Senderid must be less than 14 chars
E605Invalid Sender or Sender not allowed
E606Invalid schedule time. Minimum 15 min time gap is required.
E606ABatch size should be greater or equal to 1000
E606BSchedule minute should be in multiples of 15. minimum 15 minute
E612Invalid Template Matched
E607SMS length is exceeding 1000 characters
E607AUnable to find gateway to sent sms.
E608No Valid mobile numbers found
E608AYour daily usage limit exceeded
E609An error occured while saving group details
E610Unable to write to temp files
E611Unable to process your request. try again
H601Insufficent credits. Total 1. Required 1 more credits.

SI Lookup

The URL for performing a lookup is in the following format:

https://www.mysmsapp.in/api/push.json? method=hlr&api_key=Ad9e5XXXXXXXXXXXXX&to=997XXXXXXX&format=json

NOTE: 1 credit will be deducted per mobile number

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Mobile numbertoMobile number along with country prfix to which the SMS is to be sent.Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)

Optional Parameters

The Optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
hlrEach number will be wrapped inside hlr
onnOriginal Network Name
ocnOriginal Country Name
ocpOriginal Country Prefix
rnnRoaming Network Name
rnpRoaming Network Prefix
rcnRoaming Country Name
rcpRoaming Country Prefix
pnnPorted Network Name
pnpPorted Network Prefix
pcnPorted Country Name
pcpPorted Country Prefix
MccmncMobile country code used in the combination of mobile network code to uniquely identify an operator
MobileMobile number
idExternal message ID
creditsAmount charged for the service

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to perform an SI Lookup is as follows :

STATUSMESSAGE
A440Invalid destination numbers

Creating A Txtly

URL to create a Txtly is as follows:

https://www.mysmsapp.in/api/push.json?method=txtly.create&api_key=Ad9e5XXXXXXXXXXXXX&url=https://www.google.co.in&format=json

NOTE: It is mandatory to either provide a url or attachment that has to be compressed to a short link

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Mobile numbertoMobile number along with country prfix to which the SMS is to be sent.Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)

Optional Parameters

The Optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON
tokentoken'http://msg.mn/heel' Here heel is the token. It is unique for each txtlyThis can customized word representing your brand/compnay. If not provided a random unique token is generated
Title of the TxtlytitleA significant title to your txtlyIf not provided, your txtly will not contain any title
Advanced Analytics Enable?advancedadvanced analytics gives an option to track who (Recipient mobile numbers) visited the page1- will enable advanced analytics/0(default) - will disable advanced analytics
Location Track?trackLocation Track gives the city and state details of URL visitor1- will enable location tracking/0(default) - will disable location tracking
Attachmentattachmedia file that requires to be compressed to a short link.Provide the media file in a CURL request

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
tokenReturns the unique token of that txtly
txtlycompressed url that is ready to use

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to create a Txtly are as follows :

STATUSMESSAGE
E500Please provide url to redirect
E501Txtly Already Exists. Please try another one.
E502Please attach a file
E503Invalid file format. Upload valid file.
E504File size exceed. Maxmium 50000 Kb.
E505File upload failed. Please try again.

Deleting A Txtly

URL to delete a Txtly is as follows:

https://www.mysmsapp.in/api/push.json? method=txtly&api_key=Ad9e5XXXXXXXXXXXXX&task=delete&format=json&id=123&app=1

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
tasktaskTask to be performed on txtlydelete
id of the txtlyidid of the txtly123
ApplicationappApplication reference1

Optional Parameters

The Optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.

Txtly Reports Extraction - PULL

URL to Pull logs for all txtly in your account

https://www.mysmsapp.in/api/push.json?method=txtly&api_key=Ad9e5XXXXXXXXXXXXX&app=1&format=xml

API Parameter Specifications

The API parameter specifications are described in the following sections.

Mandatory Parameters

The mandatory parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
URLURLURL of your SMS ServiceURL
MethodmethodPredefined methodsms
API/Working keyapikeyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panel
Mobile numbertoMobile number along with country prfix to which the SMS is to be sent.Also provide multiple numbers in comma separated format.Mobile number(GET-10numbers,POST-100numbers)

Optional Parameters

The Optional parameters in the HTTP API are tabulated below:

NameParameterDescriptionExpected Values
Response TypeformatOutput format should be as specified by this variableXML/PHP/JSON/JSONP. Default response will be in JSON

Example Responses

Sending An SMS Using XML API

To send an SMS using XML API, the following format is used:

https://www.mysmsapp.in/api/push.json? method=sms.xml&api_key=Ad9e5XXXXXXXXXXXXX&format=json&xml=<Your XML_data or XML_url>

SMS can be sent using the XML API by posting values to the preceding URL by the POST method or the GET method.

API URL Parameter Specifications

The API URL parameter specifications are described in the following sections.

API URL Parameters

ParameterDescriptionExpected ValuesType
URLURLURL of your SMS ServiceRequired
MethodPredefined methodsms.xmlRequired
API/Working keyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panelRequired
xmlYou can provide either urlencoded XML data directly Or url of the XML fileValid XML document or link of XML documentRequired
formatResponse format typeXML/PHP/JSON/JSONP. Default response will be in JSONOptional
callbackCallback function for JSONP response formatJavascript function name standardsOptional

XML Tag Parameters

Note: If message,sender and dlrurl is specified within both SMS tag and XML tag, the former overrides the later.

ParameterDescriptionExpected ValuesType
xml version="1.0" encoding="UTF-8"XML HeaderVersion and EncodingRequired
apiDocument RootDocument RootRequired
timeGlobal schedule timeEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PMOptional
unicodeTo specify that the message to be sent is in unicode format. Also can be used for automatic detection of unicode SMS.1/0/autoOptional
flashGlobal node for flash1/0Optional
senderSender ID assigned to your accountSender IDRequired
messageMessage to be sent. In case of any special characters in your message, enclose it within CDATA as in the exampleMessage textRequired
dlrurlThe URL to receive delivery reports.Spiffing reference id is mandatoryEX: http://www.example.com/dlr.phpOptional
campaignGlobal campaign name tagcampaign nameOptional
smsSMS Node(can repeat)SMS NodeRequired
toMobile number in sms nodeComma seperated 10 digit mobile numbersRequired
customMessage ID for smscomma seperated message ID'sOptional
custom1Custom reference 1 (comma separate) comma seperated custom 1 referencesOptional
custom2Custom reference 2 (comma separate)omma seperated custom 2 referencesOptional

Example Request

Sample Data

Sending to multiple numbers with different message

NOTE: In case of special characters in the content within any of the XML tags , enclose it within CDATA as in the example

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send an SMS is in the below format :

STATUSMESSAGE
A411Port number must be numeric
A415Invalid xml/Invalid Json
A416Invalid Message ID/Mobile
A417Invalid Message ID/Mobile
A418Invalid Group ID/Campaign
A419Invalid Group ID/Campaign
A430Invalid Group ID
A431Invalid Group ID
A432Campaign already completed/Campaign already cancelled
A433Schedule time already passed
A434Campaign within next 5 minutes cannot be modified/canceled.
A434Invalid schedule time. Minimum 5 min time gap is required.
E601Missing receipent
E603Missing message
E602Missing senderid
E604Senderid must be less than 14 chars
E605Invalid Sender or Sender not allowed
E606Invalid schedule time. Minimum 15 min time gap is required.
E606AInvalid schedule time. Minimum 15 min time gap is required.
E606ABatch size should be greater or equal to 1000
E606BSchedule minute should be in multiples of 15. minimum 15 minute
E612Invalid Template Matched
E607SMS length is exceeding 1000 characters
E607AUnable to find gateway to sent sms.
E608No Valid mobile numbers found
E608AYour daily usage limit exceeded
E609An error occured while saving group details
E610Unable to write to temp files
E611Unable to process your request. try again
H601Insufficent credits. Total 1. Required 1 more credits.

Sending An SMS Using JSON API

To send an SMS using JSON API, the following format is used:

https://www.mysmsapp.in/api/push.json? method=sms.json&api_key=Ad9e5XXXXXXXXXXXXX&format=xml&json=<Your JSON_data or JSON_url

SMS can be sent using the JSON API by posting values to the preceding URL by the POST method or the GET method.

API URL Parameter Specifications

The API URL parameter specifications are described in the following sections.

API URL Parameters

ParameterDescriptionExpected ValuesType
URLURLURL of your SMS ServiceRequired
MethodPredefined methodsms.xmlRequired
API/Working keyAPI/Working key generated from your SMS AccountAlphanumeric working key generated from web panelRequired
xmlYou can provide either urlencoded XML data directly Or url of the XML fileValid XML document or link of XML documentRequired
formatResponse format typeXML/PHP/JSON/JSONP. Default response will be in JSONOptional
callbackCallback function for JSONP response formatJavascript function name standardsOptional

JSON Tag Parameters

Note: If message,sender and dlrurl is specified within both SMS tag and JSON tag, the former overrides the later.

ParameterDescriptionExpected ValuesType
xml version="1.0" encoding="UTF-8"XML HeaderVersion and EncodingRequired
apiDocument RootDocument RootRequired
timeGlobal schedule timeEX Format: YYYY-MM-DD HH:MM:SS OR YYYY-MM-DD HH:MM AM/PMOptional
unicodeTo specify that the message to be sent is in unicode format. Also can be used for automatic detection of unicode SMS.1/0/autoOptional
flashGlobal node for flash1/0Optional
senderSender ID assigned to your accountSender IDRequired
messageMessage to be sent. In case of any special characters in your message, enclose it within CDATA as in the exampleMessage textRequired
dlrurlThe URL to receive delivery reports.Spiffing reference id is mandatoryEX: http://www.example.com/dlr.phpOptional
campaignGlobal campaign name tagcampaign nameOptional
smsSMS Node(can repeat)SMS NodeRequired
toMobile number in sms nodeComma seperated 10 digit mobile numbersRequired
customMessage ID for smscomma seperated message ID'sOptional
custom1Custom reference 1 (comma separate) comma seperated custom 1 referencesOptional
custom2Custom reference 2 (comma separate)omma seperated custom 2 referencesOptional

Example Request

Sample Data

Sending to multiple numbers with same message

NOTE: In case of special characters in the content within any of the XML tags , enclose it within CDATA as in the example

Example Responses

Response Data

statusIt indicates the success or failure of your request.
messageIt indicates the success or failure message.
group_idWebsite group id for your reference
dataAll the response is wrapped in side data
smsEach number will be wrapped inside sms
idWebsite message id for your reference
customidCustom message id if you provide one
customid1Custom message id 1 if you provide one
customid2Custom message id 2 if you provide one
mobileMobile number the sms will be sent
statusstatus of the message

API Error Codes

When certain parameters of the API URL are not entered correctly, you will receive a response from the URL stating the type of error. These error descriptions will help you to pin-point the erroneous parameter in the URL and rectify it.

The common error codes received while using the API to send an SMS is in the below format :

STATUSMESSAGE
A411Port number must be numeric
A415Invalid xml/Invalid Json
A416Invalid Message ID/Mobile
A417Invalid Message ID/Mobile
A418Invalid Group ID/Campaign
A419Invalid Group ID/Campaign
A430Invalid Group ID
A431Invalid Group ID
A432Campaign already completed/Campaign already cancelled
A433Schedule time already passed
A434Campaign within next 5 minutes cannot be modified/canceled.
A434Invalid schedule time. Minimum 5 min time gap is required.
E601Missing receipent
E603Missing message
E602Missing senderid
E604Senderid must be less than 14 chars
E605Invalid Sender or Sender not allowed
E606Invalid schedule time. Minimum 15 min time gap is required.
E606AInvalid schedule time. Minimum 15 min time gap is required.
E606ABatch size should be greater or equal to 1000
E606BSchedule minute should be in multiples of 15. minimum 15 minute
E612Invalid Template Matched
E607SMS length is exceeding 1000 characters
E607AUnable to find gateway to sent sms.
E608No Valid mobile numbers found
E608AYour daily usage limit exceeded
E609An error occured while saving group details
E610Unable to write to temp files
E611Unable to process your request. try again
H601Insufficent credits. Total 1. Required 1 more credits.

Developers Guide

Scroll to Top