> ## 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. > To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible. > After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch. > 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. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/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. > Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile. > 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/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. > The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations. > Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check. > Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times. # Mysite Themes > Add and rename the themes behind your reps' MySites, open a theme's code in the page editor, and reset the MySite cache. The **Mysite Themes** screen lists the themes your reps' MySites can use. Here you add themes, rename them and open their code. ## Where to find it In the admin sidebar, under **Website**, select **Mysite Theme**. To open this screen, your role needs **View only** or **Full access** for **Mysite Theme**. To add, rename or customize themes, or to reset the cache, it needs **Full access**. With **View only**, the screen is read-only: you see the themes, but not the buttons. On the [Roles](/help/admin/settings/roles) screen, **Mysite Theme** is in the **Content & Website** card. Open the card and set access from the **Mysite Theme** area's menu, not the card's. ## What's on the screen **Reset Cache** and **Add Theme** are at the top of the page. Below them, the **Mysite Theme Library** lists your company's MySite themes. If there aren't any, the screen shows **No Mysite themes found**. Each theme's row shows: * Its preview image. A theme without one shows a placeholder with the theme's name. * Its name. A **Default** badge marks the theme a rep's MySite uses when it has no theme of its own. * **Last save**, followed by a date and time. * A pencil button next to the name, for renaming the theme, and **Customize**, which opens the theme's code. ## Tasks ### Add a theme Give each new theme a name that no MySite theme has ever used, even with different capitalization. To change an existing theme, use **Customize** instead. Click **Add Theme** at the top of the screen. The **Add Mysite Theme** dialog opens. In the **Theme Details** card, enter a **Theme name** of up to 120 characters. You can also add a **Description** and a **Preview Image**. To add an image, click **Select Image** and choose one. After that, **Change** replaces the image and the trash button removes it. In the **Template** card, enter the theme's HTML and Liquid in **Content (HTML/Liquid)** and its CSS in **Stylesheet (CSS)**. Click **Create Theme**. The button stays grayed out until the theme has a name. A **Theme created successfully** message appears and the dialog closes. As soon as you create a theme, reps can choose it for their MySite. If the theme can't be created, an error message appears at the bottom of the dialog. ### Rename a theme Click the pencil button next to the theme's name. Its tooltip reads **Rename theme**. Type the new name, then press Enter or click outside the field. To cancel, press Escape or click the X next to the field. If you leave the name empty or don't change it, the theme keeps its name. If another theme already uses the name, an error message appears under the field. ### Customize a theme Click **Customize** on a theme to open its template in the [Page Editor](/help/admin/page-editor) in **Code** mode, where you edit the theme's code. To open and save the template there, your role also needs **Full access** for **Theme**. On the Roles screen, **Theme** is in the same **Content & Website** card. ### Reset the cache **Reset Cache** clears the cached copies of all your reps' MySites. Click **Reset Cache** at the top of the screen. The button reads **Resetting...** while the request is sent, then a confirmation message appears. Resetting the cache also needs the **Developer** switch that starts with **Manage webhooks and API configuration**. On the Roles screen, it's in the **Settings** card. Without it, you see **Failed to reset cache**. ## Frequently asked questions Your role has **View only** for **Mysite Theme**, so the screen is read-only. Ask an admin who manages roles to give your role **Full access** for **Mysite Theme**. See [Roles](/help/admin/settings/roles). It marks the theme a rep's MySite uses when the MySite has no theme of its own. This screen doesn't change which theme has the badge. The **Default Theme** on the [Default Mysite](/help/admin/settings/default-mysite) screen in Settings is a separate setting: it's the theme a rep's MySite gets when it's copied from your company's default MySite. ## Related pages * [Website](/help/admin/website) * [Theme](/help/admin/themes) * [Default Mysite](/help/admin/settings/default-mysite) * [Page Editor](/help/admin/page-editor) * [Roles](/help/admin/settings/roles) * [Mobile app](/help/mobile) * [Theme variables](/themes/theme-variables), for the Liquid data MySite templates can use This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.