Release: Product Advertising API on 2009-05-07

Release Notes>Product Advertising API>Release: Product Advertising API on 2009 05 07
New branding and new request authorization narrative.

Details

Submitted By: scotmaws
Release Date: May 7, 2009 12:00 AM GMT
Latest Version: 2009-03-31
Latest WSDL: http://ecs.amazonaws.com/AWSECommerceService/2009-03-31/AWSECommerceService.wsdl
Created On: April 29, 2009 2:22 PM GMT
Last Updated: May 7, 2009 9:11 PM GMT

These release notes provide a summary of all New Features, Resolved Issues, and Known Issues in this version of the Product Advertising API. For changes made in previous Product Advertising API versions, go to http://aws.amazon.com/resources.

New Features

The following list describes the new features found in this release.

  • Service name change. This service is called the Product Advertising API.
  • Added narrative about request authentication.

 

Known Issues

The following table describes irregular behavior seen in this release of the Product Advertising API.

Issue Description Impact
RelatedItemsCount is greater than the number of related items returned. The response element, RelatedItemsCount returns the number of related items found. The number of related items returned, however, can be less because not all of the related items found are necessarily available for purchase. Do not programmatically use RealtedItemsCount to iteratively return results.
When using the KindleStore search index, the BrowsenodeId parameter has no effect. In an ItemSearch request that uses a KindleStore search index, the BrowsenodeId parameter has no effect. Avoid using the BrowsenodeId parameter in ItemSearch requests when using the KindleStore search index.
Author parameter for Books index is not working as expected when you use quotes. Typically, you use quotation marks around one or more words to get exact results. When you use quotation marks around an author's name in an ItemSearch request, the Product Advertising API does not always return all of the results for the specified author. Do not use quotes around an Author's name when the search index is Books..
In the JP locale, the Sort parameter value, release-date, does not work correctly when the search index is VideoGames. Items sorted by release-date should be returned in chronological order. This is not the case when the search index is VideoGames. If you need to return video games chronologically according to release-date, you will need to post-process the response elements. Otherwise, your items video games will not be sorted correctly.
The EAN field does not support ISBN-13 in the JP locale. ISBN numbers have increased to 13 digits. The existing EAN field can hold 13 digits. ItemSearch requests using the EAN field this way, however, return inaccurate results. JP locale ItemSearch requests cannot use the EAN field for the ISBN number. <he wo> The workaround is to use the "ISBN" for the IdType parameter in an ItemLookup request. In this case, the ItemId is the ISBN number of a book. The ISBN value works only with the Book search index.
ItemSearch using Browsenodes when the search index is PetSupplies does not work correctly. ItemSearch requests are inaccurate when the Browsenodes parameter is used and the search index is PetSupplies. You cannot use the Browsenodes parameter when you set the search index to PetSupplies in an ItemSearch request. The work around is to use the Kitchen search index instead of PetSupplies.
The BrowseNodeLookup operation often returns inaccurate results for top sellers when the browse node in the request is the root node of a category. Browsenode lookup is often used to find the top seller in the browsenode category. When the browsenode is at the top of the category, the top sellers list is inaccurate. Do not use the top root browse node in a category to find top sellers. The workaround is to use one of the child browse nodes with the TopSellers response group.
The ListFull and ListInfo response groups sometimes return an incorrect value for TotalItems. The discrepancy arises when the response sometimes includes invalid ASINs as part of the total. Applications trying to use TotalItems programmatically can run into problems.
Items returned by ItemSearch may have prices that fall outside of the range specified by MaximumPrice and MinimumPrice. The ItemSearch parameters, MaximumPrice and MinimumPrice, should limit the items returned according to the specified price range. Sometimes, items are returned whose prices fall outside of the specified range. ItemSearch requests that use both MaximumPrice and MinimumPrice should limit the items returned according to the specified price range.
ItemSearch requests based on Actor or Director return the same results. The source data in the database does not distinguish between actors and directors. Do not use ItemSearch requests based on Actor or Director.
Salesrank values in the CA and EU locales do not match the values returned by the retail web site in those locales. Salesrank values given by the Product Advertising API and Amazon's retail web site differ from those given, at times, in the CA and EU locales. Do not use ItemSearch requests sorted by Salesrank.
Not all parent browse nodes are returned by BrowseNodeInfo. The response group, BrowseNodeInfo, used in BrowseNodeLookup requests returns the child and parent browse nodes of the browse node specified in the request. When a browse node has multiple parents, however, only one of the parent browse nodes is returned in the response. That is why there might be a difference between the Product Advertising API response and the result displayed on Amazon’s retail web site. BrowseNodeInfo returns the entire lineage of both child and parent browse nodes. For example, in the following response snippet, the parentage of the browse node in the request, Social Sciences, is traced all the way up the browse node tree to the root browse node, Books. Also, all of the children of the node, Social Sciences, are returned. For the sake of brevity, the following response snippet shows only some of the returned child browse nodes.

<Item>
<ASIN>0131856340</ASIN>
-<BrowseNodes>
  -<BrowseNode>
   <BrowseNodeId>11232</BrowseNodeId>
   <Name> Social Sciences</Name>
     -<Ancestors>
      -<BrowseNode>
      <BrowseNodeId>53</BrowseNodeId>
      <Name>Nonfiction</Name>
      -<Ancestors>
       -<BrowseNode>
       <BrowseNodeId>1000</BrowseNodeId>
       <Name>Subjects</Name>
      -<Ancestors>
        -<BrowseNode>
        <BrowseNodeId>283155</BrowseNodeId>
        <Name>Books</Name>
      </BrowseNode>
    </BrowseNode>
  </BrowseNode>
- <Children>
  - <BrowseNode>
      <BrowseNodeId>11233</BrowseNodeId>
      <Name>Anthropology</Name>
    </BrowseNode>
  - <BrowseNode>
      <BrowseNodeId>11242</BrowseNodeId>
      <Name>Archaeology</Name>
    </BrowseNode>
  - <BrowseNode>
      <BrowseNodeId>3048861</BrowseNodeId>
      <Name>Children's Studies</Name>
    </BrowseNode>
  </Children>
</BrowseNodes>

Notice that all of the nodes in the response show only one parent node, for example, the parent node of Social Sciences is Nonfiction. Only a single parent node would be returned even if a node had multiple parents.
Do not use BrowsenodeLookups that attempt to work "up" the browsenode hierarchy.
Items sorted by salesrank are returned out of order. In an ItemSearch request where Sort=salesrank, you would expect the items to be returned in order of their sales rank from best (1) to worst (large number). The sales rank values for items change frequently. The Product Advertising API sales rank updates lag behind the sales rank updates on the retail web site. So, in an ItemSearch request, although the sales rank numbers are out of order in the Product Advertising API response, the items are, in fact, ordered according to the sales rank computed on the retail web site. In this way, the sales rank order of items returned by the Product Advertising API and Amazon’s retail web site match. One alternative in the US locale is to use the TopSellers response group to get the top 10 bestsellers. Those items are returned in order. Do not use ItemSearch requests that are sorted by Salesrank.
ItemSearch power searches sometimes return different results when the sort parameter is specified versus when it is not specified. Submitting the same request twice, once with and once without the sort parameter, potentially returns different sets of results. Submit multiple ItemSearch power searches to verify answers.
The parameter, pubdate, which is used in ItemSearch Power searches is not working correctly. This parameter sometimes does not return results for the specified pubdate value when it should. Do not use ItemSearch power searches that use pubdate.
Changing access to lists often requires up to twenty-four hours to take effect. Only lists made public by a customer are returned by ListSearch. A customer can change access restrictions on their lists. There is a lag time between that change and the time when others can or cannot (depending on the change in permissions) access that list. Do not use submit ListSearch requests within 24 hours of when access permissions were changed.
Relevancy rank does not work with blended searches. Relevancy rank generally corresponds with sales rank. Currently, the relevancy rank using ItemSearch blended searches yields inaccurate results. Do not use ItemSearch requests where the SearchIndex is "Blended" and the sort parameter is relevancy.
Updating the availability status of some items takes exceptionally long. There is a lag time incurred for the availability status of an item to be updated. For a few items in each Search Index, however, those lag times are exceptionally long.  These lag times account for inaccurate availability information, even when the ItemSearch parameter, Availability, is set to "Available." To check the true availability of an item, use the Offers Response Group. If an offer is returned for an item, it is truly available. Do not use requests that list the availability of items in the response.
GZIP functionality not working. XML responses are not GZIPed, even if the proper Accept-Encoding header is sent with the request. Do not use requests that stipulate a GZIPed response.
The total number of pages returned from a search request decreases as you page through the results. To optimize search results, grouping of similar items is not done until the items are viewed. When the items are viewed and the grouping occurs, the page count shrinks. Do not use a pplications or web sites that make use of the TotalPages element.
Relevancy score values are sometimes unexpected. Relevancy scores are, in part, determined by the number of occurrences of a word. This algorithm can sometimes lead to unexpected results. For example, while you might expect "laptop" to be most relevant to Computers category, the relevancy score is higher in "Sporting Goods" because the word "laptop" occurs there more often, for example, in phrases such as "laptop bag." Do not use ItemSearch requests sorted by relevancy.
In cart operations, validation is not performed on ListItemId. Validation is not performed in some cart operations. It is possible, for example, for the ListItemId not to correspond to the ASIN. Do not add items to a cart using a ListItemId.
The ItemSearch parameter, MerchantId, does not work with the following search indices: books, wireless, communities, wishlists, Target, and all international stores. Using. MerchantId with these search indices can lead to unexpected results, such as the return of items being sold by some merchant other than the one specified by MerchantId. Do not use MerchantId in ItemSearch requests that also use the unsupported search indices.
SellerLookup sometimes does not return the Seller Name or correct location. Results from the SellerLookup operation may not return the SellerName element or return the correct Location values. Do not use applications or web sites that use the SellerName or Location values.
ItemLookup does not return some editorial reviews. ItemLookup only returns the editorial reviews written by Amazon.com. Editorial reviews recorded by another web site cannot be included in the reviews returned by ItemLookup.
Feature elements are missing from ItemAttributes. The Product Advertising API does not return the Feature element, which was returned by Amazon Associates Web Service 3.0, for ItemAttributes. Do not use applications or web sites that use the 3.0 Feature element.
Items returned using the PCHardware search index may not be hardware. Using the PCHardware search index with the ItemSearch operation returns non-hardware items. Examine the results carefully when using the PCHardware search index.
ItemSearch Power requests do not return accurate results for specific dates. ItemSearch responses may be incorrect when the request specifies a specific day. Using date ranges returns expected results. Do not look for specific dates in ItemSearch Power requests.
WishList is returned even when ListType=WeddingRegistry. In ListLookup, when you set ListType to “WeddingRegistry,” the operation returns both a WeddingRegistry and, unexpectedly, a WishList. Both lists are based on the same ListId. When you set ListType to “WishList,” ListLookup only returns a WishList, which is correct. Do not use ListLookup requests that set ListType to "WeddingRegistry."
Customer Reviews are not in sync with Amazon's retail web site. Customer Reviews returned by search operations may not be in sync with the reviews on Amazon's retail web site. Do not use applications that return customer reviews.
ReleaseDate not returned for some items. Some items, such as DVDs, do not have release dates. Sorting by release date, then, sometimes generates spurious results. Do not use applications or web sites that use the ReleaseDate element.
Phrases in quotes used as values for the Keywords parameter in ItemSearch requests do not perform as expected. Quoted phrases in the Keywords field for ItemSearch are not accepted as a whole phrase. Instead, they are broken up into individual terms and results are returned for subsets of the phrase. For example, the parameter Keywords="the last time" should only return results for "the last time", rather than "the", "last" or "time". Do not use ItemSearch requests that use phrases for Keyword values. Instead, use the TextStream parameter.
Default input content encoding is not UTF-8. JP is the only locale that correctly takes UTF8 input. All other locales use LATIN1. Do not use applications dependent on UTF8.
ItemSearch using TextStream may not work for all search indices. Some search indices, such as, Tools, Software, and Jewelry, do not work in ItemSearch requests using the TextStream parameter. Do not use applications or web sites that use the TextStream parameter.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.