> ## 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. > 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. > 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. # Mist Apps > List your company's Mist apps with their status, hosted resource and public URL, and create a new Mist from Settings. Use the Mist Apps screen to see the hosted apps your company has deployed with Mist and to create new ones. Apps you build and ship with the Fluid CLI or Mist Desktop appear here too. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **System**, select **Mist Apps**. To open the screen, your role needs at least **View only** for **Mist**, in the **Other** card on the role's **Permissions** tab. To see the **Create Mist** button, your role also needs the **Mist** permission that starts with **Create new Mist hostings**. ## What's on the screen The **Create Mist** button is in the page header. Below the header, a banner describes Mist and has a **View Mist Documentation** link, which opens the Fluid docs in a new tab. Above the table is a search box. Search matches any part of an app's name, slug, vendor or URL, or the droplet name shown under **Hosts**. The table lists one row per Mist app: * **App**: the app's name, with its slug below it. If the app has no name, the slug shows in its place. * **Status**: one of **Live**, **Provisioning**, **Pending**, **Failed**, **Pending Destroy** or **Archived**. * **Hosts**: what the app wraps. A droplet app shows the droplet's name with **Droplet App** below it. Other hosted resources show their type, such as **Mobile Widget** or **Drop Zone**, and, when there is one, the resource's ID, such as `#123`. An app that hosts nothing shows **Standalone**. * **URL**: the app's public address. Click it to open the app in a new tab. A dash (—) means the app has no public URL. * **Vendor**: the app's vendor, or a dash (—) if it has none. * **Created**: the date the app was created, such as Oct 1, 2026. If you have no Mist apps, the table shows **No Mist apps yet**, with a reminder of the ways to deploy one. You see the same message when no app matches your search. Clear the search to see your apps again. ### Create Mist panel fields **Create Mist** opens a side panel with the same title. In order, it has: * **Name** (required): the app's name. * **Host a resource**: leave this set to **None — standalone mist**. The panel ends with **Cancel** and **Create**. ## Create a Mist app Click **Create Mist**. Enter a **Name**, and leave **Host a resource** set to **None — standalone mist**. Click **Create**. You see **Mist created successfully**, the panel closes and the app appears in the table. If you leave **Name** empty, you see **Give your mist a name.** You can also deploy apps with the Fluid CLI (`fluid mist create`) or Mist Desktop. Developers can list and create Mist apps through the API too. See the [API overview](/api/overview). ## Frequently asked questions You see **Failed to create mist**, with the reason when one is available, or **Something went wrong. Please try again.** The panel stays open with your entries, so you can fix them and click **Create** again. The **Mist Apps** item appears only if your role can view Mist hostings. Ask an admin who manages roles to edit your role's permissions: open the **Other** card, then set **Mist** to **View only** or **Full access**. See [Roles](/help/admin/settings/roles). The same permission also shows **AI Spend** under **Payments**. See [AI Spend](/help/admin/settings/ai-spend). **Create Mist** appears only if your role can create Mist hostings. Ask an admin who manages roles to open the **Other** card on your role's **Permissions** tab, click **Mist**, and turn on the permission that starts with **Create new Mist hostings**. Setting **Mist** to **Full access** also works, but it turns on every Mist permission, including reading and changing environment variables. ## Related pages * [Settings](/help/admin/settings) * [Roles](/help/admin/settings/roles) * [AI Spend](/help/admin/settings/ai-spend) * [API overview](/api/overview) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.