New: Introducing App Integrations API v2024-04-01 for Seller Notifications
Amazon launched the App Integrations API (v2024‑04-01) on April 1 2024, enabling developers to POST real‑time alerts to a seller’s Appstore banner via /notifications/v2024-04-01/notifications. The API supports customizable payloads (title, message, severity, actionUrl) and DELETE calls to remove resolved alerts.
Overview
Amazon introduced the App Integrations API (version 2024‑04‑01) to let third‑party developers create and control seller‑focused alerts inside the Selling Partner Appstore banner on Seller Central. The service pushes messages in real time, covering topics such as inventory shortages, policy breaches, or performance warnings. Sellers benefit because instant, in‑app notifications can speed up corrective actions, lower support inquiries, and improve overall account health.
Key Points
- Create alerts — A POST call lets a developer generate a banner message for a designated seller, for example “Stock for SKU 12345 has fallen below the safety stock level.”
- Immediate display — Once the request succeeds, the notification appears instantly on the seller’s Appstore banner, visible the next time they log into Seller Central.
- Remove alerts — A DELETE request erases a notification that is no longer relevant, preventing the banner from becoming cluttered; e.g., deleting a “Missing compliance document” notice after the seller uploads the file.
- Unified authentication — The API uses the same Login with Amazon (LWA) access‑token flow and seller refresh token that power all other Selling Partner APIs.
- Throttling rules — Calls are subject to Amazon’s global rate‑limit policies, so developers must implement retry logic for occasional 429 (Too Many Requests) responses.
- Customizable payload — The request body can include a title, body text, severity level (info, warning, critical), and an optional action URL that routes the seller directly to the relevant Seller Central page.
How the App Integrations API Works
- Obtain authorization — The developer first exchanges LWA client credentials for an access token, then swaps the seller’s refresh token for a scoped token that permits posting notifications. Example: An inventory‑management SaaS authenticates, receives a token, and is now authorized to send alerts on behalf of a seller.
- Submit a notification — A POST request to carries JSON fields such as , , , , and . : The SaaS posts and receives a unique in the response.
Analysis & Recommendations
Why This Matters
Instant banner alerts let sellers react to low stock, policy breaches, or performance warnings without leaving Seller Central, reducing support tickets and improving account health. The ability to delete resolved alerts keeps the banner uncluttered, and the unified LWA authentication simplifies integration for existing SP‑APIs.
Key Takeaways
- Version 2024‑04-01 adds POST and DELETE endpoints at /notifications/v2024-04-01/notifications.
- Payload can include title, message, severity (info, warning, critical) and an optional actionUrl.
- API uses the same Login with Amazon (LWA) access‑token flow and seller refresh token as other SP‑APIs.
- Throttling follows Amazon’s global rate‑limit; 429 responses require retry after the Retry‑After header.
Recommended Actions
- →Authorize the third‑party app in Seller Central: Settings > User Permissions > Appstore Integrations, then grant the required scopes.
- →Implement POST calls with required fields (sellerId, title, message, severity) to push alerts, and DELETE calls using the returned notificationId t...
- →Add retry logic for 429 responses using the Retry‑After header to stay within global rate limits.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!