Getting all attributes of an Item

[FloderCC]

Good afternoon,

I need to get all the attributes of an Item given its ASIN, but the 'attributes' value for the 'includedData' parameter is only available to the brand owner of the item.

I am using the query https://github.com/amzn/selling-partner-api-docs/blob/main/references/catalog-items-api/catalogItems_2020-12-01.md#getcatalogitem and It return the error: {'code': 'InvalidInput', 'message': 'FORBIDDEN', 'details': 'The includedData requested requires Brand Registry affiliation with the requested item. Remove the requested includedData item or register the brand of the item in Brand Registry with the seller.'}

Is there any other way to get all attributes for any Amazon listing given its ASIN?

[teddy-codes]

Does summaries provide you with what you are looking for?

[chapmanjw]

The attributes data set is only available to the brand owner of the ASIN. Are there specific data elements you are looking for that are not covered by the summaries or one of the other data sets?

[FloderCC]

The attributes data set is only available to the brand owner of the ASIN. Are there specific data elements you are looking for that are not covered by the summaries or one of the other data sets?

Hello, first thank you for your attention, Yes. I would like to obtain all the details of the product, just like when a product is uploaded, all the properties are specified in the form ... "resolution": [ { "language_tag": "en_US", "value": "4K", "marketplace_id": "ATVPDKIKX0DER" } ], ... I would like to be able to obtain all this information. Including quantity in stock, product dimensions etc. I would like to do that at least with the products that I have for sale, including those that I am not the brand ower.

[MasterShoty]

Ditto, I am performing migrations from mws to sp-api and getCatalogItem doesn't include the following data in summaries:

• authors and bindings for books (which is publicly available to view on the amazon store)
• product dimensions and weights (which is also publicly available through https://sellercentral.amazon.com/hz/fba/profitabilitycalculator/index?lang=en_US)

I was previously able to obtain all of these data with mws GetMatchingProduct

[teddy-codes]

Basically all of the data that was from GetMatchingProduct(ForID) has been hidden behind the attributes key now and that's going to make the migration basically impossible.

[lijinghui]

The data set is only available to the brand owner of the ASIN. Are there specific data elements you are looking for that are not covered by the or one of the other data setsattributes``summaries?

Hi, but the catalog item v0 can get attributes info. Why version 2020-12-01 abandon this logic？ It puzzled me.

[ashokrajab]

Requesting response from Amazon team with respect to this issue. cc @rugved1991 @ShivikaK

[ashokrajab]

As mention above we are unable to achieve the same functionality of GetMatchingProduct in SP API Catalog Version 2020-12-01.

MWS Flow:

1. Using SKU call GetMatchingProductForId.
2. Identify whether an item is a variant under an item group. If so, then obtain the ASIN of parent from the response of above GetMatchingProductForId API.
3. Make GetMatchingProduct with parent ASIN to get the parent details such as name, attributes.

Trying to achieve the same functionality in SP API:

1. Response received for CatalogAPI Version 2020-12-01 (without specifying includedData): {asin: "B00YT13T3Q", attributes: null, identifiers: null, images: null, productTypes: null, salesRanks: null, summaries: [{ marketplaceId: "ATVPDKIKX0DER", brandName: "SAMSUNG", browseNode: null, colorName: "Gold", itemName: "Samsung Galaxy Grand Prime GSM Cellphone - Gold", manufacturer: "Samsung", modelNumber: "Galaxy Grand Prime", sizeName: null, styleName: null }], , variations: null, vendorDetails: null }

Response received for CatalogAPI Version 2020-12-01 (specifying includedData): { "errors": [ { "code": "InvalidInput", "message": "FORBIDDEN", "details": "The includedData requested requires Brand Registry affiliation with the requested item. Remove the requested includedData item or register the brand of the item in Brand Registry with the seller." } ] }

As you can see we are unable to obtain parent information.

2. Making Catalog API V0: { "identifiers": { "marketplaceASIN": { "marketplaceId": "ATVPDKIKX0DER", "ASIN": "B00YT13T3Q" }, "skUIdentifier": null }, "attributeSets": { [{ "actor": null, "artist": null, "aspectRatio": null, "audienceRating": null, "author": null, "backFinding": null, "bandMaterialType": null, "binding": "Electronics", "blurayRegion": null, "brand": "SAMSUNG", "ceroAgeRating": null, "chainType": null, "claspType": null, "color": "Gold", "cpuManufacturer": null, "cpuSpeed": null, "cpuType": null, "creator": null, "department": "Unlocked cell phones are compatible with GSM carriers like AT&T and T-Mobile as well as with GSM SIM cards (e.g. H20, Straight Talk, and select prepaid carriers). Unlocked cell phones will not work with CDMA Carriers like Sprint, Verizon, Boost or Virgin.", "director": null, "displaySize": { "value": 5, "units": "inches" }, "edition": null, "episodeSequence": null, "esrbAgeRating": null, "feature": null, "flavor": null, "format": null, "gemType": null, "genre": null, "golfClubFlex": null, "golfClubLoft": null, "handOrientation": null, "hardDiskInterface": null, "hardDiskSize": null, "hardwarePlatform": null, "hazardousMaterialType": null, "itemDimensions": { "height": { "value": 0.34, "units": "inches" }, "length": { "value": 5.70, "units": "inches" }, "width": { "value": 2.84, "units": "inches" }, "weight": { "value": 0.343750, "units": "pounds" } }, "isAdultProduct": null, "isAutographed": null, "isEligibleForTradeIn": true, "isMemorabilia": null, "issuesPerYear": null, "itemPartNumber": null, "label": "Samsung", "languages": null, "legalDisclaimer": null, "listPrice": { "amount": 159.99, "currencyCode": "USD" }, "manufacturer": "Samsung", "manufacturerMaximumAge": null, "manufacturerMinimumAge": null, "manufacturerPartsWarrantyDescription": null, "materialType": null, "maximumResolution": { "value": null, "units": "megapixels" }, "mediaType": null, "metalStamp": null, "metalType": null, "model": "Galaxy Grand Prime", "numberOfDiscs": null, "numberOfIssues": null, "numberOfItems": null, "numberOfPages": null, "numberOfTracks": null, "operatingSystem": [Android], "opticalZoom": null, "packageDimensions": { "height": { "value": 1.99999999796, "units": "inches" }, "length": { "value": 5.99999999388, "units": "inches" }, "width": { "value": 3.49999999643, "units": "inches" }, "weight": { "value": 0.65036367290, "units": "pounds" } }, "packageQuantity": 1, "partNumber": "G531H GLD", "pegiRating": null, "platform": null, "processorCount": null, "productGroup": "Wireless", "productTypeName": "CELLULAR_PHONE", "productTypeSubcategory": null, "publicationDate": null, "publisher": "Samsung", "regionCode": null, "releaseDate": null, "ringSize": null, "runningTime": null, "shaftMaterial": null, "scent": null, "seasonSequence": null, "seikodoProductCode": null, "size": null, "sizePerPearl": null, "smallImage": { "URL": "https://m.media-amazon.com/images/I/51s-DOPdzwL._SL75_.jpg", "height": { "value": 75, "units": "pixels" }, "width": { "value": 75, "units": "pixels" } }, "studio": "Samsung", "subscriptionLength": null, "systemMemorySize": { "value": 8, "units": "GB" }, "systemMemoryType": null, "theatricalReleaseDate": null, "title": "Samsung Galaxy Grand Prime GSM Cellphone - Gold", "totalDiamondWeight": null, "totalGemWeight": null, "warranty": null, "weeeTaxValue": null }] }, "relationships": { [{ "identifiers": { "marketplaceASIN": { "marketplaceId": "ATVPDKIKX0DER", "ASIN": "B00YVNVGXM" }, "skUIdentifier": null }, "color": null, "edition": null, "flavor": null, "gemType": null, "golfClubFlex": null, "handOrientation": null, "hardwarePlatform": null, "materialType": null, "metalType": null, "model": null, "operatingSystem": null, "productTypeSubcategory": null, "ringSize": null, "shaftMaterial": null, "scent": null, "size": null, "sizePerPearl": null, "golfClubLoft": null, "totalDiamondWeight": null, "totalGemWeight": null, "packageQuantity": null, "itemDimensions": null }] }, "salesRankings": { [{ "productCategoryId": "ce_display_on_website", "rank": 107622 }, { "productCategoryId": "7072561011", "rank": 3987 }] } }

As you can see the V0 returns attributes and relationship information. Although that still remains ambiguous because there are unnecessary information sent under attributes. It is not clear which are the actual attributes of the variant.

[However this should be irrelevant with respect to the issue since this version anyway going to be deprecated. I'm just using this to point out the attribute info in present in V0 and not in Version 2020-12-01].

Requesting Amazon Team's assistance in this regard at the earliest.

Thanks in advance.

cc @ShivikaK @rugved1991 @chapmanjw

[ashokrajab]

I have raised a case log for the same: Case ID 7224294572.

[chapmanjw]

We do have a backlog item to address the variation details, item/package dimensions, and additional identifying attributes in the next revision of this API.

While the current MWS Products API + Catalog V0 API operations do include more data in some cases, they are by no means comprehensive of all catalog data associated with an ASIN. The attributes for those include a snapshot of common identifying attributes from 10+ years ago.

The purpose of providing all of the attributes data for brand owners specifically is that is the role associated with fully managing the content for display on the detail pages. This attributes data is not intended for use outside the express purpose of managing the content (i.e. inspecting for correctness, submitting missing data, etc.).

The summaries and other data sections are intended for use by resellers, building search results pages, and other workflows for selling items on Amazon. For those use-cases, we are not providing "all" attributes data, rather we are providing specific data elements to serve these use-cases as needed. With that in mind, we are asking for which specific data elements are needed to serve your non-brand-owner use-cases. The 2020-12-01 version is a "starting" point for that. There will be another iteration prior to deprecating v0 + MWS operations with additional data elements, depending on public feedback.

So, knowing that you cannot blanketly have "all" data as a non-brand-owner, what data specific data elements are needed and what are those data elements needed for?

[FloderCC]

We do have a backlog item to address the variation details, item/package dimensions, and additional identifying attributes in the next revision of this API.

While the current MWS Products API + Catalog V0 API operations do include more data in some cases, they are by no means comprehensive of all catalog data associated with an ASIN. The attributes for those include a snapshot of common identifying attributes from 10+ years ago.

The purpose of providing all of the attributes data for brand owners specifically is that is the role associated with fully managing the content for display on the detail pages. This attributes data is not intended for use outside the express purpose of managing the content (i.e. inspecting for correctness, submitting missing data, etc.).

The summaries and other data sections are intended for use by resellers, building search results pages, and other workflows for selling items on Amazon. For those use-cases, we are not providing "all" attributes data, rather we are providing specific data elements to serve these use-cases as needed. With that in mind, we are asking for which specific data elements are needed to serve your non-brand-owner use-cases. The 2020-12-01 version is a "starting" point for that. There will be another iteration prior to deprecating v0 + MWS operations with additional data elements, depending on public feedback.

So, knowing that you cannot blanketly have "all" data as a non-brand-owner, what data specific data elements are needed and what are those data elements needed for?

Hello, Thank you very much for that valuable information!

In our case, we want to make our system allow downloading all the information of any product or at least of those that are for sale in the user's Amazon account. That would allow the user to manage the product information from our system through the Listings Items API. But to do that, we need to download all the data of the product of which the user is a reseller (or not), or at least those attributes that are required for the productType of that product, so that once our system imports a product have all the information necessary to put it on sale in the user's Amazon account, or if a product that the user already has for sale is imported, then the user can simply modify data in our system and our system has all the information to reflect that change in Amazon using the putListingsItem in endpoint. Currently, there are specific data for each productType that is required when using the putListingsItem call and that we have not been able to obtain from Amazon.

[chapmanjw]

@FloderCC Would it be fair to summarize the use-case you are describing as a reseller creating/managing all of the product content for items that the owner of the brand have not themselves listed on Amazon (or at least are not themselves actively maintaining)?

[FloderCC]

@FloderCC Would it be fair to summarize the use-case you are describing as a reseller creating/managing all of the product content for items that the owner of the brand have not themselves listed on Amazon (or at least are not themselves actively maintaining)?

Hello. It would be a reseller who wants to download the data of a product and then manage its offer through the Listings Items API (https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/use-case-guides/listings-items-api-use-case-guide/listings-items-api-use-case-guide_2020-09-01.md#tutorial-create-or-fully-update-a-listing) . This reseller would only manage attributes of its offer, but the putListingsItem operation requests some attributes that are not in the summary.

[ashokrajab]

Hi @chapmanjw, Here is our use-case:

We sync standalone items and variants along with it's parent's details into our system. With this data we will be correspondingly creating standalone item and item group with variants in our app. This means we need information such as attributes (eg: Color, Size, Material etc) of the Parent, attribute options (eg: Red, XL, Cotton etc) of the variants, Parent ASIN present in the response of Catalog API made for variant ASIN.

Without this information we cannot create the item/item group in our app. So we need these information to be sent for resellers as well. Otherwise this will break the existing functionality that is established by MWS API.

Hope this clarifies.

[chapmanjw]

@FloderCC If you look at the Product Type Definitions API, you will see the option for requirements: https://github.com/amzn/selling-partner-api-docs/blob/main/references/product-type-definitions-api/definitionsProductTypes_2020-09-01.md#requirements-subgroup-2. The LISTING_OFFER_ONLY requirements allows you to create a listing with a product id (UPC, EAN, ASIN, etc.), condition, price, inventory, etc., without providing all of the product attributes needed to create a new item.

Does this cover your use-case without needing all of the attributes data to "create" a new product as opposed to creating a new offer on an existing product?

[chapmanjw]

@AshokRaja10 We do have action items to add all variation theme dimension attributes and all identifying attributes to the summaries. We are working on that for the next revision of the API. There are some known gaps in that regard in the MWS/V0 APIs too (i.e. we don't currently return all variation theme data, only some of it).

[teddy-codes]

@chapmanjw so, can you confirm that our attributes will be available eventually?

https://github.com/amzn/selling-partner-api-models/issues/1563

[chapmanjw]

@teddy-codes Yes, each of those attributes listed are either already covered or planned on our roadmap before deprecating v0 (I can't commit to specific timelines, as you'd expect).

[FloderCC]

Definitely, you can not get all the detailed information of a type of product registered by another seller. So I couldn't backup any product, but I could put it up for sale because as @chapmanjw said: The LISTING_OFFER_ONLY requirements allowed me to create a listing with a product id (UPC, EAN, ASIN, etc.), condition, price, inventory, etc., without providing all of the product attributes needed to create a new item. Thank you very much @chapmanjw

[jamescurrer]

I'd like to add my use case for missing Attributes here. We provide software for recyclers of used media product (books, music, DVD), who use the attribute responses MWS provides in GetMatchingProductForId to determine which products to sell on Amazon and which to recycle. This in turn drives sales on Amazon because the product being listed is relevant and more likely to sell, rather than cluttering the marketplace with unpopular offers. We have machine learning models that depend on the following attributes coming from MWS to evaluate a products saleability in real time (as the product is passing under a barcode scanner):

• Binding - essential to avoid mismatches with incorrect catalogue data, Kindle editions etc
• PublicationDate / ReleaseDate
• Publisher
• ListPrice / RRP
• Edition
• NumberOfPages
• Author / Artist
• Languages

We also use the aforementioned Product dimensions / weights for pricing as well, again ensuring that the most competitive price can be offered to the customer without having to make inaccurate assumptions about how much something will cost to ship.

[chapmanjw]

@FloderCC @teddy-codes We have updated the 2020-12-01 version of the Catalog Items Get API to no longer require brand affiliation with an ASIN in order to retrieve the raw attributes data set. Requesting the attributes data set will return all attributes for an ASIN that are defined by the Product Type Definitions API for the product type of the ASIN. As we are in-progress of migrating product types to the APIs, some ASINs will continue to rollup to the PRODUCT product type for the available attributes and only include the attributes that are defined on the root PRODUCT product type.

While the attributes data will assist in inspecting the "raw" attributes for an ASIN, it is unmodeled data and is not ideal for some use-cases depending on modeled data (i.e., modeled in the Swagger model). With that in mind, we do still plan another release where additional details are added to the Swagger model of the summaries and variations sections.

Thanks for the feedback thus far and helping us to refine this product!

[whitedevils]

Sorry, how can i submit a new item with pulistingitem api if there is not "Asin" property? Thanks

[chapmanjw]

@whitedevils The Listings APIs (like listings on Seller Central) are keyed by SKU, which you define. If you are looking to associate your listing with an existing ASIN, you can use the merchant_suggested_asin attribute when calling the Listings APIs. You can use the Product Type Definitions API to sell the full list of available attributes: https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/use-case-guides/product-type-definitions-api-use-case-guide/definitions-product-types-api-use-case-guide_2020-09-01.md

[jamesp26]

Hi. We are in the latter stages of migrating from getMatchingProductForId over to getCatalogItem. However, 2 fields that were essential for our reporting back to clients were

• Flavor
• Scent

I cannot find these in summaries or the attributes. Interestingly, 'Color' is available in summaries.

Is there another way i should be getting these attributes (Flavor, Scent)? We only need them for the brand owners and it seems logical that they should be available in the getCatalogItem request. Thanks for any help.

[IamPARAMESH]

@AshokRaja10 We do have action items to add all variation theme dimension attributes and all identifying attributes to the summaries. We are working on that for the next revision of the API. There are some known gaps in that regard in the MWS/V0 APIs too (i.e. we don't currently return all variation theme data, only some of it).

@chapmanjw can you provide us with the timeline for the complete attribute information availability? With migration deadlines nearing, it would be better if we knew the timeline in advance, to avoid last-minute hassles.

Thanks in Advance.

[chapmanjw]

@IamPARAMESH For expanding the attributes section to include all attributes, not just the ones for launched product types (i.e. what this poll describes: https://github.com/amzn/selling-partner-api-docs/discussions/1609), we are expecting that to roll out in the next few weeks. We're nearly code complete on that change, working through final testing and validation before we roll it out.

[chapmanjw]

For everyone following this thread, I've posted a discussion with a preview of the next iteration of the Catalog Items API: https://github.com/amzn/selling-partner-api-docs/discussions/2017. I would love your feedback as we prepare to implement and launch this next iteration.

[RMagician]

If you are using python and python-amazon-sp-api note that by default the get_catalog_item endpoint uses the 2020 version.

When creating the object, you have the option to pick the version you want to use

class CatalogItemsVersion(str, enum.Enum):
    V_2020_12_01 = "2020-12-01"
    V_2022_04_01 = "2022-04-01"
    LATEST = "2022-04-01"

class CatalogItems(Client):
    """
    CatalogItems SP-API Client
    :link:

    The Selling Partner API for Catalog Items provides programmatic access to information about items in the Amazon catalog.
    """

    version: CatalogItemsVersion = CatalogItemsVersion.V_2020_12_01

    def __init__(self, *args, **kwargs):
        if 'version' in kwargs:
            self.version = kwargs.get('version', CatalogItemsVersion.V_2020_12_01)
        super().__init__(*args, **{**kwargs, 'version': self.version})

this being said, I'm still getting empty variations / relationships catalog_response = catalog_items_api.get_catalog_item(asin="B07FTVJ7Y9", includedData=["relationships"]) gives {'asin': 'B07FTVJ7Y9', 'relationships': [{'marketplaceId': 'A1F83G8C2ARO7P', 'relationships': []}]}