Looking up Product Data in the Amazon Catalog

Data from Amazon's catalog that is returned by ECS contains product features, price and purchasing information and other data.

This section of the documentation describes how to make precise requests and receive back a specific set of data from Amazon's product catalog.

Looking up Specific Products

The ItemLookup operation requests catalog information, offers, and offer listings for up to ten products at a time. Depending on which ItemLookup response groups you include in your request, you can retrieve product reviews, variations, similar products, pricing, availability, images of products, accessories, and other information.

When you return offers for a parent ASIN, the TotalItems will equal zero because parent ASINs are abstractions. As such, they are not for sale. For example, a parent ASIN could be "Shoe." Amazon cannot sell this abstraction. What Amazon can sell is a child of the abstraction, such as a men's shoe, size 10, black, penny loafer, made by Eddy Bauer. For this reason, an ItemLookup can return zero for TotalItems and still have items listed in the response.

Specifying the Product(s) for the Lookup

Products can be retrieved by their ASIN (Amazon Standard Identification Number), SKU, UPC or EAN. In a single request, you can retrieve products by one type of identifier only. For example, you could look up three ASINs in one request, but you could not look up an ASIN and a SKU in a single operation unless you used a batch request.

To retrieve a product by its ASIN, you must include the following parameter in your ItemLookup request:

ItemId The ASIN to be searched for; for multiple products, insert a comma-delimited list (REST) or multiple elements (SOAP).

So, for example, the REST request below would look up a specific product ASIN:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[Your Access Key ID Here]
    &Operation=ItemLookup 
    &ItemId=0486411214

To retrieve a product by its SKU, you must include the following parameters in your ItemLookup request:

IdType SKU

ItemId The product identifier to be searched for; for multiple products, insert a comma-delimited list (REST) or multiple elements (SOAP).

MerchantId SKUs are unique to a particular merchant. In order to ensure you retrieve the exact product you desire, you must always include a merchant ID in your request when you look up an item by SKU.

So, for example, the REST request below would look up a specific product by its SKU:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[Your Access Key ID Here]
    &Operation=ItemLookup 
    &ItemId=[SKU] 
    &MerchantId=[MerchantID]
    &IdType=SKU

To retrieve a product by its UPC (US only), you must include the following parameters in your ItemLookup request:

IdType UPC

ItemId The product identifier to be searched for; for multiple products, insert a comma-delimited list (REST) or multiple elements (SOAP).

SearchIndex The name of the Amazon store that the product associated with the UPC belongs to.

So, for example, the REST request below would look up a specific book by its UPC:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[Your Access Key ID Here]
    &Operation=ItemLookup 
    &ItemId=[UPC] 
    &SearchIndex=Books
    &IdType=UPC

To retrieve a product by its EAN (DE, JP, and CA only), you must include the following parameters in your ItemLookup request:

IdType EAN (Note: EAN or European Article Number is the same as JAN or Japanese Article Number).

ItemId The product identifier to be searched for; for multiple products, insert a comma-delimited list (REST) or multiple elements (SOAP).

SearchIndex
The name of the Amazon store that the product associated with the EAN belongs to. See Search Index Values for the SearchIndex values.

So, for example, the REST request below would look up a specific electronics product on the JP site by its SKU:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[Your Access Key ID Here]
    &Operation=ItemLookup 
    &ItemId=[EAN] 
    &SearchIndex=Electronics
    &IdType=EAN

Filtering Products Returned

The product(s) returned by ItemLookup can be further filtered to include only

offers from a particular merchant(s)
offers for products in a specific condition (new, used, refurbished, collectible)
delivery method (shipped or in-store pickup) US only

To filter your ItemLookup request, include the optional parameters below, as desired.

MerchantId
All returns offer data for all merchants including Amazon.

MerchantId is an alphanumeric identity that specifies a merchant. It can have three settings: All, in which all merchants are included in the response, an alphanumeric identity that specifies a single merchant, or FeaturedBuyBoxMerchant, which returns the merchant identified as the “Buy Box Winner” on a specific detail page. The "Buy Box Winner" is the merchant associated with the sale of the item listed in the Buy Box, which is the box on an item's detail page that enables you to add an item to a shopping cart. The default value for MerchantId is “Amazon.”

If this parameter is omitted, the default is Amazon.

Condition All, New, Used, Refurbished or Collectible - the default is New

DeliveryMethod Ship or ISPU (in-store pickup) - Ship is the default. ISPU applies to the US only.

ISPUPostalCode If the DeliveryMethod parameter is set to ISPU, then this parameter is required and its value should be the zip code of the area where in-store pickup is requested.

FeaturedBuyBoxMerchant

MerchantId is an alphanumeric identity that specifies a merchant. It can have three settings: All, in which all merchants are included in the response, an alphanumeric identity that specifies a single merchant, or FeaturedBuyBoxMerchant.

Multiple retailers often sell the same item, for example, a Harry Potter book. When a user clicks on the Harry Potter book on the Amazon retail web site, the next page, the detail page, includes a Ready to Buy box, which invites the user to add the item to their shopping cart. The merchant associated with the sale is called the “Buy Box” merchant for that detail page.

This functionality is facilitated by setting: MerchantId=FeaturedBuyBoxMerchant. In this way, MerchantId is set to the “Buy Box” merchant.

Requesting Various Subsets of Output Data

All ECS operations support the ResponseGroup parameter which specifies the data subset to be returned. Since Item elements are returned by ItemLookup, the response groups are similar to the response groups for ListLookup, listed below. If no response groups are specified in an ItemLookup operation, the default is Request and Small.

Standard response groups:

Request - Echoes the operation parameters.
ItemIds - Returns only ASINs.

Amalgamated response groups:

Small - Global, item-level data (no pricing or availability), including the ASIN, product title, creator (author, artist, composer, directory, manufacturer, etc.), product group, URL, and manufacturer.
Medium - Includes Small, Request, ItemAttributes, OfferSummary, SalesRank, EditorialReview, and Images response groups.
Large - Includes Medium, Tracks, BrowseNodes, Reviews, ListmaniaLists, Similarities, Offers, and Accessories response groups.

Offer information (actual prices/availability):

OfferSummary
Offers - Includes OfferSummary plus all offer listings specified by the Condition parameter
OfferFull - Includes Offers plus merchant name or seller nickname.

Variations data management:

VariationMinimum
VariationSummary
Variations - Includes VariationMinimum and VariationSummary response groups plus other details

Plus various product attributes:

Paging through the Results

The ItemLookup operation retrieves ten items at a time. For each item, ECS returns a default number of offers, reviews, and variations. To access additional offers, reviews, and variations beyond the default number, you can make additional requests to ECS and use these three parameters:

Parameter	Default Page Number	Items per page	Valid Values	Description
OfferPage	1	10	1..100	Offers. Up to 100 pages of offers can be returned (10 offers per page).
ReviewPage	1	5	1..20	Reviews. Up to 20 pages of reviews (5 reviews per page) can be requested, one page at a time.
VariationPage	1	10	1..150	Variations. Up to 150 pages of child parents can be returned for this parent ASIN (10 child elements/variations per page).

If these parameters are omitted, only the first page of offers, reviews, and variations is returned. However the data also indicates the number of offers, reviews and variations available (and the number of pages) so that additional pages can be retrieved if desired.

Putting it all Together: Some ItemLookup Samples and Notes

ItemLookup Scenarios - US
ItemLookup Scenarios - UK
ItemLookup Scenarios - DE
ItemLookup Scenarios - JP
ItemLookup Scenarios - FR
ItemLookup Scenarios - CA
ItemLookup Notes

ItemLookup Scenarios - US

Scenario #1:

You want to get competitive pricing information for several products that are listed on Amazon. The products do not have variations. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345 
    &ResponseGroup=Request,Small,Offers
    &Condition=All 
    &MerchantId=All

Scenario #2:

You want to get pricing information on a list of music CDs sold by a specific competitor, but you also want to compare the length and number of tracks for the CDs. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345 
    &ResponseGroup=Request,Small,Offers,Tracks
    &Condition=New 
    &MerchantId=[ID]

Scenario #3:

You want to find a toy by its UPC and determine price and availability for collectibles from any vendor. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &IdType=UPC 
    &ItemId=[UPC]
    &SearchIndex=Toys 
    &ResponseGroup=Request,Small,Offers 
    &Condition=Collectible
    &MerchantId=All

Scenario #4:

You want to find in-store pickup for a particular gas grill. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &IdType=UPC 
    &ItemId=[UPC]
    &SearchIndex=OutdoorLiving 
    &DeliveryMethod=ISUP 
    &ISPUPostalCode=12345
    &ResponseGroup=Request,Small,Offers 
    &Condition=All 
    &MerchantId=All

Scenario #5:

You want to evaluate whether competitors are pricing products differently for different size/color combinations of certain types of apparel. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &IdType=SKU 
    &ItemId=[SKU1,SKU2,SKU3]
    &SearchIndex=Apparel 
    &ResponseGroup=Request,Small,Offers,Variations 
    &MerchantId=[ID]

Scenario #6:

You want to find out if a new book is available yet through Amazon. ReleaseDate is included in the Medium and ItemAttributes response groups. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,ItemAttributes,Offers

Note that since no condition is specified, only New books will be located; the vendor will be Amazon by default. It is not necessary to specify the search index, but single-index searches deliver results faster than searching Amazon's entire product database.

Scenario #7:

You find a scrap of paper with an Amazon ASIN written on it, and you don't know what it is, you just remember that it was something interesting. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]

Scenario #8:

You want to see all of the reviews for the bestseller that you wrote. Your sequence of REST requests might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,EditorialReview,Reviews,SalesRank

To see additional pages of customer reviews:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,Reviews 
    &ReviewPage=2

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID]
    &Operation=ItemLookup
    &ItemId=[ASIN]
    &SearchIndex=Books
    &ResponseGroup=Request,Reviews
    &ReviewPage=3

ItemLookup Scenarios - UK

The UK site permits lookups similar to the US site with the following differences:

UK site has SoftwareVideoGames search index
UK has HomeGarden store/search index
In the UK locale, you can search by ASIN, SKU, UPC.
UK site has no in-store pickup
UK site has no variations and no merchants

Scenario #1:

You want to get competitive pricing information for several products that are listed on Amazon. Your REST request might look like this:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345 
    &ResponseGroup=Request,Small,Offers
    &Condition=All 
    &MerchantId=All

Note that this will return only non-Amazon pricing. For Amazon pricing, you must submit the additional request:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345 
    &ResponseGroup=Request,Small,Offers

Since Amazon only sells New products, the Condition parameter is not necessary.

Scenario #2:

You want to get pricing information on a list of music CDs, but you also want to compare the length and number of tracks for the CDs. Your REST request might look like this:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345 
    &ResponseGroup=Request,Small,Offers,Tracks
    &Condition=New

Scenario #3:

You want to find a toy by its ASIN and determine price and availability for collectibles from any vendor. Your REST request might look like this:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Toys
    &ResponseGroup=Request,Small,Offers 
    &Condition=Collectible 
    &MerchantId=All

Scenario #4:

You want to find out if a new book is available yet through Amazon. ReleaseDate is included in the Medium and ItemAttributes response groups. Your REST request might look like this:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,ItemAttributes,Offers

Scenario #5:

You find a scrap of paper with an Amazon ASIN written on it, and you don't know what it is, you just remember that it was something interesting. Your REST request might look like this:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]

Scenario #6:

You want to see all of the reviews for the bestseller that you wrote. Your sequence of REST requests might look like this:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,EditorialReview,Reviews,SalesRank

To see additional pages of customer reviews:

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,Reviews 
    &ReviewPage=2

http://webservices.amazon.co.uk/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID]
    &Operation=ItemLookup
    &ItemId=[ASIN]
    &SearchIndex=Books
    &ResponseGroup=Request,Reviews
    &ReviewPage=3

ItemLookup Scenarios - DE

The DE site permits lookups similar to the US site with the following differences:

EAN search available, no SKU or UPC searches
HomeGarden store/search index
ForeignBooks store/search index for non-German language books
DE site has SoftwareVideoGames store/search index
DE site has no in-store pickup
DE site has no variations and no merchants

Scenario #1:

You want to get competitive pricing information for several products that are listed on Amazon. Your REST request might look like this:

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345 
    &ResponseGroup=Request,Small,Offers
    &Condition=All 
    &MerchantId=All

Scenario #2:

You want to get pricing information on a list of music CDs, but you also want to compare the length and number of tracks for the CDs. Your REST request might look like this:

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345 
    &ResponseGroup=Request,Small,Offers,Tracks
    &Condition=New

Scenario #3:

You want to find a toy by its EAN and determine price and availability for collectibles from any vendor. Your REST request might look like this:

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &IdType=EAN 
    &ItemId=[EAN]
    &SearchIndex=Toys 
    &ResponseGroup=Request,Small,Offers 
    &Condition=Collectible
    &MerchantId=All

Scenario #4:

You want to find out if a new book is available yet through Amazon. ReleaseDate is included in the Medium and ItemAttributes response groups. Your REST request might look like this:

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,ItemAttributes,Offers

Scenario #5:

You find a scrap of paper with an Amazon ASIN written on it, and you don't know what it is, you just remember that it was something interesting. Your REST request might look like this:

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]

Scenario #6:

You want to see all of the reviews for the bestseller that you wrote. Your sequence of REST requests might look like this:

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,EditorialReview,Reviews,SalesRank

To see additional pages of customer reviews:

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN] 
    &SearchIndex=Books
    &ResponseGroup=Request,Reviews 
    &ReviewPage=2

http://webservices.amazon.de/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID]
    &Operation=ItemLookup
    &ItemId=[ASIN]
    &SearchIndex=Books
    &ResponseGroup=Request,Reviews
    &ReviewPage=3

ItemLookup Scenarios - JP

The JP site permits lookups similar to the US site with the following differences:

EAN search (searches for JAN), no SKU or UPC searches
ForeignBooks store/search index for non-Japanese language books
JP site has no in-store pickup
JP site has no variations and no merchants

Scenario #1:

You want to get competitive pricing information for several products that are listed on Amazon. The products do not have variations. Your REST request might look like this:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345
    &ResponseGroup=Request,Small,Offers 
    &Condition=All
    &MerchantId=All

Scenario #2:

You want to get pricing information on a list of music CDs, but you also want to compare the length and number of tracks for the CDs. Your REST request might look like this:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345
    &ResponseGroup=Request,Small,Offers,Tracks
    &Condition=New

Scenario #3:

You want to find a toy by its EAN (JAN) and determine price and availability for collectibles from any vendor. Your REST request might look like this:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &IdType=EAN
    &ItemId=[EAN] 
    &SearchIndex=Toys 
    &ResponseGroup=Request,Small,Offers
    &Condition=Collectible 
    &MerchantId=All

Scenario #4:

You want to find out if a new book is available yet through Amazon. ReleaseDate is included in the Medium and ItemAttributes response groups. Your REST request might look like this:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]
    &SearchIndex=Books
    &ResponseGroup=Request,ItemAttributes,Offers

Scenario #5:

You find a scrap of paper with an Amazon ASIN written on it, and you don't know what it is, you just remember that it was something interesting. Your REST request might look like this:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup
    &ItemId=[ASIN]

Scenario #6:

You want to see all of the reviews for the bestseller that you wrote. Your sequence of REST requests might look like this:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]
    &SearchIndex=Books
    &ResponseGroup=Request,EditorialReview,Reviews,SalesRank

To see additional pages of customer reviews:

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]
    &SearchIndex=Books 
    &ResponseGroup=Request,Reviews
    &ReviewPage=2

http://webservices.amazon.co.jp/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]
    &SearchIndex=Books 
    &ResponseGroup=Request,Reviews
    &ReviewPage=3

ItemLookup Scenarios - FR

The FR site permits lookups similar to the US site with the following differences:

EAN search, no SKU or UPC searches
ForeignBooks store/search index for non-French language books
FR site has no in-store pickup
FR site has no variations and no merchants

Scenario #1:

You want to get competitive pricing information for several products that are listed on Amazon. The products do not have variations. Your REST request might look like this:

http://webservices.amazon.fr/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345
    &ResponseGroup=Request,Small,Offers 
    &Condition=All
    &MerchantId=All

Scenario #2:

You want to get pricing information on a list of music CDs, but you also want to compare the length and number of tracks for the CDs. Your REST request might look like this:

http://webservices.amazon.fr/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345
    &ResponseGroup=Request,Small,Offers,Tracks
    &Condition=New

Scenario #3:

You want to find out if a new book is available yet through Amazon. ReleaseDate is included in the Medium and ItemAttributes response groups. Your REST request might look like this:

http://webservices.amazon.fr/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=[ASIN]
    &SearchIndex=Books
    &ResponseGroup=Request,ItemAttributes,Offers

ItemLookup Scenarios - CA

The CA site permits lookups similar to the US site with the following differences:

EAN search, no SKU or UPC searches
ForeignBooks store/search index
CA site has no in-store pickup
CA site has no variations and no merchants

Scenario #1:

You want to get competitive pricing information for several products that are listed on Amazon. The products do not have variations. Your REST request might look like this:

http://webservices.amazon.ca/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345
    &ResponseGroup=Request,Small,Offers 
    &Condition=All
    &MerchantId=All

Scenario #2:

You want to get pricing information on a list of music CDs, but you also want to compare the length and number of tracks for the CDs. Your REST request might look like this:

http://webservices.amazon.ca/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=ItemLookup 
    &ItemId=ABC1,ABC2,P12345
    &ResponseGroup=Request,Small,Offers,Tracks
    &Condition=New

ItemLookup Notes

ItemLookup returns data similar to ListLookup. If you don't get the returned data that you expect, the most common culprit is a response group that does not include the data you require.

If you are attempting to find out if a product can be purchased, you must be sure to include the appropriate response group (Offers, OfferSummary or OfferFull).

For debugging purposes, no single response group returns all of the data. However for ItemLookup, setting the ResponseGroup parameter to include Large and Variations (US only) will return all available data. This may result in a very large response, but for debugging, it's an ideal way to look at all of the available data.

Looking up Similar Products

The SimilarityLookup operation is very similar to ItemLookup except that instead of looking up products, it looks up products that are similar to the specified product. SimilarityLookup does not work with UPC, SKU or EAN, it requires an ASIN(s).

SimilarityLookup returns up to ten similar products in an Items element, with an individual Item element for each similar product.

A SimilarityLookup request to look up similar products requires only one parameter:

ItemId ASIN of product to use for similarity lookup; insert multiple product ASINs as a comma-delimited list (REST) or multiple elements (SOAP).

By default, if multiple ASINs are provided to this operation, products are returned that are similar to ALL products in the request. SimilarityLookup can also retrieve an assortment of products that are similar to any of the items in the input list. To do this, you would use the parameters:

ItemId ASINs of products; comma-delimited list for REST, multiple elements for SOAP.

SimilarityType Random (Default value is Intersection.) Set the value of SimilarityType to Random if you want the list of similar products returned by SimilarityLookup to include an assortment of similar products corresponding to any of the items in the request.

SimilarityLookup behaves similarly to ItemLookup in filtering the product(s) returned to include only

Offers from a particular merchant(s)
Product offers in a specific condition (new, used, refurbished, collectible)
Delivery method (shipped or in-store pickup)

To filter your SimilarityLookup request, include the optional parameters below, as desired.

MerchantId All, Featured or a specific merchant ID. Setting the MerchantId parameter to Featured returns the same merchant that is displayed when you click the "Add to Shopping Cart" button on the product detail page of the Amazon Web site. The default value is Amazon.

Condition All, New, Used, Refurbished or Collectible - the default value is New

DeliveryMethod Ship or ISPU (in-store pickup) - the default value is Ship. This parameter is available in the US only.

ISPUPostalCode If the DeliveryMethod parameter is set to ISPU, then this parameter is required and its value should be the zip code of the area where in-store pickup is requested.

The SimilarityLookup operation supports the ResponseGroup parameter with the same values as are available for ItemLookup.

SimilarityLookup Samples and Notes

Scenario #1:

You have a single ASIN and you want to find products similar to it. Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=SimilarityLookup 
    &ItemId=ABC1
    &ResponseGroup=Request,Small,Offers 
    &Condition=All
    &MerchantId=All

Scenario #2:

You want to find products similar to a group of products (e.g., a book, an appliance, some apparel). Your REST request might look like this:

http://webservices.amazon.com/onca/xml?Service=AWSECommerceService
    &AWSAccessKeyId=[ID] 
    &Operation=SimilarityLookup
    &ItemId=ABC1,ABC2,ABC3 
    &ResponseGroup=Request,Small,Offers
    &Condition=All 
    &MerchantId=All

Except for the site name at the start of the request, these sample requests are the same for all of the Amazon Web sites. Note that a single ASIN typically does not represent the same product on all sites.

Similar products will be returned only if they are available in the Amazon database. You may also want to try looking for accessories or using browse nodes to try to find related products.

SimilarityLookup does not allow you to page through results, it simply returns up to ten items.

IdType	SKU
ItemId	The product identifier to be searched for; for multiple products, insert a comma-delimited list (REST) or multiple elements (SOAP).
MerchantId	SKUs are unique to a particular merchant. In order to ensure you retrieve the exact product you desire, you must always include a merchant ID in your request when you look up an item by SKU.

IdType	EAN (Note: EAN or European Article Number is the same as JAN or Japanese Article Number).
ItemId	The product identifier to be searched for; for multiple products, insert a comma-delimited list (REST) or multiple elements (SOAP).
SearchIndex	The name of the Amazon store that the product associated with the EAN belongs to. See Search Index Values for the SearchIndex values.

MerchantId	All returns offer data for all merchants including Amazon. MerchantId is an alphanumeric identity that specifies a merchant. It can have three settings: All, in which all merchants are included in the response, an alphanumeric identity that specifies a single merchant, or FeaturedBuyBoxMerchant, which returns the merchant identified as the “Buy Box Winner” on a specific detail page. The "Buy Box Winner" is the merchant associated with the sale of the item listed in the Buy Box, which is the box on an item's detail page that enables you to add an item to a shopping cart. The default value for MerchantId is “Amazon.” If this parameter is omitted, the default is Amazon.
Condition	All, New, Used, Refurbished or Collectible - the default is New
DeliveryMethod	Ship or ISPU (in-store pickup) - Ship is the default. ISPU applies to the US only.
ISPUPostalCode	If the DeliveryMethod parameter is set to ISPU, then this parameter is required and its value should be the zip code of the area where in-store pickup is requested.

ItemId	ASINs of products; comma-delimited list for REST, multiple elements for SOAP.
SimilarityType	Random (Default value is Intersection.) Set the value of SimilarityType to Random if you want the list of similar products returned by SimilarityLookup to include an assortment of similar products corresponding to any of the items in the request.

MerchantId	All, Featured or a specific merchant ID. Setting the MerchantId parameter to Featured returns the same merchant that is displayed when you click the "Add to Shopping Cart" button on the product detail page of the Amazon Web site. The default value is Amazon.
Condition	All, New, Used, Refurbished or Collectible - the default value is New
DeliveryMethod	Ship or ISPU (in-store pickup) - the default value is Ship. This parameter is available in the US only.
ISPUPostalCode	If the DeliveryMethod parameter is set to ISPU, then this parameter is required and its value should be the zip code of the area where in-store pickup is requested.