Amazon deprecated the Fulfillment Inbound API (v0) in April 2024 and replaced it with the Fulfillment Inbound API (v2024-03-20). If you have an Amazon Seller Central integration built with the universal HTTP connection or a custom flow with Amazon Seller Central export/import for the deprecated API, you should migrate to the new version at the earliest opportunity, based on your business requirements.
This article explains how to find deprecated endpoints in your existing flows and replace them with new ones. Additionally, see the references listed below and make the necessary changes according to your business requirements.
The following table lists the deprecated endpoints. For detailed information on new operations, see Fulfillment Inbound API v2024-03-20.
Deprecated endpoint |
---|
createInboundShipmentPlan |
updateInboundShipment |
createInboundShipment |
getPreorderInfo |
confirmPreorder |
getTransportDetails |
putTransportDetails |
voidTransport |
estimateTransport |
confirmTransport |
Find and replace the endpoint in the existing flows
To find an export/import that uses a Universal HTTP Amazon Seller Central connection:
-
Sign in to your Celigo integrator.io account.
-
Navigate to Resources > Connections.
-
Search for an existing Universal HTTP Amazon Seller Central connection. From the Actions overflow menu, select Used by. A list of all items that use this connection appears.
-
Select your browser’s option to open the export or import in a new tab.
-
Replace the configuration for the deprecated endpoint with the new endpoint as shown in the following example:
Example of how to replace the deprecated endpoint (createInboundShipmentPlan)
Navigate and expand the How would you like the records imported? section and update the following settings:
Existing configuration to be replaced:
-
HTTP method * :
POST
-
Relative URI:
/fba/inbound/v0/plans
Note: To get the relative URIs of the new operations, refer to Fulfillment Inbound API v2024-03-20.
Replacement:
-
HTTP method * :
POST
-
Relative URI:
/inbound/fba/2024-03-20/inboundPlans
Note: For existing exports/imports, you must also update any mappings, hooks, and filters based on the new endpoint data, if any are used in your resources.
Comments
Article is closed for comments.