Overview

In early April 2024 Amazon announced that a set of SP‑API endpoints will be retired between May 15 2024 and September 30 2024. The notice makes clear that any request sent to these legacy URLs after their removal dates will return error codes, potentially halting order‑processing workflows. Sellers who depend on automated fulfillment integrations must revise their code now to keep inbound shipment creation, inventory updates, and order fulfillment running without interruption.

Key Points

• Deprecation schedule — End‑point shutdowns start on May 15 2024 and continue through September 30 2024, with each date listed in Amazon’s official deprecation table.
• Impacted APIs — The Fulfillment Inbound API version 0 (v0) methods such as GetInboundGuidance, CreateInboundShipmentPlan, and UpdateInboundShipment are slated for removal.
• Error response — After the cut‑off, calls to a retired endpoint return HTTP 404 or 410 together with a “ResourceNotFound” error message.
• Migration path — Sellers must move to the version 1 (v1) equivalents, which require updated request schemas and new mandatory fields.
• Overlap window — Amazon provides a 30‑day period during which both v0 and v1 endpoints accept traffic; the window ends on the announced removal date, after which only v1 remains functional.
• Compliance risk — Failure to migrate can cause delays in inbound shipments, inventory mismatches, and may trigger health‑metric warnings in the seller’s account dashboard.

How the Deprecation Process Works

1. Notice publication — Amazon posts a formal deprecation announcement on the developer portal, enumerating each endpoint, its version, and the exact date it will be retired. Example: The notice specifies that GET /fba/inbound/v0/shipments will cease on July 31 2024.
2. Dual‑runtime phase — For roughly 30 days both the old (v0) and new (v1) URLs remain active. Sellers can issue test calls to the v1 endpoint while still receiving successful responses from v0.