> ## 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. > 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/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. # Default MySite > Set the content, buttons and theme new members' MySites can start with, and the content and buttons shown on MySites with none of their own. Use this screen to build your company's Default MySite. While **Auto Populate Status** is **Active**, each new member's MySite starts with a copy of it. Any member's MySite that has no content items of its own shows your Default MySite content, and one with no buttons of its own shows your buttons. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Company**, select **Default Mysite**. To see **Default Mysite** in the sidebar and change anything on it, your role needs **Full access** for **Default Mysite**, in the **Content & Website** card on the role's **Permissions** tab. See [Roles](/help/admin/settings/roles). ## What's on the screen The screen has a content panel and four cards: **Instant Redirect**, **Default Theme**, **Auto Populate Status** and **Buttons**. Both **Save** buttons, at the top of the screen and in the **Buttons** card, save everything on the screen. ### Content The content panel lists the items on your Default MySite, in order. * The type menu sets what kind of item you search for. It starts on **Products**. The other types are **Pages**, **Media**, **Promotions** and **Enrollments**. **Enrollments** lists active enrollments only. * The **Search content...** field finds items of the selected type. Items you've already added don't appear in the results. * **Add** puts the item you selected in the results at the bottom of the content list. It stays unavailable until you select an item. * The content list shows each item's title and type, with a drag handle and a trash icon. ### Instant Redirect When **Enable instant redirect** is checked, a **Forwarding URL** field appears. ### Default Theme Select the theme new members' MySites get when they're copied from your Default MySite. That copy happens only while **Auto Populate Status** is **Active**. The menu lists **Default** and your company's MySite themes. To manage those themes, in the admin sidebar, under **Platforms**, click **Website** > **Mysite Theme**. ### Auto Populate Status This card has two options: * **Active**: when a new member is added, their MySite gets a copy of your Default MySite content, buttons and theme. Nothing is copied if the member has no country, or if none of your content is available in the member's country. * **Inactive**: new members' MySites get no copy. A Default MySite that has never been saved starts as **Inactive**. Either way, a MySite with no content or buttons of its own shows your current Default MySite content and buttons. ### Buttons The **Custom Buttons** list holds the buttons on your Default MySite. * **Add** creates a new button at the top of the list and opens it for editing. * Each button has a row that opens and closes when you click it, and a trash icon. A button with no text shows as **Untitled button**. * Every button needs both **Button Text** and **Button Link**. ## Set up your Default MySite Choose a type from the type menu, click **Search content...**, and select an item. Click **Add**. Repeat for each item you want. Drag items by their handle into the order you want. To remove an item, click its trash icon. In the **Buttons** card, click **Add**, then enter the **Button Text** and **Button Link**. To change a button later, click its row and edit the fields. To remove one, click its trash icon. In the **Default Theme** card, select a theme. New members get it only while **Auto Populate Status** is **Active**. In the **Auto Populate Status** card, select **Active** if new members' MySites should start with a copy of this setup. Select **Inactive** if they shouldn't. If **Enable instant redirect** is checked and **Forwarding URL** is empty, uncheck **Enable instant redirect**. The save stops while the box is checked and the field is empty. Click **Save**. When the save succeeds, a confirmation message appears. ## FAQ Only MySites that have none of their own. A MySite with no content items of its own shows your current content, and one with no buttons of its own shows your current buttons. Content and buttons copied to a member's MySite when they joined count as their own, as do items the member added, so your later changes don't reach them. A member's MySite page can keep showing the earlier version until you clear the MySite cache. To clear it, in the admin sidebar, under **Platforms**, click **Website** > **Mysite Theme**, then click **Reset Cache**. * **Save** stays unavailable until you change something on the screen. * There's no **Save** button at the top and you can't change anything: your role doesn't have **Full access** for **Default Mysite**. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). * A button is missing its **Button Text** or **Button Link**. The save stops with a message asking you to fill in all button fields. Open the button and fill in the empty field, or remove the button with its trash icon. * **Enable instant redirect** is checked and **Forwarding URL** is empty. Uncheck **Enable instant redirect**, then save again. ## Related pages * [Settings](/help/admin/settings) * [Roles](/help/admin/settings/roles) * [Admin portal](/help/admin)