Using the Browse API, you can create a rich selection of items for your buyers to browse with keyword and category searches.
Browse API resources
The Browse API has the following resources:
- item_summary – basic information for an item or a group of items, such as title, pricing, images, shipping, and seller. It also includes refinements, such as item condition, buy options, category, and item aspects (color, brand, size, etc.).
- item - detailed information for a purchasable items to enable users to make buying decisions. In addition to the basic item information and providing additional information about shipping, seller, etc., the item details include product review data, item location, return policy terms, and more. This resource also provides a bridge between the RESTful Buy APIs and the legacy APIs, such as Trading and Finding.
The Browse API is designed to be used together with the Buy APIs to create cohesive shopping, browsing, buying applications. For example, your buyers can have a seamless buying experience woven into a social application. This section outlines the high-level use cases for the Browse API.
Find eBay items using search
You can find exactly the items you want to show to your shoppers by searching for items by keyword, category, eBay product ID (EPID), or GTIN. Or a combination of these.
Refine the search results
You can control what is returned by the search using the fieldgroups field. By default, search returns matching items. But in addition to or instead of returning items, you can choose to return the aspects (all the variations of an item such and color and size), buying options (fixed or auction), conditions, and categories of the items found. These are known as refinements. This information enables you to create histograms, which enables shoppers to drill down in each refinement narrowing the search results.
Filter the search results by item aspects
You can use the information returned in aspectDistributions to filter the results by specific aspects, such as brand.
Filter the search results by field values
You can use field filters to refine the results based on the value returned in a field, such as listing format, item condition, price range, UPC value, listing end date, location, and more. You can use multiple filters in a single call. For details about, see search Call Field Filters.
Get the details of each item in a group or a specific item
When the item has variations, you can retrieve the details of the individual items in an item group. You can also retrieve the details of a specific item.
Get item details using a legacy item ID or SKU
You can use the item IDs returned by eBay legacy APIs, such as Trading, Shopping, and Finding, to retrieve the details of the item and the RESTful item ID, which you can use with all the Buy API calls.
Please note the following constraints for the Browse API.
The Buy APIs identifiers for item and order do not match the identifiers used on the eBay site and in buyer emails. So you cannot use the Buy APIs identifiers with any of the eBay legacy APIs, such as Trading and Finding. But you can use the eBay legacy item identifiers in the Browse API getItemByLegacyId call to retrieve items. For details, see the Legacy API compatibility overview in the Buying Integration Guide.
The Browse API is currently supported on the following eBay sites:
- EBAY-AU - Australia (ebay.com/au)
- EBAY-CA - Canada (English) (ebay.ca)
- EBAY-DE - Germany (ebay.de)
- EBAY-ES - Spain (ebay.es)
- EBAY-FR - France (ebay.fr)
- EBAY-IT - Italy (ebay.it)
- EBAY-UK - Great Britain (ebay.co.uk)
- EBAY-US - USA (ebay.com)
search call limit and restriction
The search call can return a maximum of 10,000 items and you cannot use the wildcard
* in the search call request.
eBay policies and rules
Although the eBay Buy APIs are available for anyone to use in eBay's sandbox environment, use of the APIs in production is restricted. Users must meet standard eligibility requirements, get approvals from eBay support organizations, and sign contracts with eBay and PayPal to access the Buy APIs in production.
See Buy APIs Requirements in the Buying Integration Guide for more information.