Identify the listing's SKU and the marketplaceId for the target region; the Listings Items API operates per SKU per marketplace
Build a PATCH body with patches array: each patch has op (replace), path (e.g., /attributes/purchasable_offer or /fulfillmentAvailability), and value for the specific attribute being updated
PATCH /listings/2021-08-01/items/{sellerId}/{sku}?marketplaceIds={marketplaceId} with the body; a 200 response with status ACCEPTED means the patch was received for processing, not yet applied
Poll GET /listings/2021-08-01/items/{sellerId}/{sku}?marketplaceIds={marketplaceId}&includedData=attributes,fulfillmentAvailability to confirm the new price and quantity are reflected
Handle the issues array in the response: Amazon may return ACCEPTED but flag issues (e.g., price too far from competitor prices) that cause delayed or conditional application of the update
Known gotchas
The path for price updates is /attributes/purchasable_offer and the value must be a JSON object matching the purchasable_offer attribute schema including currency and schedule; the exact schema varies by product type — retrieve the product type definition to confirm required fields
Listings Items PATCH does not validate whether the SKU exists before returning 200; if the SKU is wrong or not owned by the seller, the response may still be ACCEPTED but the listing will never reflect the change
Price updates via the Listings API for FBA listings may be superseded by Amazon's automated repricer if the seller has enabled it; coordinate with pricing strategy before patching FBA prices
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