Execute a search asynchronously allowing further personalization to run in the background during a redirect or page load.
search_id that can be used with the Search API to execute the search.
search_id body parameter<YOUR_LAYERS_TOKEN>. Same requirements as the Search API.id, 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, and first_or_matched_variant. See the Product Schemafor 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:search_idsearch_id that identifies the prepared search| Header | Description |
|---|---|
x-request-id | A unique identifier (ULID) for the request. Use it to correlate requests across your infrastructure or when contacting support. |
x-layers-build | The Layers build version that served the request. |
X-Storefront-Access-Tokensearch_id with the Search API in the search_id body parameter to execute an optimized search.