Obtain an SP-API access token by exchanging your LWA (Login with Amazon) client credentials and refresh token at https://api.amazon.com/auth/o2/token.
Retrieve the current listing to confirm the SKU exists: GET /listings/2021-08-01/items/{sellerId}/{sku}?marketplaceIds=ATVPDKIKX0ER&issueLocale=en_US.
Build a JSON Patch document targeting only the attributes you want to change — for price use the 'purchasable_offer' attribute and for quantity use 'fulfillment_availability'; each patch entry has an 'op' of 'replace' and a 'path' of '/attributes/{attributeName}'.
Submit PATCH /listings/2021-08-01/items/{sellerId}/{sku}?marketplaceIds=ATVPDKIKX0ER with the JSON Patch body and Content-Type: application/json.
Inspect the response 'status' field: 'ACCEPTED' means the patch was queued; 'INVALID' returns an 'issues' array with human-readable error messages and suggested values.
Poll GET /listings/2021-08-01/items/{sellerId}/{sku}?includedData=attributes,issues,offers after a few minutes to confirm the updated attributes are live.
Known gotchas
Only top-level attributes can be patched — nested attribute patching is not supported; you must replace the entire top-level attribute object even if you only want to change one nested field within it.
The JSON_LISTINGS_FEED feed type (and its XML predecessors) was the legacy way to do bulk price/quantity updates; as of July 31, 2025, XML and flat-file feed types for listings are deprecated — use patchListingsItem or JSON_LISTINGS_FEED for remaining bulk needs.
The mode=VALIDATION_PREVIEW query parameter lets you dry-run a patch and inspect issues without persisting changes — use it in staging before writing to production listings.
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