Post back Delivery Receipt API to your server

We can post back to you the Delivery Reports via an API as they come in instead of you having to query us to check when a message has been updated.
(preferred)

The arguments are:
MSG_ID (message ID that is given to you when you post to us via the API)
DLRSTATUS ( either DELIVRD / ACCEPTD / EXPIRED / UNDELIV etc..)
DLR_ERR (always returns 0 for DELIVRD; returns possible error codes for ACCEPTD state or UNDELIV etc – is a 3 digit integer. Full list below)
DONEDATE (is a 10 digit integer in the format of yymmddhhmm – year month day hour minute)

Please note that these might be delayed as these are low priority compared to sending messages, however the DONEDATE will have the correct time the message was sent.

e.g. if a phone is turned off, you will receive a DLR status with 107 Absent subscriber with the DONEDATE at the initial attempt to send the message, then when the phone is turned back on, you will receive another DLR report with the same message id with an updated status of DELIVRD, and the DONEDATE of the time the message was delivered when the phone was turned on.

So e.g. a url would be www.yourserver.com.au/receivedlr.php?msgid=MSG_ID
&dlrstatus=DLRSTATUS&dlr_err=DLR_ERR&donedate=DONEDATE

List of possible error codes for ACCEPTD and UNDELIV state:
0 Unknown subscriber
10 Network time-out
100 Facility not supported
101 Unknown subscriber
102 Facility not provided
103 Call barred
104 Operation barred
105 SC congestion
106 Facility not supported
107 Absent subscriber
108 Delivery fail
109 Sc congestion
110 Protocol error
111 MS not equipped
112 Unknown SC
113 SC congestion
114 Illegal MS
115 MS not a subscriber
116 Error in MS
117 SMS lower layer not provisioned
118 System fail
512 Expired
513 Rejected
515 No route to destination
608 System error
610 Invalid source address
611 Invalid destination address
625 Unknown destination

Please contact us to set this up on your account.