Start from the job your application or agent needs to perform. Use the matching API page for setup, auth model, and runtime placement; use reference pages for methods, paths, fields, status codes, and schema details.

Start with the job

• New storefront discovery, product listing, facets, autocomplete, or MCP search.* reads: start with Search. Use Search GraphQL reference for fields, inputs, enums, and operation documents.
• Existing REST storefront catalog reads: start with Shopper API. Use Shopper OpenAPI for methods, paths, parameters, and schemas.
• Trusted catalog, order, channel, market, warehouse, or DAM administration: start with Management API. Use Management OpenAPI for operation details.
• Customer identity, sessions, saved carts, wishlists, account orders, or customer-group price reads: start with Auth API. Use Auth reference for endpoint details.
• Integration records, setup checks, stats, webhook settings, or sync jobs: start with Integrations. Use Integrations reference for endpoint details.
• Public folders, media search, folder facets, or shareable-link reads: start with Media/DAM. Use DAM public reads for endpoint details.
• Agent docs tools, OAuth setup, public capability discovery, or governed tool use: start with MCP server. Use the API, Search, Media, or DAM reference for the affected data.

Available APIs

• Management API: trusted server-side catalog, commerce, DAM administration, channels, warehouses, organizations, and operator workflows.
• Auth API: identity, sessions, carts, orders, wishlists, organisations, customer groups, and account attributes in signed-in customer flows.
• Shopper API: existing public REST storefront reads for clients that already depend on the Shopper route shape.
• Integrations API: connector records, setup checks, stats, sync creation, and sync status.
• Media/DAM: public folder browsing, media search, facets, shareable-link consumption, and DAM administration routing.
• Search GraphQL: new storefront discovery, filters, facets, autocomplete, listing reads, and agent read workflows.
• MCP server: agent setup, capability discovery, OAuth expectations, governed tool use, and where MCP fits with APIs.

Reference shortcuts

When you already know what you are building, open the page that matches the detail you need:

• REST operation method, path, parameters, schemas, or status codes: open Reference or OpenAPI references.
• Product work that crosses storefront and admin boundaries: open Products reference.
• Order work that crosses Management writes, Auth reads, and events: open Orders and order lines.
• Auth signup, login, refresh, verification, or signed-in state: open Auth reference.
• Integration records and sync lifecycle: open Integrations reference.
• Search fields, inputs, enums, fragments, and operation documents: open Search GraphQL reference, schema, or documents.

Start new storefront read and discovery work from Search GraphQL before falling back to Shopper REST compatibility. Follow the overall policy in Versioning.