Start here when you already know the job and want the fastest route into the right reference.

Start here

• Need exact REST request or response details now -> open the subject hub first, then confirm the exact endpoint or OpenAPI spec.
• Need Search GraphQL guidance or helper coverage -> start at Search GraphQL reference.
• Need exact Search fields, inputs, enums, fragments, operations, nullability, or types -> use the Search GraphQL reference and raw Search SDL/documents.
• Not sure which API owns the work yet -> start at /apis before choosing a reference hub.
• Need broader Search setup or runtime context before reference lookup -> start at /search/latest.

Fast paths into common hubs

• Products - Start here for product lookup, browse, pricing, and catalog detail work that may cross Search, Shopper, and Management boundaries.
• Variants - Use for variant detail, stock, inventory, and pricing work across shopper reads and management updates.
• Categories - Use for category tree, category-product, and taxonomy routing across storefront and management surfaces.
• Collections - Use for collection browse, membership, and merchandising work.
• Orders - Start here for order lookup and order-management work, then confirm whether the exact endpoint belongs to auth or management flows.
• Auth - Use for login, registration, password, refresh-token, and email-verification endpoints.
• DAM - Use for DAM folders, media placement, and shareable-link endpoints.
• OpenAPI specs - Use when you already know the API or need schema-level detail across a complete contract.

Contract ownership

• REST hubs and OpenAPI specs own exact REST endpoint contracts.
• Search GraphQL reference owns the Search schema and operation reference. Exact Search fields, inputs, enum values, nullability, operation documents, fragments, and TypeScript types stay in the Search reference and SDK package types.