> ## 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. # Share Pages > Build the Share screen of your company's mobile app: share pages, their system tabs, share widgets and media creation, and who sees each page. Use the **Share Tabs** screen to build the Share screen of your company's mobile app. Share pages work like home pages: each has tabs across the top, widgets on each tab and access rules, and they open in the same editor. This page covers what's different. For the editor, see [Home Tabs](/help/admin/mobile/home). For how reps use the app, see [Mobile app](/help/mobile). ## Where to find it In the admin sidebar, under **Mobile App**, select **Share Tabs**. To open this screen and the page editor, your role needs **View only** or **Full access** for both **Share Pages** and **Mobile Pages**. With **View only**, pages open in the editor without a **Save** button, and the list has no actions menu. To create, edit, duplicate, set the default or delete share pages, it needs **Full access** for both. On the [Roles](/help/admin/settings/roles) screen, **Share Pages** is in the **People** card and **Mobile Pages** is in the **Content & Website** card. Open each card and set access from the area's menu, not the card's. ## What's on the screen **New Page** is above the list of your company's share pages. The list always includes your default share page, marked **Default**. Members who match no other active share page see it. The list works like the one on Home Tabs: the **All**, **Active** and **Inactive** tabs, search, sorting by **Name** or **Status**, the same columns and the same actions menu. See [Pages list](/help/admin/mobile/home#pages-list). **Not in navigation for:** in the **Member Type** column means a navigation hides the Share screen from the members it names. Access rules, publishing and the default page work as on Home Tabs, among share pages. See [Settings and access rules](/help/admin/mobile/home#settings-and-access-rules). ### System tabs Share pages have system tabs, one each for uploads, playlists, products, enrollments, media and pages. Each opens a screen built into the app, so it has no widgets. A grid icon marks them in the **Tabs** sidebar. * A new share page starts with all six under **Main Tabs**, named **Uploads**, **Playlists**, **Products**, **Enrollments**, **Media** and **Pages**. A page can have up to eight main tabs, so you can add two more, or move system tabs to **Not Linked** to make room. * You can rename system tabs and drag them between **Main Tabs** and **Not Linked**, but you can't delete them. * When you select a system tab, the preview shows a placeholder card instead of the screen, and **Settings** stays open. Widget tabs and embed tabs work as on home pages. See [Tabs](/help/admin/mobile/home#tabs). ### Media creation Share pages have one more setting. In **Settings**, under **Media creation**, the **Allow media creation** switch lets app users create uploads and playlists from this share page in the mobile app. It's on for a new share page. Click **Save** to apply a change. ### Widgets The widget drawer on a share page offers these widgets, and your company's own widgets for share pages, if it has any, under **My Widgets**: * **MySite**, **Unordered List**, **Ordered List**, **Video**, **Carousel**, **Spacer**, **Image**, **Text**, **Nested Unordered List**, **Quick Links** and **Subscriptions and Orders**. They work as on home pages. See [Widgets](/help/admin/mobile/home#widgets). * **Quick Share**: one item to share, with a QR code. Choose the item under **Share Content**, from your enrollments, products, media, pages or playlists. You can also set its **Title**, **Text Color**, **Background** and **Overlay intensity**. * **Quick Share Links**: links reps can share. Under **Links**, each link goes to a page of your website, such as a collection or post, to a web address, or to a shareable item. **Widget Title** sets the heading. ## Tasks ### Create a share page Click **New Page**. Fluid creates an inactive page named after you, such as **Alex's Page #43**, with the six system tabs, and opens it in the editor. In **Settings**, change the **Page Name**, add access rules, and set **Allow media creation**. Add tabs and widgets, and arrange the system tabs. Turn on **Publish** when the page is ready for members, then click **Save**. The new page stays in the list even if you close the editor without saving. ### Duplicate, set the default or delete a share page Use the page's actions menu in the list. These work as on Home Tabs; see [Duplicate, set the default or delete a page](/help/admin/mobile/home#duplicate-set-the-default-or-delete-a-page). A copy keeps the system tabs' names, order and sections. ## Related pages * [Mobile App](/help/admin/mobile) * [Home Tabs](/help/admin/mobile/home) * [Shop Tabs](/help/admin/mobile/shop) * [Navigation](/help/admin/mobile/navigation) * [Mobile app](/help/mobile) * [Media](/help/admin/media) * [Playlists](/help/admin/playlists) * [Roles](/help/admin/settings/roles) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.