• Navigation
  • Welcome
  • Getting Started
  • API Methods
  • API Notifications
  • API Usage Limits
  • Sample Code
  • Recent changes
  • Help

API Notifications

From Developer's API

Revision as of 20:43, 30 January 2009 (view source) Darrinm (Talk | contribs) ← Older edit		Revision as of 20:44, 30 January 2009 (view source) Darrinm (Talk | contribs) Newer edit →
Line 22:		Line 22:
	* Test Notifications		* Test Notifications
	* New Orders		* New Orders
−
	===Notification URL===		===Notification URL===

---

Revision as of 20:44, 30 January 2009

The notification system sends messages via http of new events¹ that have taken place on your merchant account. A message is created in XML and sent to a user configurable URL. The notification data can then be used to call the API and retrieve specific information, such as the details of a new order.

The API notifications are sent reliably, meaning that the message will be retried until a http response 200/OK is received from your notification url. Please note that the time between each attempt will be doubled, for example, first attempt immediately, second attempt at 1 minute, third attempt at 2 minutes, fourth attempt at 4 minutes etc.

Contents 1 API Notifications Overview 1.1 Diagram Explained 2 Notification URL 3 Test Notifications 4 New Orders

API Notifications Overview

The following diagram shows the typical flow of data when the API sends a new event notification.

http://www.mcssl.com/developer/images/process.jpg

Diagram Explained

1. When a new event¹ is generated in your merchant account a notification token is prepared and sent over https to your notification url
2. The notification request sent from the API contains XML in the request body and holds the event type and token within its nodes
3. Parse the event type and token values from the XML then call the API wrapper method corresponding to the event type to retrieve the detailed information
4. The API wrapper will prepare the request to the API and send the request over https
5. The API will parse out the merchant id, merchant key and token value from the request and prepare the requested data.
6. The API will send the prepared data back over https to the API wrapper
7. The API wrapper receives the requested data back from the API as XML
8. The notification listener receives the XML data from the API wrapper where it can verify the success attribute of the response node
9. Add functionality to support your business processes. for example you can parse the ShippingInfo node and prepare shipping labels.

¹ Currently the following events support API notification:

• Test Notifications
• New Orders

Notification URL

Information for this section is coming soon.

Test Notifications

A Test Notification is sent when a you call the Test Notification API Method. Use this feature to verify that your Notification Listener is functional.

The data contained in a Test Notification is as follows:

<Test>Test notification queued at 2008-12-03 14:26:30</Test>

New Orders

New Order Notification is sent when a new order has been placed for your merchant account.

The data contained in a New Order Notification is as follows:

<NewOrder><Token>{Token Value}</Token></NewOrder>