Amazon Notification API
Amazon Notification API is the API page through which push notifications from Amazon arrive in Business Central, for example about new or canceled orders. It has no user interface: it is called by a relay that passes Amazon's notifications on to your Business Central.
Push notifications are a supplement. Without them, the order import fetches orders and cancellations at fixed times; nothing else needs to be set up for that.
Setup
ALTENBRAND support sets up push notifications for your company. The connector itself creates neither destinations nor subscriptions at Amazon and does not call Amazon's Notifications API: at Amazon, a destination belongs to the whole application and thus to all customers, not to a single tenant.
Your part: in the Amazon Settings, enter the Notification API Key that you agreed on with support. Every notification must carry it. The key applies to all companies in the environment.
Endpoint
https://api.businesscentral.dynamics.com/v2.0/<Tenant>/<Environment>/api/altenbrand/amazoncloud/v1.0/companies(<Company ID>)/amazonNotifications
Only POST is accepted. The page rejects modifications and deletions.
Fields
| Field | Description |
|---|---|
| notificationType | Type of the notification, e.g. ORDER_CHANGE. The type stated in the payload is recorded. |
| notificationPayload | The notification from Amazon as JSON text. |
| apiKey | The Notification API Key. It is checked but not stored. |
| id | ID of the entry in the notification log (read-only). |
| status | Result of the processing: Processed, Failed, or Ignored if the notification requires nothing of the connector, for example because the same notification has already arrived once (read-only). |
| processedAt | Time of processing (read-only). |
The response to the POST returns apiKey and notificationPayload empty. It contains no error text: the error text can name the buyer and is only shown in the Amazon Notification Log in Business Central. For the relay, status Failed is enough.
Processing
- First, the page checks the key. If the key is missing, if none is stored in Business Central, or if it does not match, the call ends with an error: nothing is processed, nothing is stored, and Amazon is not called.
- Then it checks whether the notification has already arrived once: Amazon can deliver the same notification more than once. If its Notification ID is already in the Amazon Notification Log, the page does not process it again; the new entry gets the status Ignored with the reason that Amazon delivered it again.
- After that, it processes the notification in a separate error scope. If the processing fails, whatever it started is rolled back.
- Finally, it writes an entry to the Amazon Notification Log: type, Notification ID, depending on the type the Amazon Order ID, SKU and ASIN, and the result – Processed, Failed with the reason for the error, or Ignored with the reason if the notification required nothing. Only a failed entry keeps the payload, so that it can be processed again with Reprocess.
| Notification | Processing |
|---|---|
ORDER_CHANGE |
Status Unshipped: import of an order you ship yourself. Shipped: import of an FBA order. Canceled: cancellation via the hub's order cancellations. The same rules apply as for the order import. |
FEED_PROCESSING_FINISHED |
Evaluation of the feed in the Amazon Feed Tracker. |
LISTINGS_ITEM_STATUS_CHANGE |
Listing status of the Amazon item with this SKU, only on the marketplace of the notification (see below). |
ANY_OFFER_CHANGED, B2B_ANY_OFFER_CHANGED |
Market and BuyBox data; the lowest price of other sellers goes to the hub as the competitor price (see Prices and Offers). |
REPORT_PROCESSING_FINISHED |
only a log entry (Processed) |
| other types, such as inventory changes | are not processed: Ignored with the reason that the connector does not process notifications of this type |
Listing Status Changes
A LISTINGS_ITEM_STATUS_CHANGE notification states the seller, marketplace, SKU, ASIN and the list of statuses that Amazon currently gives the offer. The connector derives one status from it: BUYABLE if it appears anywhere in the list, otherwise the first entry; a missing or empty list counts as NOT_PUBLISHED – the listing exists but is neither buyable nor discoverable. It applies this status by the same rules as Refresh Listing Status on the Amazon Item Card:
| Status at Amazon | Listing Status |
|---|---|
| BUYABLE or DISCOVERABLE | Active |
| SUPPRESSED | Suppressed |
| INCOMPLETE | Incomplete |
| DELETED or BLOCKED | Blocked |
| NOT_PUBLISHED and unknown statuses | Inactive |
A listing closed with Close Listing stays Closed unless Amazon reports it as buyable (BUYABLE): then the closing did not take effect, and it becomes Active. If a change from Close Listing or Reactivate Listing is still waiting for its feed, the status stays until the feed has been processed. Only the Amazon item with this SKU on the marketplace of the notification is changed – the same SKU in other countries and in other sales channels stays as it is. If the Amazon item has no SKU of its own, the connector finds it via the item number. It copies the ASIN from the notification to the Amazon item; waiting entries of the item in the Amazon ASIN Search Queue are then set to Ignored.
Notifications from another seller (the Seller ID is not the Merchant ID in the Amazon Settings), notifications for a marketplace for which there is no marketplace participation (see Amazon Marketplace Participations), and notifications without a SKU are skipped. They change nothing; in the log they appear as Ignored, with the reason in Error Message.
Tips
Notifications supplement the order import
Keep the ORDERS job running even with push notifications. On a notification, the connector does not retrieve an order from Amazon again if the hub already knows it.
Changing the key
Only change the Notification API Key together with ALTENBRAND support. Until the relay uses the new key, the page rejects every notification.