Update: The Catalog Items API v2022-04-01 provides a new classifications parameter for sellers and vendors
Amazon added a new classifications query flag to the Catalog Items API v2022‑04‑01, allowing up to 20 ASINs per call and returning the full category hierarchy. Legacy MWS calls (GetProductCategoriesForSKU/ASIN) will be retired after the Q3 2026 quarterly update. The change consolidates authentication to SP‑API LWA + IAM.
Overview
Amazon has upgraded the Catalog Items API (v2022‑04‑01) by adding a classifications query option. The new parameter lets sellers and vendors retrieve the complete category tree for any ASIN in the same request they use to pull item details. Consolidating this data into a single SP‑API endpoint removes the need for the older MWS category calls and speeds up integration workflows.
Key Points
- New query flag — The
classificationsflag is placed inside theincludedDataarray, enabling a single call to return both product attributes and the full category hierarchy. - MWS retirement — Legacy MWS operations
GetProductCategoriesForSKU(seller) andGetProductCategoriesForASIN(vendor) are scheduled for deprecation and will cease delivering data after the upcoming quarterly update. - Complete hierarchy — The response now includes every level from the root node to the leaf node, for example “Home & Kitchen > Kitchen & Dining > Cookware”, instead of a single category identifier.
- Unified security — All requests rely on SP‑API authentication (LWA token plus IAM role), eliminating the separate credential set that MWS required.
- Batch capability — Up to 20 ASINs can be queried in one request, reducing the number of HTTP calls needed for large inventories and lowering overall latency.
How the Classifications Parameter Works
-
Authenticate with SP‑API — Obtain an LWA access token and assume the IAM role that grants Catalog Items permissions.
- Example: Using the AWS SDK, invoke
sts.assumeRolewith a policy such asAmazonSPAPIAccess, then exchange the temporary security credentials for an LWA token via Amazon’s token endpoint.
- Example: Using the AWS SDK, invoke
-
Compose the request URL — Add
includedData=classificationsto theGET /catalog/v0/itemsendpoint and list the desired ASINs in the query parameter.
Analysis & Recommendations
Why This Matters
Without migrating, integrations will lose category data after Q3 2026, breaking listings and advertising targeting. The batch limit of 20 ASINs cuts HTTP calls by >90 % for large catalogs, reducing latency and cost. Full hierarchy enables more accurate keyword and compliance rules.
Key Takeaways
- The `classifications` flag is added to the `includedData` array of GET /catalog/v0/items.
- Up to 20 ASINs can be queried in a single request, replacing one‑SKU MWS calls.
- MWS endpoints GetProductCategoriesForSKU and GetProductCategoriesForASIN will stop delivering data after the Q3 2026 update.
Recommended Actions
- →In Seller Central, open the API Integration page and replace any MWS GetProductCategories calls with a GET to https://sellingpartnerapi-na.amazon.c...
- →Update your batch logic to group ASINs into chunks of 20 and send parallel requests, using the SP‑API SDK's assumeRole workflow for LWA token gener...
- →Run a one‑time audit before Q3 2026: export existing category IDs, pull fresh classifications via the new endpoint, compare, and correct mismatches...
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!