> ## 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 > Share your MySite link, check its views and leads, change its theme, and choose the content and buttons your site shows. MySite is your personal website, where customers and prospects can see the products, media and links you pick. Use the **MySite** screen to share it, change how it looks, and choose what it shows. ## Where to find it In the app, tap your profile picture at the top of **Home**, then tap **MySite**. The **MySite** card shows only if you have a MySite. ## What's on the screen From top to bottom, the **MySite** screen shows: * The info button at the top right. It opens **Introducing MySite**, a short overview of what MySite is for. * **Visitor Details**: two counts for your site, **Views** and **Leads**. * **Your Share Link**: your MySite link. Tap it to open **Quick Share**. See [Share your MySite link](#share-your-mysite-link). * A preview of your site, with **Current Theme** and your theme's name. Tap the preview or **Preview** to open your site in a browser window. The edit button next to **Preview** opens **Theme**. * **MySite Content**: the products and media on your site. * **Buttons**: the links on your site. ## Tasks ### Share your MySite link On the **MySite** screen, tap your link under **Your Share Link**. Choose one: * Tap the link at the top of **Quick Share** to copy it. **Copied to clipboard** appears. * Tap **Share** to send it with your phone's share options. * Tap **Preview** to see your site first. * Under **Send To Your Contacts**, search by name or email to find a contact and send them the link. **Quick Share** also shows a QR code for your link. For more on the share options and sending to contacts, see [Sharing content](/help/mobile/sharing). ### Add products and media to your MySite Open the product, media or page you want on your site. Tap the three-dot button at the top of the screen. The **Add To** menu opens. Tap **MySite**. **This has been added to MySite** appears. Cards that have a plus button open the same **Add To** menu. If the item is already on your MySite, **You have already added this card to MySite** appears instead. ### Manage your MySite content On the **MySite** screen, tap **MySite Content**. It shows what you've added to your site as cards. If you haven't added anything yet, **MySite Favorites** appears with an example card. On each card: * Tap the card to open the item. * Tap the share button to open **Quick Share** for that item. * Tap the minus button to remove the item from your MySite. It's removed right away, and **This has been deleted from MySite** appears. Above the list, two buttons show the cards in a single column or in a grid. To change the order: When you have more than one item, **Drag to Re-arrange content** appears above the list. Let go to save the new order. ### Change your theme The **Theme** screen shows a preview of your site with **Current Theme** and a **Preview** button. Below it, **Explore Themes** lists the themes you can choose, by name. A check mark marks your current theme. On the **MySite** screen, tap the edit button next to **Preview**. Under **Explore Themes**, tap a theme. A **Preview** sheet opens and shows your site in that theme. Tap **Apply**. The sheet closes. To keep your current theme, tap **Cancel** instead. **Apply** doesn't appear when you preview the theme you already use. If the change fails, **There was an error updating your theme. Please try again.** appears. ### Add a button Buttons are named links on your MySite. On the **Buttons** screen, each button shows its name, its link and its number of **Clicks**. If you have no buttons yet, **No buttons** appears with a **New Button** button. On the **MySite** screen, tap **Buttons**. Tap the plus button at the top right. If you have no buttons yet, you can tap **New Button** instead. The **Button** form opens. Enter the **Button Name** and the **Link**. Both are required. Tap **Save**. You return to **Buttons**. ### Edit, reorder or delete a button On the **Buttons** screen, tap the button. Change the **Button Name** or the **Link**, then tap **Save**. To delete the button, tap **Delete Button**. It's deleted right away. To reorder your buttons, touch and hold one, drag it to its new place, and let go. ## Tips * Pull down on **MySite Content**, **Buttons** or **Theme** to refresh it. * Your **Home** tab may include a MySite widget. Tap it to open your MySite. ## Frequently asked questions Yes, if your company allows it. The last part of your MySite link is your username. To change it: 1. Tap your profile picture at the top of **Home**, then tap **Profile**. 2. Under **Username**, enter the new username. 3. Tap **Save**. Changing your username changes your MySite link, and links you shared with your old username stop working. A username needs at least 2 characters. It can use lowercase letters, numbers, hyphens and underscores. A hyphen can't come first or last, or next to another hyphen. Capital letters are saved as lowercase. If the field shows **Your admin manages the username on this account.**, you can't change it in the app. For the other profile fields, see [Settings and troubleshooting](/help/mobile/settings). Open the product or media, tap the three-dot button at the top, and tap **MySite** in the **Add To** menu. Cards that have a plus button open the same menu. See [Add products and media to your MySite](#add-products-and-media-to-your-mysite). You make every change from the **MySite** screen: * To change how your site looks, tap the edit button next to **Preview**. See [Change your theme](#change-your-theme). * To choose the products and media it shows, tap **MySite Content**. See [Manage your MySite content](#manage-your-mysite-content). * To add or change its links, tap **Buttons**. See [Add a button](#add-a-button). To change your MySite link, see [Can I change my MySite link?](#how-to-customize-my-mysite-url). On the **MySite** screen, tap **Preview** on the preview of your site. Your site opens in a browser window. **Quick Share** has a **Preview** button too. To see a theme before you apply it, tap the edit button next to **Preview**, then tap the theme. On the **MySite** screen, tap **Buttons**, then tap the plus button at the top right. Enter a **Button Name** and a **Link**, then tap **Save**. To edit or delete a button later, tap it. See [Add a button](#add-a-button). The **MySite** card shows only if you have a MySite. If you think you should have one, tap **Get Help** on the Dashboard to contact support. ## Related pages * [Mobile app](/help/mobile) * [Getting around the app](/help/mobile/getting-around) * [Sharing content](/help/mobile/sharing) * [Settings and troubleshooting](/help/mobile/settings) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.