Amazon SP-API Deprecation Wave: Key Deadlines for Catalog, Feed, and Settlement Report Migrations
Amazon will retire the legacy catalog hierarchy endpoint (listCatalogCategories) on March 31 2026, disable twelve XML/flat‑file feed types on June 30 2025, and stop V2 settlement reports after March 25 2026. Sellers must switch to the 2022‑04‑01 Catalog Items API, use JSON_LISTINGS_FEED, and request reports via the new Reports API.
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
listCatalogCategoriescall 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_DATAandPOST_INVENTORY_AVAILABILITY_DATAwill 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_FEEDformat. - 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
-
Catalog Items API migration —
What happens: Calls to the legacylistCatalogCategoriesendpoint 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/itemsand adjust the payload to match the new JSON schema. -
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 .
Analysis & Recommendations
Why This Matters
The deprecations affect every integration that pulls categories, uploads product data, or downloads settlement files. Missing the June 2025 feed deadline or the March 2026 report cut‑off will cause 404 or 403 errors, halting listings and financial reconciliation, which can directly impact sales and accounting accuracy.
Key Takeaways
- listCatalogCategories endpoint will return 404 after March 31 2026; migrate to /catalog/2022-04-01/items.
- Twelve XML/flat‑file feeds (e.g., POST_PRODUCT_DATA) are disabled on June 30 2025; replace with JSON_LISTINGS_FEED.
- V2 settlement reports cease after March 25 2026; use the Reports API (GET /reports/2022-01-01/reports) for JSON output.
- New OAuth scopes required: sellingpartnerapi::catalog, sellingpartnerapi::reports, and sellingpartnerapi::feeds.
Recommended Actions
- →Audit all code repositories for calls to listCatalogCategories, any POST_* XML feed, and V2 settlement reports; locate them via a grep for those st...
- →Update LWA token requests in Seller Central > Developer Settings to include sellingpartnerapi::catalog, ::reports, and ::feeds scopes and test with...
- →Create a sandbox test in your SP‑API developer account and submit a JSON_LISTINGS_FEED by June 1 2025 to validate the new endpoint before the produ...
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!