Search

# Search Search documentation covers product search, listing, facets, autocomplete, app-scoped Search GraphQL context, generated Search documents, and React SDK search surfaces. ## Current ownership - Start with Search API for new storefront product discovery, listing, facets, and autocomplete work. - Use the [Shopper API](/apis/shopper/latest) only when you specifically need the current public REST read endpoint surface. - Search schema truth, generated documents, generated types, and SDK helper coverage come from `enad-packages` artifacts. - docs-v3 owns public guidance, route selection, AI-readable summaries, and source-of-truth boundaries. - Public package docs should link to stable docs-v3 routes instead of deep-linking to generated internals. - Search-backed runtime examples and visual experimentation remain in the playground: [sdk.enad.io/sandbox](https://sdk.enad.io/sandbox). ## Start here - [Search GraphQL latest](/search/latest): primary guide for new storefront discovery work, including endpoint context, `createSearchClient()`, current helper coverage, generated documents, fragment notes, React runtime boundary, and the schema-introspecting Search GraphQL playground. - [Search GraphQL reference latest](/reference/search-graphql/latest): public reference-compatible route for package docs, tools, and AI agents that need a stable Search GraphQL reference URL. - [TypeScript SDK latest](/ts-sdk/latest): package-level entry point for `@enadhq/enad-ts-sdk`, including the Search package surface. - [React product listing and search](/react-sdk/latest/guides/product-listing-search): PLP, filters, autocomplete, connected Search UI, and provider-backed runtime guidance. - [Commerce components](/react-sdk/latest/components/commerce): search bars, autocomplete, search panels, and Search product components. - [API and Search AI guide](/ai/apis/latest): AI-safe Search routing and source-of-truth rules. ## What this section covers - How Search GraphQL is scoped by app, market, store group, and locale. - When to use named `SearchClient` helpers versus generated Search documents. - Product, facet, brand, series, category, collection, autocomplete, and slug lookup route selection. - Compatibility notes for top-level `warehouseSlug`, rich product fragments, variant group data, and price fields. - React SDK guidance for keeping provider context separate from shopper-facing Search UI. ## Public route stability Use `/search/latest` as the canonical public Search guidance route for new discovery-heavy storefront work. Use `/reference/search-graphql/latest` when a stable reference-compatible URL is needed, while remembering it is source-pending guidance rather than a generated GraphQL schema reference. Keep exact Search schema truth in generated `enad-packages` artifacts instead of hand-authored docs prose.