POST to /inbound/2024-03-20/inboundPlans to create an inbound plan, providing items (msku, quantity, prepOwner, labelOwner) and a sourceAddress; note the inboundPlanId
Poll GET /inbound/2024-03-20/inboundPlans/{inboundPlanId}/packingOptions until operationStatus is SUCCESS, then list generated packing options
Confirm a packing option via POST /inbound/2024-03-20/inboundPlans/{inboundPlanId}/packingOptions/{packingOptionId}/confirmation; proceed to placement options
List and confirm a placement option similarly; after placement confirmation, retrieve shipments from the placement and generate box labels via generateDeliveryWindowOptions if small parcel, or pallet options for LTL/FTL
Confirm the delivery window and retrieve the final shipment's destination FCs and carrier labels before physically shipping
Known gotchas
The FBA Inbound v2024 API is a multi-step async workflow — nearly every POST returns an operationId and you must poll the corresponding /operations/{operationId} endpoint for the result before proceeding to the next step
Packing, placement, and delivery window options all have an expiry time; if you do not confirm within the window, the options expire and you must re-generate them, which can result in different FC placements
The legacy Fulfillment Inbound v0 API (createInboundShipmentPlan) is deprecated for new integrations; do not mix v0 and v2024 calls for the same shipment plan as they use incompatible IDs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp