May 2022 SP-API Release Announcement
On May 20 2022 Amazon released Catalog Items API v2022‑04‑01, replacing keyword searches with identifier‑based lookups (ASIN, SKU, UPC, EAN) and trimming response payloads to improve latency. Sellers can now retrieve precise product data with fewer API calls, enhancing listing creation and inventory updates.
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 —
searchCatalogItemsnow 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")
-
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/itemswith the headerAuthorization: Bearer <token>. -
Request Construction — The
searchCatalogItemsendpoint now requires anIdentifiersobject. Example payload:{ "Identifiers": { "ASIN": ["B07PGL2ZSL"], "SKU": ["MYSKU123"] } } -
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.
Analysis & Recommendations
Why This Matters
The new identifier‑based search returns deterministic results, cutting post‑processing time and reducing round‑trips. Payload trimming lowers latency for common use cases like listing creation, enabling faster inventory sync and fewer API calls.
Key Takeaways
- Release date: May 20 2022
- API version: 2022‑04‑01
- Identifier types: ASIN, SKU, UPC, EAN
- Payload trimmed: only ItemInfo, Offers, Variations returned
Recommended Actions
- →Update integration to use the Identifiers parameter in searchCatalogItems calls, replacing keyword searches with ASIN lookups for listings
- →Test the new API in sandbox with a batch of 100 ASIN queries and compare latency and error rates to the previous version
- →Monitor API metrics for 4xx/5xx responses after switching, setting alerts for any increase
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!