Update: Fulfillment Inbound API v0 removal date changed to January 21, 2025
Amazon will retire the Fulfillment Inbound API v0 on January 21 2025, extending the original deadline by roughly 18 months. Sellers must migrate to the v1 endpoints (e.g., https://sellingpartnerapi-na.amazon.com/fba/inbound/v1/shipments/createInboundShipmentPlan), update request bodies and add the x‑amz‑access‑token header before that date.
Amazon is moving its Fulfillment Inbound API from version 0 to version 1, and the shutdown of the v0 endpoints has been rescheduled to January 21, 2025. All sellers who rely on inbound‑shipment automation must migrate to the v1 API before that date, or risk losing the ability to create shipment plans, confirm transport, and replenish inventory.
Key Points
New retirement date — The v0 inbound‑API will cease to respond on January 21, 2025, extending the original timeline by roughly 18 months.
Endpoints affected — The deprecation covers every v0 call used for inbound logistics, including createInboundShipmentPlan, updateInboundShipment, createInboundShipment, getPreorderInfo, confirmPreorder, getTransportDetails, putTransportDetails, voidTransport, estimateTransport, and confirmTransport.
v1 as the replacement — Version 1 delivers identical functional coverage but introduces revised request bodies, stricter authentication, and more granular error messages.
Automation breakage — Any custom script, third‑party integration, or ERP system that still points to the v0 URLs will start receiving HTTP 410 “Gone” responses after the cutoff, halting the inbound workflow.
Support window — Amazon will make migration guides, sandbox access, and a dedicated help channel available through July 2024 to assist sellers in testing v1 calls.
Error‑code overhaul — Generic InvalidParameter errors from v0 are replaced by specific codes such as ShipmentPlanNotFound, CarrierIdInvalid, and TransportOptionUnavailable, enabling faster troubleshooting.
How the Change Works
Endpoint shutdown — On January 21, 2025 Amazon’s servers will return a 410 status for every v0 URL, for example . A script that previously posted a shipment‑plan request to that address will instantly fail, stopping the plan‑creation step.
Analysis & Recommendations
Why This Matters
After Jan 21 2025 all v0 calls will return HTTP 410, halting shipment‑plan creation, transport confirmation and inventory replenishment. Updating URLs, payload structures and authentication ensures continuous inbound workflow and avoids lost sales.
Key Takeaways
Retirement date moved to Jan 21 2025, about 18 months later than originally planned.
Every v0 inbound call (e.g., createInboundShipmentPlan, updateInboundShipment, estimateTransport) will return a 410 Gone response after the cutoff.
v1 requires payload changes such as moving ShipFromAddress into an originAddress object and mandates the x‑amz‑access‑token header for delegated se...
From July 2024 v0 responses will include a Deprecation header and Amazon will provide migration guides and sandbox access.
Recommended Actions
→Replace all ‘/v0/’ URLs with ‘/v1/’ in your integration code (e.g., in Seller Central > Developer Settings or your source repository).
→Update request bodies to match the v1 schema (move address fields into an originAddress object) and validate using the SP‑API sandbox (Developer Co...
→Add logic to fetch and attach the x‑amz‑access‑token header for delegated seller accounts; test by calling estimateTransport and confirming no 401 ...
v1 endpoint activation — The matching v1 URLs (e.g., https://sellingpartnerapi-na.amazon.com/fba/inbound/v1/shipments/createInboundShipmentPlan) stay operational throughout the transition. Sellers must change the request path and reshape the payload; for instance, the ShipFromAddress field moves from the top level into a nested originAddress object.
Tighter authentication — Both versions rely on AWS Signature 4, but v1 enforces a narrower timestamp window and requires the x-amz-access-token header for delegated seller accounts. A seller using a refresh token will need to add this header when calling estimateTransport; otherwise the request will be rejected with a 401 error.
Detailed error mapping — v0 often returned a blanket InvalidParameter for many validation problems. v1 introduces precise codes like CarrierIdInvalid when an outdated carrier identifier is supplied, allowing developers to programmatically retry only recoverable failures.
Sandbox parity — Amazon’s sandbox mirrors production for v1 calls, letting sellers simulate the full inbound sequence—creating a shipment plan, confirming preorder, estimating transport—without touching live inventory. A successful sandbox run that returns a shipmentPlanId confirms the integration is ready for production.
Deprecation signaling — Starting July 2024, Amazon will attach a Deprecation header to any v0 response, indicating the upcoming removal date. Monitoring this header gives sellers an early warning before the hard cutoff.
Context: Before vs. After
Before: An integration posted createInboundShipmentPlan to the v0 endpoint, sending a flat JSON where fields like ShipFromCountryCode sat at the root level, and relied on a generic 400 Bad Request for any validation issue. The same endpoint handled both regular and preorder shipments, forcing developers to add conditional logic in their code.
After: The same workflow now targets the v1 endpoint, nests address data under an originAddress object, and separates preorder actions into a distinct confirmPreorder call. Errors such as TransportOptionUnavailable are returned with specific codes, enabling the system to automatically retry only when transport options truly fail, while surfacing other problems for manual review.
Seller Impact
Sellers should begin the migration immediately to keep their inbound supply chain uninterrupted.
Swap out URLs — Replace every occurrence of a v0 URL in your code with the corresponding v1 path. For example, change POST https://.../v0/shipments/createInboundShipmentPlan to POST https://.../v1/shipments/createInboundShipmentPlan and verify that the response contains a shipmentPlanId.
Revise JSON structures — Align your request bodies with the v1 schema. If your current payload includes "ShipFromCountryCode":"US" at the top level, move it inside "originAddress":{"countryCode":"US"}. Run a sandbox test with a sample SKU list to ensure the payload passes validation.
Update authentication flow — Make sure your integration fetches a fresh x-amz-access-token for delegated seller accounts and includes it on every v1 request. Adding a small routine that logs token expiry times can prevent unexpected 401 errors during high‑volume replenishment periods.
Watch deprecation headers — From July 2024 onward, Amazon will add a Deprecation header to v0 responses. Configure your logging to capture this header and trigger an internal alert, giving you a safety net before the final shutdown.
Leverage migration resources — Download Amazon’s migration guide, use the sandbox to execute end‑to‑end scenarios, and contact the dedicated support channel if a v1 call returns an unfamiliar error code.
Validate transport workflows — After updating the estimateTransport and confirmTransport calls, run a sandbox test that estimates a carrier cost and then confirms the transport. Confirm that the response includes a transportId and that no 401 or 410 errors appear.
Document the change — Record the new endpoint URLs, payload schemas, and authentication steps in your internal integration wiki. Sharing this documentation with the operations team ensures that any future code changes respect the v1 requirements and avoid accidental re‑introduction of v0 calls.
By completing these actions well before the January 2025 deadline, sellers can maintain seamless inventory replenishment, stay compliant with Amazon’s fulfillment standards, and benefit from the clearer error handling and modernized data structures introduced in the v1 Fulfillment Inbound API.
Source: developer-docs.amazon.com
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
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!