Overview

Amazon is rolling out a series of Selling Partner API (SP‑API) retirements that will take effect between mid‑2025 and early‑2026. The deprecation schedule targets the old catalog hierarchy endpoint, twelve XML‑based feed formats, and the V2 settlement report types. Sellers and developers who still rely on these interfaces must begin migration planning now, or risk workflow failures once the cut‑off dates pass.

Key Points

• Catalog hierarchy endpoint removal — The listCatalogCategories call will cease operation on March 31 2026, requiring a switch to the 2022‑04‑01 Catalog Items API.
• Twelve legacy feed formats sunset — XML and flat‑file feeds such as POST_PRODUCT_DATA and POST_INVENTORY_AVAILABILITY_DATA will be disabled on June 30 2025.
• V2 settlement reports deprecated — Both flat‑file and XML settlement reports will stop being generated after March 25 2026.
• JSON‑only mandate — All new integrations must use the JSON‑based Listings Items API and the JSON_LISTINGS_FEED format.
• Tight testing windows — Enterprise sellers with complex pipelines have less than a year to validate new endpoints before the June 2025 feed deadline.
• Financial reporting impact — Accounting systems that ingest settlement data must transition to the newer Reports API to keep tax and profitability calculations accurate.

What's Changing

1. Catalog Items API migration —
   What happens: Calls to the legacy listCatalogCategories endpoint will return a 404 error after March 31 2026.
   Example: A third‑party listing tool that previously fetched category trees via the old endpoint will need to replace its request URL with /catalog/2022-04-01/items and adjust the payload to match the new JSON schema.

2. Feed format overhaul —
   What happens: The twelve XML/flat‑file feeds are permanently removed on June 30 2025, and Amazon will reject any submissions using those types. : A seller who uploads inventory using must rebuild the upload process to generate a payload, which includes attribute‑level validation flags such as .