DocsDocsHome
Developer portal

Choose the Enad surface that matches the job.

Start from the caller and workflow, then move into the SDK, API, Search schema, event catalog, MCP guide, or operation reference that owns the implementation details.

Start with conceptsChoose APIAPI reference
Fast starts
Start hereEssential conceptsLearn the Enad model before choosing an SDK, API, or agent route.Frontend teamsReact storefrontSet up the React SDK, provider boundary, theme, and storefront composition.Backend teamsAPI chooserFind the API or reference page that matches the request you need to make.AgentsAgent setupLoad the short agent index, MCP setup, and manifest when an agent needs context.

Find the right starting point

Start with the area that matches the work, then move into reference when you need exact methods, fields, auth, or response behavior.

Getting started

Concepts, versioning, troubleshooting, and surface selection.

StartHow Enad worksVersioning

Build

SDK, Search, media, event, and integration implementation guides.

SDKsSearchMedia/DAMIntegrations

Technical

REST endpoints, Search GraphQL, OpenAPI specs, and reference routes.

ReferenceOpenAPI specs

Agentic Flows

Agent guidance, MCP setup, manifests, and compact context files.

AgentsMCP server

Learn

Implementation writing that explains tradeoffs without replacing reference contracts.

BlogChoosing a surface

API references

Open these when you already know which service you are calling, or when a guide sends you to the contract.

Management API

Administrative writes and operational reads.

Shopper API

Storefront reads and shopper-owned flows.

Auth API

Authentication and account access routes.

DAM public reads

Public asset-library browsing and lookup.

Integrations API

Connected services and integration workflows.

I want to...

Learn how Enad worksProduct, app, market, and runtime model.Choose an SDKReact storefronts or server-side TypeScript work.Pick an APICaller, auth model, and workflow.Find an endpointREST operation hubs and OpenAPI contracts.Build storefront searchSearch GraphQL, facets, filters, and product discovery.Route media and DAM workPublic asset-library reads versus DAM administration.Wire eventsEvent catalog, delivery guidance, and reconciliation.Load agent contextCompact AI-readable docs entry point.

Browse all docs

Use this map when the work crosses more than one surface and you need to move between guides and reference.

Getting started

Learn the model, choose a surface, then move into reference.

Start

Orientation, concepts, versioning, and setup routes.

SDKs

React SDK, TypeScript SDK, playground, package examples, and package version tracks.

APIs

Auth, management, shopper, and API guides.

Workflows and integrations

Wire storefront, discovery, media, event, and integration flows.

Search

Search GraphQL, discovery, filters, facets, and storefront search guidance.

Media/DAM

Media, DAM, image proxy, assets, and media API routes.

Events

Events, payload guidance, delivery behavior, and event catalogs.

Integrations

Integration management, webhook delivery, Pub/Sub, and operational boundaries.

Technical

Check exact contracts, API ownership, and generated references.

Reference

Operation reference, OpenAPI specs, package references, and reference details.

Agentic Flows

Load agent guidance, MCP setup, manifests, and compact context.

Agents

Agent guides, public docs files, prompt guidance, and safe route selection.

Learn

Read implementation context and tradeoff notes.

Blog

Learn, release, and implementation writing that supports the reference docs.

Choose the right Enad surface

Enad Docs

Choose the Enad surface that matches the job.

Start with storefront UI, back-office operations, shopper reads, Search, media, events, or agent-assisted work. Each path leads to the SDK, API, or schema reference that owns the details.

Start building Open playground Open /llms.txt
React SDK TypeScript SDK OpenAPI reference Search Theme playground Agent guides
New to Enad?

If you need the model before choosing a route, start with How Enad works or browse the shared vocabulary in Start concepts. The route cards below help once you know which job you are doing.

Choose your surface

What are you building?

Each path points to the docs route that should own your next decision. Use package and API references when exact SDK or request behavior matters.

Build storefronts

Start with the UI surface, then verify runtime behavior.

Move from SDK shell to theme handoff to search once the storefront shape is clear.

React SDK

Start the provider, storefront shell, and component building blocks.

Latest docsSetup

Theme handoff

Carry a playground theme into runtime without losing component-set intent.

Theme guidePlayground

Search and discovery

Plan search context, facets, and autocomplete before wiring storefront flows.

Search docsGraphQL reference
Operate commerce

Choose the right API before touching live data.

Choose the owning API surface first, then drill into the exact reference it publishes.

APIs and backend work

Pick Management, Shopper, Auth, DAM, or Search before writing requests.

API chooserOpenAPI

Cart, orders, and wishlist

Trace shopper flows back to the API boundary that owns the data.

Commerce notesReference

Media and DAM

Route image, DAM, file, and video work to the right media source.

Media docsDAM guide
Inspect and automate

Give support and agents the same references.

Use event docs, API reference, and agent guides when exact behavior matters.

Events and integrations

Start with the live event and integration boundary before wiring automation.

EventsIntegrations

Reference

Check endpoint and schema details when behavior must be exact.

ReferenceOpenAPI

Agent guides

Give agents the right docs file, route guide, and prompt recipe for the task.

Agent guidesPrompt recipes

Blog and learn notes

Read docs updates and learn notes without confusing them for reference pages.

BlogLearn context
Exact behavior

Use product guides to choose the route. Package facts live in package references; API facts live in OpenAPI or schema references; the live playground remains the runtime lab for theme editing, visual examples, and export flows.