Search handles discovery. Use it when you add product grids, filters, facets, autocomplete, SDK-backed views, or storefront handoffs that need app, market, store group, and locale context. Open Search GraphQL reference for schema fields, variables, fragments, enums, and operation documents.
- New storefront reads and discovery: Search GraphQL latest. Search GraphQL is the preferred surface for new storefront reads and discovery.
- Existing REST clients: Shopper API, only when the public REST read compatibility surface is required.
- Exact contract detail: Search GraphQL reference latest for fields, variables, fragments, enums, operations, and raw schema files.
- Package behavior: SDK package reference for exports, generated types, helper names, and runtime behavior.
- Live examples: sdk.enad.io/sandbox.
- Search GraphQL latest: endpoint context,
createSearchClient(), helper coverage, operations, fragments, React boundaries, and playground usage.
- Search GraphQL reference latest: schema and operation detail.
- TypeScript SDK latest: package-level entry point for
@enadhq/enad-ts-sdk and its Search package surface.
- React product listing and search: PLP filters, autocomplete, connected UI, and provider-backed runtime guidance.
- Commerce components: search bars, autocomplete, search panels, and product components.
- API and Search agent guide: agent-safe routing across APIs, Search, Media, Events, and MCP.
- App, market, store-group, and locale context for storefront discovery.
- When to call named
SearchClient helpers and when to use generated documents directly.
- Route choice for products, facets, brands, series, categories, collections, autocomplete, and slug lookup.
- Compatibility notes for top-level
warehouseSlug, rich product fragments, variant group data, and price fields.
- React guidance for keeping provider context separate from shopper-facing UI.
Use /search/latest as the canonical public guide for new discovery-heavy storefront work. Use /reference/search-graphql/latest when exact schema or operation detail matters.
Search
# Search
Search handles discovery. Use it when you add product grids, filters, facets, autocomplete, SDK-backed views, or storefront handoffs that need app, market, store group, and locale context. Open Search GraphQL reference for schema fields, variables, fragments, enums, and operation documents.
## Start by job
- New storefront reads and discovery: [Search GraphQL latest](/search/latest). Search GraphQL is the preferred surface for new storefront reads and discovery.
- Existing REST clients: [Shopper API](/apis/shopper/latest), only when the public REST read compatibility surface is required.
- Exact contract detail: [Search GraphQL reference latest](/reference/search-graphql/latest) for fields, variables, fragments, enums, operations, and raw schema files.
- Package behavior: SDK package reference for exports, generated types, helper names, and runtime behavior.
- Live examples: [sdk.enad.io/sandbox](https://sdk.enad.io/sandbox).
## Starting points
- [Search GraphQL latest](/search/latest): endpoint context, `createSearchClient()`, helper coverage, operations, fragments, React boundaries, and playground usage.
- [Search GraphQL reference latest](/reference/search-graphql/latest): schema and operation detail.
- [TypeScript SDK latest](/ts-sdk/latest): package-level entry point for `@enadhq/enad-ts-sdk` and its Search package surface.
- [React product listing and search](/react-sdk/latest/guides/product-listing-search): PLP filters, autocomplete, connected UI, and provider-backed runtime guidance.
- [Commerce components](/react-sdk/latest/components/commerce): search bars, autocomplete, search panels, and product components.
- [API and Search agent guide](/ai/apis/latest): agent-safe routing across APIs, Search, Media, Events, and MCP.
## Core concepts
- App, market, store-group, and locale context for storefront discovery.
- When to call named `SearchClient` helpers and when to use generated documents directly.
- Route choice for products, facets, brands, series, categories, collections, autocomplete, and slug lookup.
- Compatibility notes for top-level `warehouseSlug`, rich product fragments, variant group data, and price fields.
- React guidance for keeping provider context separate from shopper-facing UI.
## Public route stability
Use `/search/latest` as the canonical public guide for new discovery-heavy storefront work. Use `/reference/search-graphql/latest` when exact schema or operation detail matters.