Overview

Amazon has announced final removal dates for several outdated Selling Partner API (SP‑API) components, with the earliest cutoff on 26 February 2025. The deprecations affect notification payloads, catalog‑lookup endpoints, and a suite of XML‑based feed types, meaning any integration that still calls these legacy services will start returning errors once the deadlines pass. Sellers must verify that their custom code or third‑party tools have migrated to the newer JSON‑based alternatives to avoid disruptions in listing management, inventory updates, and pricing adjustments.

Key Points

• Listing‑issue notification v1.0 — The first deadline arrives on 26 Feb 2025; any system still parsing the old LISTING_ITEM_ISSUES_CHANGE payload will miss critical alerts about listing problems.
• Catalog Items API v0 — Both listCatalogItems and getCatalogItem calls will stop working after 31 Mar 2025, forcing a switch to the v2022‑04‑01 version for product data retrieval.
• Twelve legacy feed types — XML and flat‑file feeds such as POST_PRODUCT_DATA and POST_FLAT_FILE_PRICEANDQUANTITYONLY_UPDATE_DATA are retired on 30 Jun 2025, with JSON‑based feed options recommended as replacements.
• Reduced throttling already in effect — Since 31 Dec 2024, Amazon has lowered request limits on the deprecated Catalog Items API, causing slower response times for any integration that has not yet upgraded.
• Vendor accountability — Third‑party software providers are expected to complete their migration plans before the respective cutoffs; sellers should obtain concrete timelines to confirm compliance.

What's Changing

1. Notification payload upgrade — Systems that listen for LISTING_ITEM_ISSUES_CHANGE must adopt the new JSON schema; for example, a seller’s alert service that previously extracted the “issueCode” field from XML will need to map the same data from the revised “issueDetails” object.
2. Catalog API version shift — Calls to listCatalogItems must be redirected to the v2022‑04‑01 endpoint, which supports pagination tokens and richer attribute filters; a typical inventory‑sync script that queried 10,000 SKUs in batches of 500 will now receive up to 1,000 items per request, reducing overall API calls.