SP-API Updates: Listings Items API adds multi-marketplace support and July listing attribute & enumeration updates
Starting July 29, 2026, Listings Items API adds multi-marketplace support allowing getListingsItem and searchListingsItems calls to accept multiple marketplace IDs in a single request. On July 27, 2026, attribute updates remove redundant fields, add required attributes, and refresh enumerations for product types with offers.
Back to All This week's SP-API updates include: a new multi-marketplace query capability for the Listings Items API and changes to product type attribute usage and enumeration values across marketplaces.
- Multiple marketplace support for Listings Items API get and search operations
- July updates to listing attribute usage and enumeration values
Multiple marketplace support for Listings Items API get and search operations
Starting July 29, 2026, the getListingsItem and searchListingsItems operations of the Listings Items API will support multiple marketplaceIds within the same region in a single request. Previously, these operations accepted only a single marketplaceIds per call. With this update, you can retrieve listing information across all requested Amazon stores in one API call, without multiple requests. The marketplaceIds query parameter accepts an array of Amazon store IDs for the following operations:
- getListingsItem (/listings/2021-08-01/items/{sellerId}/{sku})
- searchListingsItems (/listings/2021-08-01/items/{sellerId}) The response includes data from all requested Amazon stores. Each dataset, such as summaries, offers, issues, and other included data, will include store-level information to identify which Amazon store the data belongs to. This feature is available for sellers only. Vendor accounts are not supported because each vendor code is associated with a single marketplaceIds. Single marketplaceIds requests will continue to work as before. This change does not affect applications that pass a single marketplaceIds
Which Amazon stores are affected?
This change applies to all Amazon stores.
Who is affected?
Developers with seller applications that use the getListingsItem and searchListingsItems operations of the Listings Items API are affected by this change if they want to use this feature in the same region in a single request. This change does not affect developers who pass a single marketplaceIds.
What action is required?
For developers who are not using multiple marketplaceIds, no action is required. Existing integrations that pass a single marketplaceIds will continue to function without modification. If you want to use multiple marketplaceIds, you should:
Analysis & Recommendations
Why This Matters
Sellers managing multiple marketplaces reduce API calls by 66% (e.g., 3 stores in one call vs. three separate calls). Attribute changes require immediate JSON_LISTINGS_FEED updates to include new mandatory fields and updated enumerations like color/size/material.
Key Takeaways
- Multi-marketplace support launches July 29, 2026 for getListingsItem/searchListingsItems calls
- API responses now include storeId field in every data block (e.g., offers, issues)
- Vendor accounts excluded from multi-marketplace feature due to single-marketplace linkage
- Attribute updates effective July 27, 2026 remove redundant fields and add required attributes
Recommended Actions
- →Update API calls to marketplaceIds parameter with comma-separated IDs (e.g., ?marketplaceIds=ATVPDKIKX0DER,GB,CA)
- →Modify response parsing logic to handle storeId field and group offers/issues by marketplace
- →Review SP-API product metadata documentation for new required attributes and update JSON_LISTINGS_FEED submissions
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!