1. Single Recipient Request: –
https://domainname/fe/api/v1/send?username=username&password=APIpassword&un
icode=true/false&from=sendercli&to=torecipient&text=message&dltContentId=DL
TtemplateID
2. Multiple Recipient Request: – (Up to 100 msisdn)
https://domainname/fe/api/v1/multiSend?username=username&password=APIpasswo
rd&unicode=true/false&from=sendercli&to=torecipient1, torecipient2,
torecipient3&text=message&dltContentId=DLTtemplateID
When the request is successful, the following response will be displayed.
{“transactionId”:205538399,”state”:”SUBMIT_ACCEPTED”,”statusCode”:200,”desc
ription”:”Message accepted successfully”,”pdu”:1}
We suggest you store the response text as it may be required to retrieve status / delivery report in
future using message id.
Other responses in case of an error:
Response Description Reason
“statusCode”:2051
“Sender [xxxxxx]
doesn’t exist”. When the API request contains nonregistered SENDER ID on User
Panel
“statusCode”:2070 Authentication failure Invalid Username/Password/Account expired
“statusCode”:2054
Invalid Msisdn
[xxxxxxxxx] [IN] When the MSISDN is not in 10– or 12–digits length (with IN country
code 91)
“statusCode”:6001 Insufficient Balance! Zero Credit
“statusCode”:7001 DLT_Content_ID not
found DLT Content ID missing in API request
7: Call Back API Format & Parameter Details for Real Time Delivery Report:
Client must provide call back API (GET) in below format to configure at the backend, real time
delivery reports shall be pushed through the API.
http://{clienturl path}?txid={transactionId}&to={recpient}&from={sender}&description={descrip
tion}&pdu={totalPdu}&text={message}&deliverystatus={status}&deliverydt={don
eDate}