Skip to main content
The storefront API serves the content a Fluid store shows its shoppers: products, the groupings that organize them, and the pages, posts, and media around them. You read it to render a storefront, and you write it to manage that content from your own tools.

​
Current version

The current storefront version is v2026-04. Its paths start with /api/v202604/. Every storefront resource is available on it, and there is no newer storefront version. Older Fluid APIs still serve some of the same resources — for example the unversioned company API’s product, page, and media endpoints. Those endpoints remain available, but they don’t receive new fields or behavior. Build new integrations on v2026-04.

​
Resources

The storefront API has eight resources. They share one design, so once you know one you know most of the others. See Storefront resources for what each one adds to the shared design.

​
Two kinds of endpoint

Every resource has two sets of endpoints:
  • Public endpoints — /api/v202604/<resource> and /api/v202604/<resource>/<slug>. No token. They serve what a shopper may see, and you call them on the store’s own host.
  • Company endpoints — /api/v202604/company/<resource> and /api/v202604/company/<resource>/<id>. A Bearer token is required. They serve and manage everything, including content that isn’t live yet, and you call them on https://api.fluid.app.
See Public and company endpoints for how they differ.

​
What every resource shares

  • The same response fields. Every resource returns id, slug, title, description, image_url, canonical_url, images, active, status, publish_at, seo, metafields, and languages, then adds its own.
  • The same visibility model. Lists show only live content. Looking up a slug directly can return content that isn’t live yet. See Visibility, drafts, and scheduling.
  • The same list controls. Search with q, filter with filter[...], sort with sort, and page with page[cursor] and page[limit].
  • The same translation model. See Translate storefront resources.
  • The same SEO model. See SEO for storefront resources.
Metafields are returned in full on the public endpoints. Never store private or internal data in a storefront resource’s metafields. See Metafields.

​
Guides

Public and company endpoints

Hosts, authentication, addressing, and what each side returns.

Storefront resources

The eight resources and what makes each one different.

Find and create resources

Browse, search, and filter, then create with the company API.

Visibility, drafts, and scheduling

What makes a resource live, and what drafts return.

Slugs and URLs

How slugs are set, pinned, and turned into URLs.

SEO

What search engines see, and how to control it.

Metafields

Attach your own typed data to any resource.

Country availability

Limit a resource to the countries it’s sold in.

Translations

Write and read a resource in more than one language.

Category hierarchy

Nest categories and walk the tree.

FairShare SDK and the storefront

Credit paths, attribution, add to cart, and media on a Fluid storefront.