Fetch, filter, sort, and paginate merchandised collection pages in your catalog using our powerful browse api.
<YOUR_LAYERS_TOKEN>.first_or_matched_variant field. This is useful for scenarios like defaulting to a specific birthstone option in a jewelry collection.Behavior:first_or_matched_variant field in the responseid, title, handle, body_html, vendor, product_type, tags, images, available, created_at, updated_at, published_at, price_range, options, original_options, metafields, named_tags, calculated, category, featured_media, is_gift_card, has_variants_that_require_components, combined_listing_parent_product_id, combined_listing_role, first_or_matched_variant, and variants. See the Product Schema for detailed descriptions."vendor", "options.Size") and wildcard patterns (e.g., "options.*", "metafields.product.*").Wildcard patterns expand to all matching attribute codes. For example, "options.*" expands to all option facets like "options.Size" and "options.Color". Wildcards must match at least one attribute code to be valid.Examples:retrieveFacetCount is true then an object with keys and values of the specified attributes. When variant breakouts are enabled, facet counts reflect tile counts rather than product counts.includeFacetRanges is true then an object with keys of the facet attribute code and value is an object with min/max.__typename field to identify the tile type:
"Product" - A standard product tile"Variant" - An individual variant tile from a product with a configured breakout optionid field.id field contains the variant ID (not the product ID). The title field is formatted as "{product title} - {option value}" by default (e.g., “Amethyst Ring - Rose Quartz”), but this can be configured per breakout. If the breakout’s “Include Option Value in Title” setting is disabled, the title will be the original product title. See the Variant Breakouts documentation for more details.