Deprecation Notice: Suppressed listings reports and FBA Inventory reports
On June 15 2022 Amazon retired the _GET_MERCHANT_LISTINGS_DEFECTDATA_ and _LISTINGS_DEFECT_REPORTXL_ endpoints, returning HTTP 404. The replacement endpoint _GET_MERCHANTS_LISTINGS_FYPREPORT_ now delivers suppressed listings and FBA inventory defects in a single report. Sellers must update their MWS/SP‑API calls and run a 30‑day parallel test to ensure data parity.
Overview
On June 15 2022 Amazon discontinued the _GET_MERCHANT_LISTINGS_DEFECTDATA and _LISTINGS_DEFECT_REPORTXL endpoints across both MWS and the SP‑API. Those calls previously supplied “suppressed listings” and “FBA inventory” defect files that many sellers used to monitor compliance. Amazon now provides a single replacement endpoint— _GET_MERCHANTS_LISTINGS_FYPREPORT—so sellers must revise any automated processes before the legacy URLs stop delivering data.
Key Points
- Deprecation effective date — After June 15 2022 the two old defect‑data endpoints return HTTP 404 and no longer produce reports.
- Unified replacement — _GET_MERCHANTS_LISTINGS_FYPREPORT covers all defect categories and is live in both MWS and SP‑API.
- Data coverage — The new report still includes suppressed SKUs, FBA inventory mismatches, and other compliance flags formerly split across two files.
- Impact on integrations — Scripts, third‑party platforms, or custom dashboards that still reference the retired endpoints will encounter errors and lose visibility.
- Parallel testing recommendation — Amazon advises running the new report alongside existing pipelines for at least 30 days to confirm parity.
- Documentation shift — All current Amazon developer references now point exclusively to the FYP report for defect information.
How the _GET_MERCHANTS_LISTINGS_FYPREPORT Works
-
Authenticate the request — Use your existing MWS or SP‑API credentials (access key, secret key, seller ID) to sign a GET call.
- Example: A Node.js script builds a signed URL with
AWS4-HMAC-SHA256and appendsSellerId=A1B2C3D4E5F6G7to the query string.
- Example: A Node.js script builds a signed URL with
-
Define report parameters — Set
ReportType=_GET_MERCHANTS_LISTINGS_FYPREPORT_and optionally includeStartDate/EndDatefilters.
Analysis & Recommendations
Why This Matters
The legacy calls stopped delivering data after June 15 2022, so any automation still using them will miss suppressed SKUs and inventory mismatches, risking health‑score penalties. The new unified report consolidates both defect types, but mismatched column names and report type strings can cause errors if not updated.
Key Takeaways
- After June 15 2022 the old endpoints return HTTP 404 and no longer produce reports.
- The unified replacement is ReportType=_GET_MERCHANTS_LISTINGS_FYPREPORT_, covering suppressed listings and FBA inventory mismatches.
- Amazon advises running the new report alongside legacy pipelines for at least 30 days to confirm parity.
- Consolidating the two reports cuts API traffic by roughly 50% and eliminates post‑download data stitching.
Recommended Actions
- →Update all integration code to use ReportType=_GET_MERCHANTS_LISTINGS_FYPREPORT_ (e.g., replace _GET_MERCHANT_LISTINGS_DEFECTDATA_ in Java/Node scr...
- →Initiate a 30‑day parallel test: submit the new FYP report while still pulling legacy data, then compare row counts in Seller Central > Reports.
- →Monitor API logs for errors like ReportNotReady or InvalidReportType and correct request parameters (e.g., ensure trailing underscore in report type).
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!