Browsenodeinfo Response Group - Amazon Product Advertising API Developer's Manual

Product Advertising API Developer Guide
<Title>Harry Potter and the Half-Blood Prince (Book 6)</Title>
<Binding>Audio CD</Binding>
</AlternateVersion>
<AlternateVersion>
<ASIN>0439785960</ASIN>
<Title>
Harry Potter And The Half-Blood Prince (Harry Potter, Book 6) (Harry Potter)
</Title>
<Binding>Paperback</Binding>
</AlternateVersion>
<AlternateVersion>
<ASIN>0439786770</ASIN>
<Title>
Harry Potter and the Half-Blood Prince (Book 6) [LIBRARY EDITION]
</Title>
<Binding>Library Binding</Binding>
</AlternateVersion>

BrowseNodeInfo Response Group

For a given browse node ID, the BrowseNodeInfo response group returns the browse node name and
ID of the child and parent browse nodes.
One application of this information is to use the child and parent browse nodes to traverse the browse
node hierarchy to either refine a search (child nodes) or to generalize a search (parent nodes). You do
that using BrowseNodeLookup (p. 165)
highly targeted results. Generalizing a response enables you to find what product category a browse
node belongs to.
This response group is similar to the
BrowseNodes response group is used with operations, including
and SimilarityLookup (p. 206), that are based on item attributes, search indices, and lists, and potentially
return multiple items. BrowseNodeInfo can only be used with
is always keyed on a browse node ID.
Relevant Operations
Operations that can use this response group include:
• BrowseNodeLookup (p. 165)
Response Elements
The following table describes the elements returned by BrowseNodeInfo.
• BrowseNodeId (p. 298)
• Name (p. 306)
As you can see from this table, BrowseNodeInfo returns the identity of child and parent browse nodes.
That information is typically used with
BrowseNodeInfo Response Group
one or more times. Refining a search enables you to return more
BrowseNodes (p. 219)
BrowseNodeLookup (p. 165)
API Version 2011-08-01
217
response group. The difference is that the
ItemSearch (p. 196), ItemLookup (p.
BrowseNodeLookup (p. 165)
to traverse the browse node hierarchy.
189),
and the search