HomeDocumentationCode SamplesAPI ReferenceAnnouncementsModelsRelease NotesFAQGitHubVideos
Developer HubAPI StatusSupport
Announcements
Developer HubAPI StatusSupport
Back to All

SP-API Updates: Listings Items API adds multi-marketplace support and July listing attribute & enumeration updates

July 15th, 2026 by FabioR_Amazon

In this post

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

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:

  • Update your getListingsItem and searchListingsItems calls to include multiple Amazon store IDs in the marketplaceIds query parameter.
  • Update your response parsing to handle arrays with multiple Amazon store entries in summaries, offers, attributes, issues, and other included data.
  • Use the Amazon store identifiers returned in the response to determine which store each dataset is associated with.
  • For the searchListingsItems operation, note that the first marketplaceIds in the array is treated as the primary Amazon store. The API evaluates filtering and sorting, such as withStatus or sortBy, against the primary Amazon store only.

July updates to listing attribute usage and enumeration values

Effective July 27, 2026, Amazon will update the attribute usage and enumeration values of numerous product types across Amazon stores. These adjustments eliminate redundant attributes and improve the curation of attributes and enumeration values that apply to the corresponding product types.

For a complete list of metadata changes and affected Amazon stores, refer to SP-API product metadata changes.

Who is affected?

Both private and public developers using the Listings Items API and JSON_LISTINGS_FEED feed type to create and edit products with offers are affected by this change. Product-only listings and XSD/XML feed uploads are not affected by this change.

What action is required?

This change takes effect when you create or edit listings for products with offers. It requires you to provide values for the newly added attributes with required usage. For attributes with optional usage, you can choose to provide values. You can choose to use enumeration from the new list in the dropdown values for attributes if the new enumeration is more relevant to the product you are selling.