Overview

Amazon has rolled out breaking updates to the Product Fees API version 0, removing the itemPrice field from request payloads and renaming the response object feeContext to transactionContext. The changes are live on every Amazon marketplace simultaneously, meaning any integration that still references the old fields will receive errors. Sellers and developers must adjust their code immediately to keep fee‑preview functionality operational.

Key Points

• itemPrice field removed — Requests that previously sent pricing data inside previewAttributes.itemPrice will now be rejected.
• feeContext renamed — Responses now return a transactionContext object; any code that deserializes feeContext will fail.
• Global rollout — All marketplaces share the same update schedule, so a single code change covers North America, Europe, Japan, and other regions.
• No grace period — The API enforces the new schema instantly; there is no fallback or deprecation window.
• Alternative pricing parameters remain — Developers can still provide price information through other fields such as price or listingPrice, but must follow the revised documentation.
• Strongly‑typed SDKs need interface updates — Languages that generate classes from the API schema must regenerate or manually edit DTOs to match the new names.

What's Changing

1. Remove itemPrice from request — When building a fee preview request, delete the line that sets previewAttributes.itemPrice.
   Example: A Python script that previously did payload["previewAttributes"]["itemPrice"] = 29.99 must now omit that assignment and rely on the price field instead.
2. Rename to in response handling — Update all JSON parsing logic to look for . : A Node.js function that accessed should be changed to .