> ## 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. # Settings and troubleshooting > Manage your profile, language, notifications and orders from the Dashboard, and fix problems with app updates, the cache and signing in. The **Dashboard** holds your own settings: your profile, language, notifications, orders and subscriptions, and account details. This page also covers updating the app, clearing its cache and signing in. ## Where to find it In the app, tap your profile picture at the top of **Home**. ## What's on the screen From top to bottom, the **Dashboard** shows: * **Notifications**: the bell icon at the top. It opens your notification preferences. See [Choose your notifications](#choose-your-notifications). * **Organization**: the company you're using. It appears only if you belong to more than one company. See [Switch organizations](#switch-organizations). * Your business card, with your profile photo, name and email. If you have a MySite, the card also has a QR code that opens it. * Shortcut cards for **MySite** (if you have one), **My Uploads** and **My Playlists**. See [MySite](/help/mobile/my-site) and [Playlists and content](/help/mobile/playlists). * **Profile**: your photo, name, contact details, username, bio and social media accounts. * **Recent Activity**: see [Track engagement in Recent Activity](/help/mobile/sharing#track-engagement-in-recent-activity). * **Orders** and **Subscriptions**, if your company shows them: the orders and subscriptions you placed yourself. * **Language**: the app's language. The row shows the language you're using. * **Get Help**: contact support. * **Account**: your shipping addresses and payment methods. * **General Information**: the privacy policy, terms of use, app details and **Clear Cache**. * **Log Out**: signs you out of the app. ## Edit your profile Your profile has these sections: * **Profile Photo**: add or change your photo. It uploads when you save. * **Profile Information**: **First Name**, **Last Name**, **Primary Email Address** and **Mobile Number**. You can't change your email address here. * **Username**: the last part of your MySite link, so changing it changes the link. Links you shared with your old username stop working. See [Can I change my MySite link?](/help/mobile/my-site#how-to-customize-my-mysite-url). * **About You**: your **Bio**. * **Social Media**: your LinkedIn, Facebook, X, Instagram, YouTube, Pinterest, TikTok, WhatsApp and WeChat accounts. If your company manages your name or username, you can't edit that field, and a note such as **Your admin manages the name on this account.** appears. On the Dashboard, tap **Profile**. Change the fields you need. **First Name** and **Last Name** can't be empty, unless your company manages them. Tap **Save**. An **Updated successfully** message appears and you return to the Dashboard. A new username needs at least 2 characters, using only 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. **Delete Account** is at the bottom of your profile. Tap it, then tap **Delete** to confirm, and the app signs you out. To leave the app without deleting your account, tap **Log Out** on the Dashboard instead. ## Orders and subscriptions **Orders** and **Subscriptions** list the orders and subscriptions you placed yourself. ### Orders Each order shows its number, date and **Total**. It also shows **Total CV/QV**, unless your company hides volume. If you don't have any orders, the list says **No Orders**. Tap an order to open its **Order Detail** page: * The order number, date, number of items, and the items. * **Payment**: **Subtotal**, any points you used, **Discount**, **Tax**, **Shipping** and **Total**. Unless your company hides volume, the order's CV and QV appear below. * **Payment & Shipping**: **Shipping Address**, **Shipping Method**, **Tracking Information** and **Payment Method**. Each shipment shows its tracking number, with a **Track package** link to the carrier's tracking page when one is available. Digital orders show **No shipping required**, and free orders show **No payment required**. Tap **Manage Order** at the bottom to open the order's management page inside the app. ### Subscriptions Each subscription shows its status, ID, next billing date, how often it's delivered, and its price. A cancelled subscription shows the date it was cancelled instead. A past-due subscription shows **Next Retry At**, and a trial shows **Trial Ends**. Tap a subscription to open its **Subscription Detail** page: * **Your Upcoming Order**: **Next Order Date** and **Next Bill Amount**. * **Subscription Details**: **Order Frequency** and **Next Payment**. * **Subscription ID**, the product, and the **Payment** totals. * **Payment & Shipping**: **Shipping Address** and **Payment Method**. To change a subscription: On the Dashboard, tap **Subscriptions**, then tap the subscription. The subscription's management page opens inside the app. Make your changes there. For example, you can pause, cancel or reactivate the subscription. Tap **Back**. The subscription's page and your subscriptions list refresh to show your changes. ## Change the language The **Language** list shows the languages your company offers that the app supports. On the Dashboard, tap **Language**. Tap a language. The list closes and the app switches to that language. ## Get help Tap **Get Help** to contact support. If your company has a support email address, a new email to that address opens in your mail app. For other ways to get help, see [Getting help](/help/getting-help). ## Manage addresses and payment methods Tap **Account** to manage your shipping addresses and payment methods. The page opens inside the app. Tap **Back** when you're done. ## General Information Tap **General Information** to see: * **Privacy Policy** and **Terms of Use**: these open in your web browser. * **Clear Cache**: see [Clear the cache](#clear-the-cache). * **App Info**: your device, app version and update details. Tap **Copy** to copy them. Opening **App Info** also checks for an app update. ## Switch organizations If you belong to more than one company, **Organization** near the top of the Dashboard shows the company you're using. On the Dashboard, tap **Organization**. A list of your companies opens. Tap the company you want. The app switches to it. ## Choose your notifications Tap the bell at the top of the Dashboard to open **Notifications**. Your changes save as soon as you make them. * **Do Not Disturb** silences notifications until tomorrow morning. Turn on **All** to silence push and email notifications, or turn on only **Push** or **Email**. * Under **Presets**, tap **Default**, **Essential**, **Balanced** or **Engaged** to update all your preferences at once. * Below the presets, your notifications are grouped by category. A category's switch turns all of its notifications on or off. Each notification has two switches: the first is for push notifications, the second for email. ## Troubleshooting ### Update the app When a new version of the app is ready, an **Update Available** banner appears at the top of **Home**. Tap the banner to update. Depending on the update, the app restarts with the new version, or your app store opens so you can install it. If an update is required, the banner covers the **Home** screen. Tap it to update. To check for an update yourself, tap **General Information** on the Dashboard, then tap **App Info**. If an update is ready, the **Update Available** banner appears on that screen. ### Clear the cache Clearing the cache makes the app load your data again, which can help when a screen shows out-of-date information. You stay signed in. On the Dashboard, tap **General Information**. A **Cache cleared** message appears with your app details, such as its version. Tap **Ok**, or tap **Copy** to copy the details for support. ### Trouble signing in The sign-in screen shows your company's logo, or the app's name, and a **Sign in with email** button. Tapping it opens the sign-in page inside the app. * The sign-in screens follow your phone's language when the app supports it, not the language you chose on the Dashboard. * If the sign-in page doesn't load, tap **Back** at the top and try again. * If a message such as **There was an error signing in** appears, the app takes you back to the first screen. Tap **Sign in with email** to try again. * If you still can't sign in, see [Getting help](/help/getting-help). ## Tips * If support asks for your app details, open **General Information**, tap **App Info**, then tap **Copy** and paste the details into your message. * Pull down on **Notifications**, your orders or subscriptions, or an order's or subscription's page to refresh it. ## Frequently asked questions Tap the bell at the top of the Dashboard. On **Notifications**, you can silence notifications with **Do Not Disturb**, apply a preset, or turn each notification's push and email switches on or off. See [Choose your notifications](#choose-your-notifications). On the Dashboard, tap **Language**, then tap a language. The list shows the languages your company offers that the app supports. If you need a language that isn't listed, ask your company whether it can be added. On the Dashboard, tap **Account**. Your account page opens inside the app, where you can manage your shipping addresses and payment methods. ## Related pages * [Getting around the app](/help/mobile/getting-around) * [MySite](/help/mobile/my-site) * [Sharing content](/help/mobile/sharing) * [Getting help](/help/getting-help) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.