The browse item endpoint accepts a list of items and returns a standard browse response structure. Additional filters may be passed in the request, but custom sort orders are not supported (items will always be returned in the order of ids that are specified in the request).

The browse items endpoint is designed for fast lookup of item data in production where performance and scalability are critical. It is used by customers in contexts such as: retrieving data for products returned on a homepage with representative store pricing, supplementing result pages with data for items placed from alternate systems such as ad servers, or supporting product detail pages (PDP) in cases where additional product-specific enrichment is not required. While the endpoint is not specialized for PDP, it can be suitable when the same metadata used on product listing pages (PLP) is sufficient, e.g. Price or Availability. Typically, customers use this capability where the responses from their eCommerce platform are not sufficiently performant, or don't support store or regional pricing. The browse items endpoint does not return results for items that have not yet been indexed.

In contrast, the items ingestion API retrieves any item that has been uploaded to a customer's index, even if it hasn't yet been indexed. It is intended only for integration and backend usage, requires authentication and has more aggressive rate limiting -- it is not designed for end-users. The endpoint also does not support filter logic.

The browse items endpoint is something of a special use case and is not leveraged by most customers (most customers will use their eCommerce platform for this case). Rather, most customers and browse contexts (browse a brand or category or collection) will utilize the standard browse endpoint.

Related content

• Variations mapping
• Pre-filter expressions
• Filter names & values
• Results response structure