Notifications API

Learn how to subscribe to notifications that are relevant to a selling partner's business.

You use the Notifications API to subscribe to notifications that are relevant to your selling business. You can create a destination to receive notifications, subscribe to notifications, delete notification subscriptions, and more. Instead of polling for information, your application can receive information directly from Amazon when an event generates a notification to which you are subscribed.

You can subscribe to notifications on behalf of sellers or vendors. To determine whether you can subscribe to a notification type on behalf of sellers only, vendors only, or both, go to notificationType. We allow multiple subscriptions with different payload versions per application, notification type and party (seller/vendor). For supported payload versions of different notification types, refer to notificationType.

🚧

Build a backup mechanism

As a best practice, we recommend that you have a means to retrieve needed information in the event of an unexpected outage or delay in notification delivery.

Current versionLegacy versionsAvailable to sellersAvailable to vendors
v1 (Reference | Model)NoneYesYes
Release notes

To learn more about the terms that are used on this page, refer to Terminology.

Notification workflows

There are two separate workflows for receiving notifications. The workflow you use depends on the notification type that you want to receive.

Amazon EventBridge workflow

The following diagram provides an overview of the Amazon EventBridge workflow steps to subscribe to listings notifications.

Workflow chart of interactions between the user and Selling Partner API to subscribe to listings notifications.

Use this workflow to receive the following notification types:

Amazon Simple Queue Service workflow

Use this workflow to receive the following notification types:

  • ACCOUNT_STATUS_CHANGED: Sent when the account status changes for the developers subscribed selling partner/marketplace pairs. A notification is published when the selling partner's account status changes between NORMAL, AT_RISK, and DEACTIVATED.

  • ANY_OFFER_CHANGED: Sent when there is a change to any of the top 20 offers, by condition (new or used), or if the external price (the price from other retailers) changes for an item listed by the seller.

  • B2B_ANY_OFFER_CHANGED: Sent when there is a change in any of the top 20 B2B offers, in the form of any price change (either single unit or quantity discount tier prices) for an item listed by the seller.

  • DETAIL_PAGE_TRAFFIC_EVENT: Sent at the beginning of every hour. This notification shares traffic data at an ASIN level and includes data for the previous hour, as well as any delayed data from up to 24 hours earlier. Each notification can include multiple ASINs, and a selling partner can expect to receive multiple notifications every hour.

  • FBA_INVENTORY_AVAILABILITY_CHANGES: Sent when there is a change in the Fulfillment By Amazon (FBA) inventory quantities. This notification includes a snapshot of the FBA inventory in all eligible marketplaces in a particular region.

  • FBA_OUTBOUND_SHIPMENT_STATUS: Sent when we create or cancel a Fulfillment by Amazon shipment for a seller.

  • FEE_PROMOTION: Sent when a promotion becomes active.

  • FEED_PROCESSING_FINISHED: Sent when any feed submitted using the Selling Partner API for Feeds reaches a feed processing status of DONE, CANCELLED, or FATAL.

  • FULFILLMENT_ORDER_STATUS: Sent when there is a change in the status of a Multi-Channel Fulfillment order.

  • ITEM_INVENTORY_EVENT_CHANGE: Sent at the beginning of every hour. This notification shares inventory data at an ASIN level, and includes data for the previous hour, as well as any delayed data from up to 24 hours earlier. Each notification can include multiple ASINs, and a selling partner can expect to receive multiple notifications every hour.

  • ITEM_SALES_EVENT_CHANGE: Sent at the beginning of every hour. This notification shares sales data at an ASIN level and includes data for the previous hour, as well as any delayed data from up to 24 hours earlier. Each notification can include multiple ASINs, and a selling partner can expect to receive multiple notifications every hour.

  • ORDER_CHANGE: Sent when there is an important change in the order. Important changes include order status changes and buyer requested cancelations. Note that marketplaceIds is not a supported filter for ORDER_CHANGE. If you want to include marketplaceIds, you must use ANY_OFFER_CHANGED.

  • PRICING_HEALTH: Sent when a seller offer is ineligible to be the Featured Offer because of an uncompetitive price.

  • REPORT_PROCESSING_FINISHED: Sent when any report that you have requested using the Selling Partner API for Reports reaches a report processing status of DONE, CANCELLED, or FATAL.

  • TRANSACTION_UPDATE: Sent whenever there is a new transaction posted to the seller's account.

Uses cases

The following use case examples are available for the Notifications API:

Roles

createDestination
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)None (grantless)
createSubscription
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)The role that is associated with the notification type
deleteDestination
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)None (grantless)
deleteSubscriptionById
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)None (grantless)
getDestination
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)None (grantless)
getDestinations
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)None (grantless)
getSubscription
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)The role that is associated with the notification type
getSubscriptionById
AttributeValue
RegionsNA, EU, FE
Required roles (need at least one)None (grantless)