Deprecation of _GET_MERCHANT_LISTINGS_DEFECT_DATA_ and _LISTINGS_DEFECT_REPORT_XL_
On 15 June 2022 Amazon retired the GET_MERCHANT_LISTINGS_DEFECT_DATA and LISTINGS_DEFECT_REPORT_XL endpoints. Sellers must now call GET_MERCHANTS_LISTINGS_FYPREPORT, which returns JSON and uses a nextToken for pagination. The deprecation followed a six‑month notice and any legacy calls now return errors.
Overview
On June 15 2022 Amazon discontinued two legacy defect‑reporting endpoints—GET_MERCHANT_LISTINGS_DEFECT_DATA and LISTINGS_DEFECT_REPORT_XL—across both MWS and the Selling Partner API. Sellers who depend on these feeds to monitor listing quality must now adopt the newer GET_MERCHANTS_LISTINGS_FYPREPORT endpoint. The shift impacts any automated script, third‑party service, or manual routine that extracts defect information for compliance, performance tracking, or inventory decisions.
Key Points
- Deprecation effective date — From 15 June 2022 the former endpoints stopped delivering data and any request to them returns an error response.
- New supported endpoint —
GET_MERCHANTS_LISTINGS_FYPREPORTis the sole API that provides defect details in both MWS and SP‑API environments. - Data parity — Core defect categories such as missing images, pricing mismatches, and policy violations remain available, but the payload is now JSON‑structured to match other SP‑API resources.
- Migration timeline — Amazon gave sellers a six‑month notice; no additional extensions will be offered.
- Third‑party tool impact — Software platforms still calling the retired endpoints will show gaps in defect data and may trigger compliance alerts until they release updates.
- Sandbox testing advised — Amazon recommends validating the new report in a sandbox environment before switching production traffic to avoid throttling or schema‑related errors.
How the New Report Works
- Submit request — The seller issues a
GET_MERCHANTS_LISTINGS_FYPREPORTcall, providing the marketplace identifier and, optionally, a start‑ and end‑date. Example: A retailer requests defects for the US marketplace covering 1 July 2022 through 31 July 2022. - Authenticate — The call must carry a valid SP‑API access token (or an MWS signature for legacy users) that corresponds to the seller’s developer account.
Analysis & Recommendations
Why This Matters
Defect data drives listing health, repricing and compliance alerts. After 15 June 2022 calls to the old CSV feeds fail, risking missed policy violations and potential penalties. The new JSON report restores visibility but requires code changes and throttling safeguards.
Key Takeaways
- Deprecation took effect on 15 June 2022; all GET_MERCHANT_LISTINGS_DEFECT_DATA requests now return errors.
- The replacement endpoint is GET_MERCHANTS_LISTINGS_FYPREPORT and delivers JSON with fields like defectType, severity, and listingUrl.
- When results exceed 1,000 records the response includes a nextToken for pagination.
- Amazon gave a six‑month migration window and will not extend it.
Recommended Actions
- →Update every script or integration URL to https://sellingpartnerapi-na.amazon.com/listings/2022-03-01/fypReport via Seller Central > Developer Sett...
- →Replace CSV parsing with JSON deserialization (e.g., json.loads in Python) and map fields defectType, severity, listingUrl.
- →Add a pagination loop that checks for nextToken and implements exponential backoff for ThrottlingException.
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!