Overview

On May 20 2022, Amazon launched version 2022‑04‑01 of its Catalog Items API, part of the Selling Partner API (SP‑API) suite. The update replaces keyword‑centric queries with identifier‑driven searches, trims response payloads, and introduces clearer error handling. Sellers and developers who pull catalog data for listings, inventory, or reporting will notice faster, more precise responses and can reduce the number of API calls needed to keep their systems in sync.

Key Points

• Release Date — The new API version went live on May 20 2022 after a minor fix to report type categories.
• Identifier‑Based Search — searchCatalogItems now accepts ASIN, SKU, UPC, and EAN arrays, enabling deterministic lookups instead of broad keyword searches.
• Streamlined Responses — Unnecessary fields have been removed from the payload, lowering latency for common use cases such as listing creation and inventory updates.
• Community‑Driven Changes — Feedback from developers highlighted pain points around search accuracy and response size; the update addresses those concerns.
• Optional Upgrade — Existing integrations that rely on the older API version remain functional; the new version is available as a separate, optional endpoint.

How the New API Works (or "What's Changing")

1. Authentication — All requests must carry a valid SP‑API OAuth bearer token or an IAM role signature. Example: a GET request to https://sellingpartnerapi-na.amazon.com/catalog/v0/items with the header Authorization: Bearer <token>.

2. Request Construction — The searchCatalogItems endpoint now requires an Identifiers object. Example payload:

   {
     "Identifiers": {
       "ASIN": ["B07PGL2ZSL"],
       "SKU": ["MYSKU123"]
     }
   }
   

3. Identifier Prioritization — When multiple identifiers are supplied, the API resolves them in the order ASIN → SKU → UPC/EAN. Example: a query containing both an ASIN and a SKU returns the ASIN result first, then the SKU if the ASIN is not found.