Difference between revisions of "DLRPost"

From SMS Wiki
Jump to: navigation, search
 
(2 intermediate revisions by one user not shown)
Line 10: Line 10:
 
For example, assuming that your application is at domain foo.com the call we make is
 
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
+
http://foo.com?name=YOUR_USER_NAME&trackingid=MTID119946997360917165&status=SEE_BELOW&recipient=12088580767
  
 +
Note: https is also supported.
  
 
[[DLR_STATUS| List of Statuses ]]  
 
[[DLR_STATUS| List of Statuses ]]  
Line 19: Line 20:
  
 
----
 
----
[[APIs | back]]
+
[[DLRIntro | back]]

Latest revision as of 14:35, 13 January 2015

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&trackingid=MTID119946997360917165&status=SEE_BELOW&recipient=12088580767

Note: https is also supported.

List of Statuses

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



back