DLRPost - Revision history

Bzurkovic at 21:35, 13 January 2015

2015-01-13T21:35:20Z

Bzurkovic at 21:20, 1 May 2014

2014-05-01T21:20:34Z

Bzurkovic at 23:42, 14 September 2011

2011-09-14T23:42:34Z

Bzurkovic at 23:42, 14 September 2011

2011-09-14T23:42:00Z

Bzurkovic: 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:...

2011-09-14T07:51:52Z

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:...

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:

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

← Older revision		Revision as of 21:35, 13 January 2015
Line 12:		Line 12:
	http://foo.com?name=YOUR_USER_NAME&trackingid=MTID119946997360917165&status=SEE_BELOW&recipient=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 ]]

← Older revision		Revision as of 21:20, 1 May 2014
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

← Older revision		Revision as of 23:42, 14 September 2011
Line 19:		Line 19:

	----		----
−	[[~~APIs~~ \| back]]	+	[[DLRIntro \| back]]

@@ Line 12: / Line 12: @@
 http://foo.com?name=YOUR_USER_NAME&mtid=MTID119946997360917165&status=SEE_BELOW&number=12088580767
-•	DELIVRD   (terminal status)
+[[DLR_STATUS| List of Statuses ]]
-•	ERROR     (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
-•	REJECTD   (terminal status)
+----
+[[APIs | back]]
-•	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