Added to Amalert: Jan 30, 2026
Amazon's New Customer Feedback API Brings Voice of the Customer Data to Sellers Programmatically
Amazon released the Customer Feedback API (v2024-06-01) that returns VoC metrics such as negative‑review rate and return‑reason codes per ASIN or browse node. The API mirrors the Seller Central dashboard and enforces standard SP‑API throttling, enabling nightly pulls for thousands of products.
Overview
Amazon has launched a new Customer Feedback API (version 2024‑06‑01) as part of the Selling Partner API suite. The endpoint delivers the same review‑ and return‑related insights that appear in the Voice of the Customer (VoC) dashboard, but in a structured, machine‑readable format. Sellers and developers can now pull these signals automatically, enabling continuous product‑health monitoring across large inventories.
Key Points
- Programmatic access to reviews and returns — Sellers receive aggregated sentiment and return‑reason data without manually opening each product’s VoC page.
- ASIN‑level detail — Feedback is broken out per individual ASIN, allowing pinpoint identification of problem items such as a specific model of kitchen gadget that generates a spike in “broken on arrival” complaints.
- Category‑wide aggregation — The API also groups insights by browse node, so a seller can see that the entire “Outdoor Gear > Camping Tents” segment is experiencing higher-than‑average negative feedback.
- Parity with Seller Central — All metrics shown in the VoC dashboard (e.g., negative‑review rate, return‑reason frequency) are reproduced exactly, ensuring no loss of information when moving to an automated workflow.
- Standard SP‑API security — Access follows the existing SP‑API authentication flow, meaning developers can reuse existing credentials and token‑refresh logic.
- Rate‑limit awareness — The service enforces throttling, prompting large sellers to design efficient polling and caching strategies to stay within quota.
How the Customer Feedback API Works
-
Authenticate via SP‑API — A developer registers the application, obtains a refresh token, and exchanges it for an access token.
Example: An aggregator managing 12,000 ASINs uses its existing SP‑API client library to request a token that is valid for one hour before refreshing automatically. -
Request feedback for a target scope — The call can specify a single ASIN, a list of ASINs, or an entire browse node. : To monitor a new line of Bluetooth headphones, the seller sends a request with the ASINs and ; the response returns review sentiment scores and top return reasons for each.
Analysis & Recommendations
Why This Matters
Sellers can now automate detection of issues like a 20% rise in negative reviews for a specific ASIN within minutes, reducing manual spreadsheet work and allowing rapid listing or ad‑spend adjustments. The ability to query at ASIN and browse‑node level supports large catalogs (e.g., 5,000+ items) and improves early‑warning capabilities.
Key Takeaways
- The API version is 2024-06-01 and delivers the same metrics as the Voice of the Customer dashboard.
- Feedback can be requested per ASIN, list of ASINs, or entire browse node, enabling granular and category‑wide insights.
- Standard SP‑API authentication and token refresh are used; rate limits require caching (e.g., 30‑minute interval) to stay within quota.
- Threshold‑based alerts (e.g., negative‑review rate >15%) can trigger automated tickets or inventory adjustments.
Recommended Actions
- →Register the Customer Feedback API in the SP‑API Developer Console > Applications and obtain the required scopes.
- →Implement token exchange using the /authorization/v1/token endpoint and schedule a nightly job that calls the getFeedback endpoint for your ASIN list.
- →Set up caching (e.g., 30‑minute store) and alert logic in Seller Central > Performance > Notifications for negative‑review rates above your chosen ...
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!