> ## 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 ; 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. > 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 overview > Greet signed-in members and show their prices on cached storefront pages, and give them their own pages inside the active theme. Coming soon: member storefront is in a limited pilot and is not yet generally available. This page describes the pilot release for companies that have it enabled, and details can change before general availability. Contact [Fluid support](mailto:support@fluid.app) to ask about enabling it for your company. Member storefront brings signed-in members into the theme you already have. A member sees their own price and their own name in the same sections every visitor sees, and opens member-only pages that render inside the same theme. There is no second site to design and no separate portal to assign. It has two surfaces, and they work differently on purpose: | Surface | Where it renders | How it knows the member | | ---------------------- | ------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- | | Member-aware sections | Your storefront pages, cached once per path, country, and language | Liquid emits placeholder shells with the guest value. The member storefront SDK fills them in the browser | | Member sites and pages | Your company's account subdomain, rendered on every request | The page is rendered for the signed-in member, so templates read a `member` value directly | Member storefront features require enablement for your company. Until then the member helpers render their guest values, and the account subdomain keeps its current behavior. Use `member_price`, `member_name`, and the `member` block to add member values to cached sections. Group member pages into sites, decide who sees each site, and give each its own layout and navigation. Build the dashboard, sign-in, custom page, and layout templates that frame a member's pages. ## Why the two surfaces differ Storefront pages are cached and served to everyone. If the server rendered one member's price into a product grid, the cache would hand that price to the next visitor. Member-aware sections keep the server render identical for every viewer and move the personal part to the browser. See [Member-aware sections](/themes/member-storefront/member-aware-sections). Member pages are private. They render on every request for the signed-in member, are never cached, and are never indexed. A guest who opens one is redirected to sign in. Because the render knows the member, member page templates read `member` directly and need no shells. See [Member page templates](/themes/member-storefront/member-page-templates). ## What a member site is A member site is an access rule and the set of pages it governs. A theme holds an ordered list of sites. Each site names the countries and member types it serves, the layout that frames its pages, and the menu that navigates them. A member resolves to exactly one site, is served that site's pages, and receives a not-found response for every other site's pages. See [Member sites](/themes/member-storefront/member-sites). ## What ships with the theme The root themes ship the product card with `member_price` and nothing else. Member page templates, the member layout, and member sites are yours to author. A company whose theme has no dashboard template receives a not-found response at the account subdomain root until one exists. Member sites travel with the theme. Duplicating a theme copies its sites and pages, and exporting a theme writes them to `members_sites.json` at the theme root so an import into another company can recreate them. ## What member storefront is not * It does not replace or change the portal. Portal Definitions and Widget Packages are a separate product with separate contracts. * It adds no pricing rules. Every member price the SDK shows is a value the platform already resolves for that member. * It never puts member data into a cached page. The storefront render stays viewer-independent. ## Next steps 1. Add `member_price` to your product card and test the guest render. Start with [Member-aware sections](/themes/member-storefront/member-aware-sections). 2. Create a member layout and a dashboard template. Follow [Member page templates](/themes/member-storefront/member-page-templates). 3. Add a member site in the theme editor, choose its rule and layout, and arrange its menu. Follow [Member sites](/themes/member-storefront/member-sites).