> ## 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. # Navigation > Set up the bottom bar of your company's mobile app: its screens and their order, custom links, and which members see each navigation. Use the **Navigation** screen to set up your company's mobile app navigation: the screens on the app's bottom bar, their order, and any custom links. You can create more than one navigation and use access rules to choose which members see each one. Your website's menus are on a separate screen, under **Website** › **Navigation**. For how reps use the app, see [Mobile app](/help/mobile). ## Where to find it In the admin sidebar, under **Mobile App**, select **Navigation**. To open this screen and its editor, your role needs **View only** or **Full access** for **Mobile Pages**. With **View only**, navigations open read-only. To create, edit, publish or delete navigations, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Mobile Pages** is in the **Content & Website** card. Open the card and set access from the **Mobile Pages** area's menu, not the card's. ## What's on the screen The **New navigation** button is at the top of the page, above the list of your company's navigations. Your default navigation is always in the list, with a **Default** badge. It starts out named **Navigation**. Members who don't match any other navigation see it. ### Navigations list * The **All**, **Active** and **Inactive** tabs filter the list by status. * Use the search box to find a navigation by name. * The sort button sorts by **Name** or **Status**. Until you sort, the newest navigations come first. * The filter button opens **Filters**: **Status**, **Countries**, **Ranks** and **Languages**. The last three find navigations whose access rules include any value you pick. Click **Apply Filters**, or **Reset All** to clear the filters. The list has these columns: * **Name**: the navigation's name. * **Status**: **Active** or **Inactive**. Members only see active navigations. * **Audience**: a chip for each kind of access rule (**Member Type**, **Country**, **Language** or **Rank**), with its values. Countries show as flags. **All members** means the navigation has no access rules. * **Items**: how many items the navigation has, including hidden ones. Click a navigation to open it in the editor. Each row's actions menu has **Edit**, **Publish** or **Unpublish**, and **Delete**. The default navigation's menu has only **Edit**. ### Navigation editor The editor fills the screen. Its top bar has a close button (X), the navigation's name, a settings (gear) button and **Save**. Below are the item list, a phone preview and the **Settings** panel. To close **Settings**, click its X. The gear button opens it again. **Item list.** Items are the screens and links you can put on the app's bottom bar: * System screens: **Home**, **Share**, **Messaging**, **Contacts** and **Shop**. They're part of the app. You can hide and show them, but you can't rename them, change their icons or delete them. * Custom links: web pages you add, marked **Custom**. They open inside the app. The list has two sections: * **In navigation**: the items on the bottom bar. Top to bottom here is left to right on the bar. The bar shows up to six items. With more than six, the first five stay on the bar and the rest go to a **More** menu, which starts at the **More menu** divider. * **Hidden**: items that aren't on the bar. Hidden system screens stay here so you can show them again. **Phone preview.** The preview shows the bottom bar as icons, with the previewed screen's icon in your company's brand color. Click an icon, or an item in **In navigation**, to preview that screen. The three-dot icon opens the **More** menu. * **Home**, **Share** and **Shop** show a published page from your Home Tabs, Share Tabs or Shop Tabs, with its top tabs. * **Messaging** and **Contacts** show sample screens with a **Built into the app** notice. The content isn't your company's data, and you can't change it here. * A custom link shows its web page. Some sites can't be previewed here but still open normally in the app. **Settings panel.** With no item selected, **Settings** shows the navigation's settings: * **Name**: required. * **Active**: when it's on, members who match the access rules see this navigation. The default navigation always stays active. * **Access rules**: who sees the navigation. See [Choose who sees a navigation](#choose-who-sees-a-navigation). The default navigation applies to all members and can't have access rules. **Item settings.** Click an item in the list to see its settings, and **Done** to go back. For a system screen: * **Icon**: the icon when the screen isn't selected (**Inactive**) and when it is (**Active**). The app sets these icons. * **Content**: for Home, Share and Shop, a button such as **Edit home page content** opens [Home Tabs](/help/admin/mobile/home), [Share Tabs](/help/admin/mobile/share) or [Shop Tabs](/help/admin/mobile/shop). Build those screens' pages there, including the tabs across the top. For Messaging and Contacts, a link opens the [Messaging](/help/admin/messages) or [Contacts](/help/admin/contacts) screen. If you have unsaved changes, you're asked to save them first. For a custom link: * **Label**: the link's name in the app. Required. * **URL**: the page to open. Enter a full address that starts with `https://` or `http://`, such as `https://example.com/rewards`. * **Open in full screen**: off by default. When it's on, the link opens as a full-screen page instead of inside a tab. * **Icon**: to change the link icon, click **Change icon** and pick one. If someone else saved the navigation after you opened it, saving opens a **Someone saved newer changes** message. Click **Reload** to get their version, then make your changes again. ## Tasks ### Create a navigation Click **New navigation**. Fluid creates an inactive navigation named **New navigation**, with a copy of the default navigation's items, and opens it in the editor. In **Settings**, change the **Name**. Add at least one access rule. You can't save without one. See [Choose who sees a navigation](#choose-who-sees-a-navigation). Show, hide, order or add items. See [Change the items](#change-the-items). Turn on **Active** when you want members to see it. Leave it off to keep the navigation as a draft. Click **Save**. The confirmation message says your changes appear when members next open the app. The new navigation stays in the list even if you close the editor without saving. Delete it if you don't need it. ### Change the items In the list, click the navigation. Use the switch on an item's row, or drag the item between **In navigation** and **Hidden**. Items you show again go to the end of **In navigation**. Home can't be hidden: it's the app's landing screen. Drag items by the handle on the left of their rows to reorder them in **In navigation**. Click **Add custom link**. A link named **Custom link** appears at the end of **In navigation**, with its settings open. Enter its **Label** and **URL**, and set **Open in full screen** and **Icon** if you need them. Click **Save**. To remove a custom link, select it, click **Delete**, then click **Remove link**. It's removed when you save. System screens can only be hidden. ### Choose who sees a navigation Open the navigation. If an item's settings are showing, click **Done**. Under **Access rules**, click **Add rule** and choose **Rank**, **Country**, **Language** or **Member Type**. In the rule's card, select one or more values. Each rule gets its own card, joined by **And**. To remove a rule, click the X on its card. Click **Save**. How Fluid chooses each member's navigation: * A member can see an active navigation if they match every rule card. Within a card, any one selected value is enough. For example, a **Country** rule for Canada and a **Language** rule for French reach members in Canada whose language is French. * If a member matches more than one navigation, the most specific wins. A **Language** rule counts most, then **Country**, then **Rank**, then **Member Type**. Between equally specific navigations, the most recently updated one wins. * Members who match no other navigation see the default navigation. ### Publish or unpublish a navigation Set the navigation's access rules in the editor before you publish it. In the list, open the navigation's actions menu. Choose **Publish** to make the navigation active, or **Unpublish** to make it inactive. A confirmation message appears. You can also turn **Active** on or off in the editor's **Settings** and click **Save**. When you publish a navigation, or save one that's active, any other published navigation with exactly the same access rules is unpublished. You can't unpublish the default navigation. ### Delete a navigation In the list, choose **Delete** from the navigation's actions menu. In the **Delete Navigation?** dialog, click **Delete**. You can't undo this. Members who saw the navigation then get the next one that matches them, or the default navigation. You can't delete the default navigation. ## Frequently asked questions **Save** stays grayed out until you change something. It also stays off while the **Name** is empty, while a navigation other than the default has no access rules, or while a custom link has no **Label** or no valid **URL**. Click **Save** anyway to open the setting that needs fixing. If there's no **Save** button, your role doesn't have **Full access** for **Mobile Pages**. See [Roles](/help/admin/settings/roles). Check that: * The navigation is **Active**. Publishing or saving another active navigation with exactly the same access rules unpublishes it. * The members match every access rule card. * No more specific navigation matches them. See [Choose who sees a navigation](#choose-who-sees-a-navigation). Saved changes appear when members next open the app. ## Related pages * [Mobile App](/help/admin/mobile) * [Home Tabs](/help/admin/mobile/home) * [Share Tabs](/help/admin/mobile/share) * [Shop Tabs](/help/admin/mobile/shop) * [Mobile app](/help/mobile) * [Member Types](/help/admin/settings/member-types) * [Languages](/help/admin/settings/languages) * [Roles](/help/admin/settings/roles) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.