Difference between revisions of "DLRPost"
(New page: == How to Get Message Delivery Confirmations Using HTTP-POST == You need to implement HTTP-POST handler that will listen to incoming HTTP-PUSH from our service. This will look similar to:...) |
(No difference)
|
Revision as of 00:51, 14 September 2011
How to Get Message Delivery Confirmations Using HTTP-POST
You need to implement HTTP-POST handler that will listen to incoming HTTP-PUSH from our service. This will look similar to:
name = your_username trackingid = MTID119946997360917165 status = DELIVRD recipient = 12088580767
For example, assuming that your application is at domain foo.com the call we make is
http://foo.com?name=YOUR_USER_NAME&mtid=MTID119946997360917165&status=SEE_BELOW&number=12088580767
Status options
• DELIVRD (terminal status)
• ERROR (terminal status)
• FAILED (terminal status)
• REJECTD (terminal status)
• SENT (still in progress - may have been delivered with no DLR)
• UNDELIV (Undeliverable - the message cannot be delivered, will keep trying)
• UNDETRM (Undetermined - keep trying)
• UNIDNTFY (terminal status)
• UNKNOWN (terminal status)
When you send a message (using Send_Plain, for example) you will receive MTID (message or tracking id). This is a unique number assigned to each message. You will need to store it. When you get incoming HTTP-PUSH, simply query your database to find matching tracking_id. When you find it, update status of message