Bulk SMS Mobile industry news

Http api RESPONSE URL
Our server returns the following response for each message submitted –
This is in url encoded form.

status=1&credit=1676&display_message=SENDSMS+FOR+123456789123%2CMSGID%3D47328ceb95cc4a

if we url decode this response this changes to:

status=1&credit=1676&display_message=SENDSMS FOR 123456789123,MSGID=47328ceb95cc4a

In this response MSGID is visible. This message id is to be used when user query for the message status.

Status - It can be 1 or 0 . 1 denotes account is live and message are being accepted. 0 denotes that account in not live , reason may be wrong userid / password / clientid or no message credits left
Credit – It means the number of credits left. Please contact us immediately once the number of credits go below 5000
Message Status URL

This is url that is used to check message status.

http://xxx.xxx.xx.xx:Port/deliv?login=xx&password=xx&clientid=xx&msgid=47328ceaae3e5a

In the response we get the following.

status=6&submitdate=20040304160554585&delivdate=20040304103500000&msgid=47328ceaae3e5a

Status table: Following is the meaning of status codes returned back in the URL.

STATUS CODES
101 message id is wrong
0 invalid account
1 InQueue
2 Message Expired
3 Processed
5 DestNotSuppoerted
6 Delivered
7 Undelivered

submitdate - the time when message was submitted to our server
Delivdate – is the time stamp when message is submitted. Here the point to note is that since the SMSCs are all across world, sometimes the time stamp may contain entry hours before or after the submit date. However the same is not because of delay but because of difference in the time zones of SMSC we are connecting to.

Please visit SMSwarehouse http api for details