Overview

In June 2024 Amazon announced that a group of Selling Partner API (SP‑API) resources have moved into the deprecation phase. The endpoints will keep responding for a limited grace period, but each one has a firm removal date after which calls will fail. Sellers who depend on these APIs need to locate the affected calls, switch to the newer versions, and validate the changes before the shutdown to keep order flow and data integrity intact.

Key Points

• Deprecation status — Resources marked as “Deprecated” no longer receive feature updates or bug fixes, and Amazon will not issue patches for them.
• Functionality until removal — Calls to a deprecated endpoint continue to return successful payloads up to the published removal date, after which Amazon returns HTTP 404 Not Found or 410 Gone.
• Fixed removal dates — The deprecation table lists a specific calendar date for each resource; once that date passes, the endpoint is permanently inaccessible.
• Automation risk — Any scheduled script that extracts orders, inventory, or product details from a deprecated API will break on the removal day, potentially delaying shipments or producing stale listings.
• Migration window — Amazon typically provides several months of notice, allowing sellers to transition to the newer version of the same resource or to an alternative API.
• Compliance consequences — Persisting with a removed endpoint can generate compliance alerts in Seller Central, and repeated failures may negatively affect account‑health metrics.

How Deprecation Works

1. Announcement and documentation update — Amazon posts a deprecation notice on the developer portal and adds the affected resource to the deprecation table with a clear cut‑off date. Example: The “GET /orders/v0/orders” call was flagged as deprecated on 1 May 2024, with a removal deadline of 31 December 2024.
2. Grace period for existing calls — During the notice window, the endpoint behaves exactly as before, delivering the same response structure and data.