> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluid.app/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract.
> Authenticate with the header Authorization: Bearer <token>; public storefront read endpoints require no auth.
> Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null.
> When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination.
> Navigation menu management is documented in themes/navigation-menus. These unversioned admin endpoints (/api/menus and nested menu_items) are verified against the implementation but are not yet in the synced OpenAPI specs. Use that reference for menu payloads and its flat page/per_page pagination; missing spec coverage does not make these endpoints unavailable.
> The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/auth-v0.yaml covers the unversioned auth surface (/api/... paths — authentication, MFA, social auth, and token exchange); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country).
> api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract).
> Successful responses wrap the resource payload alongside a top-level integer status and a meta object.
> Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other.
> For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces.
> Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings.
> Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties.
> Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables.
> A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation.

# Member storefront

> Serve one cached storefront page that adapts to the signed-in member in the browser.

The member storefront lets one cacheable storefront page work for both signed-in members and guests. Your Liquid template renders guest-safe content. A browser runtime then replaces the parts that depend on who is signed in.

Nothing member-specific is baked into the cached HTML. That keeps pages shareable on a CDN while members still see their own prices, name, and account menu.

It powers four things:

| Feature                                                     | What a member sees                            |
| ----------------------------------------------------------- | --------------------------------------------- |
| [Member prices](/member-storefront/member-prices)           | Their own price on ordinary price expressions |
| [Account navigation](/member-storefront/account-navigation) | An avatar menu instead of a sign-in link      |
| Member identity and audiences                               | Their name, and content aimed at members      |
| [Resource sharing](/member-storefront/resource-sharing)     | A Share button on shareable pages             |

## Install the runtime

The runtime ships as one script that Fluid installs for you as a global embed on the storefront, placed in the page head:

```html theme={null}
<script
  type="module"
  src="https://assets.fluid.app/member-storefront-sdk/member-storefront.js"
></script>
```

You do not add this tag by hand, and you do not need a theme change to get it. Fluid provisions the embed for the company and keeps it pointing at the current release. Review it alongside your other embeds in Fluid Admin — see [Manage global embeds](/api/guides/global-embeds).

Two things to know about the script:

* It is an ES module, so it must load with `type="module"`.
* The URL carries no version. Fluid publishes each release under an immutable versioned path and repoints this stable URL once the release is verified, so storefronts pick up fixes without a theme edit.

Ask Fluid to enable the member storefront for your company. Until it is enabled, the Liquid tags below render nothing and the runtime stays idle.

## How hydration works

The runtime never reads a token from the URL or from browser storage. Instead it checks for a non-sensitive marker cookie that Fluid sets next to the real signed-in session cookie.

1. Your template renders guest-safe fallbacks and empty shells.
2. On load, the runtime looks for member shells on the page.
3. If it finds one **and** the marker cookie is present, it confirms the session with Fluid.
4. It fills the shells and reveals member-only branches.

If the marker is missing, the runtime makes no network requests at all. A forged or stale marker grants nothing, because Fluid still authenticates the real session cookie on every request.

Members who were already signed in before your company was enabled need to sign in once more.

### Guest-safe by default

Every shell keeps its original content until real data replaces it. Expired sessions, failed requests, and timeouts leave the guest content in place rather than blanking the page.

The runtime revalidates when the page regains focus or is restored from history, and it discards responses that arrive after a sign-out.

## Show member identity

Use the `{% member %}` block to branch on audience. The `{% else %}` branch is what guests and crawlers see:

```liquid theme={null}
{% member %}
  <a href="/collections/member-pricing">Your member pricing</a>
{% else %}
  <a href="/pages/join">Become a member</a>
{% endmember %}
```

Both branches ship in the cached HTML. The member branch starts hidden and is revealed in the browser, so never put anything private in it.

<Warning>
  Treat the member branch as public. It is present in the page source for every visitor, including guests and crawlers. Put only content you are willing to publish there.
</Warning>

Use `{% member_name %}` where the member's display name should appear. The tag renders an empty shell that the runtime fills in for members, so a guest sees nothing in its place.

Pair it with copy that still reads correctly when the name is absent, or place it inside a member branch:

```liquid theme={null}
{% member %}
  <p>Welcome back, {% member_name %}</p>
{% else %}
  <p>Welcome back</p>
{% endmember %}
```

## Scope

Member name shells and audience branches must sit inside a section marked with `data-fluid-member-storefront`. Price shells hydrate anywhere on the page.