> ## 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. > 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. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/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. # Floating Action Buttons > Show or hide your store's floating chat and cart buttons, and set their size, position, colors and the chat button's form text. Use the Floating Action Buttons screen to control the two buttons that float over your store: the chat button and the cart button. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Commerce**, select **Floating Action Buttons**. To open the screen, your role needs the **Company Settings** switch that starts with **View global company configuration**, in the **Settings** category. To save any change, even to only one button, your role also needs all of these switches (see [Roles](/help/admin/settings/roles)): * Under **Company Settings**, in the **Settings** category: the switch that starts with **Edit company-wide settings**. * Under **Popups**, in the **Content & Website** category: **View popup campaigns** and **Edit popup content and triggers**. * Under **Chat Widget**, in the **Settings** category: **View live chat widget configuration** and **Edit chat widget settings**. The **Popups** and **Chat Widget** switches don't mention this screen, but it uses them. ## What's on the screen On a wide screen, the **Preview** is on the left and the settings panel is on the right. The settings panel has two sections, **Chat Button** and **Cart Button**. Both start collapsed. Click a section's title to open it. Opening one section closes the other. **Save** is at the top of the screen and saves both buttons at once. ### Preview Click **Desktop** or **Mobile** to switch between a desktop view and a phone view. The preview updates as soon as you change a setting, before you save. In the preview, a button's primary color fills the button and its secondary color colors the icon. A button with **Hide Button** turned on doesn't appear in the preview. ### Chat Button * **Hide Button**: turn it on to hide the chat button on your store. * **Style** and **Content** tabs. **Style** is selected when the screen opens. On the **Style** tab: * A size selector with **Small**, **Medium** and **Large**. * **Position**: choose **Left** or **Right** to place the button in the bottom-left or bottom-right corner. * **Use brand settings**: a checkbox, checked by default. When it's checked, the button uses the primary and secondary colors from your [Brand Guidelines](/help/admin/settings/brand-guidelines) screen. * **Primary Color** and **Secondary Color**: color pickers that appear only when **Use brand settings** is cleared. Each has a swatch and a text field for a hex value. The **Content** tab has four fields for the text of the chat button's form: **Form Title**, **Form Description**, **Button Text** and **Success Text**. Each label shows a red asterisk while **Hide Button** is off. ### Cart Button * **Hide Button**: turn it on to hide the cart button on your store. * A size selector with **Small**, **Medium** and **Large**. * **Position**: choose **Left** or **Right** to place the button in the bottom-left or bottom-right corner. * **Use brand settings**, **Primary Color** and **Secondary Color**: these work the same way as on the chat button's **Style** tab. Saving this screen also sets the [Cart](/help/admin/settings/cart) screen's **Cart Drawer Position** to match the cart button's **Position**, and replaces the cart's colors and brand setting. Saving the Cart screen replaces the cart button's colors and brand setting here, but not its **Position**. ## Tasks ### Hide or show a button In the settings panel, click **Chat Button** or **Cart Button**. Turn on **Hide Button** to hide the button on your store. Turn it off to show the button. To show the chat button, first fill in its four **Content** fields. Click **Save** at the top of the screen. **Settings saved!** appears when the save succeeds. ### Style a button Each button has its own size, position and colors. To change both buttons, repeat these steps for the other one. Click **Chat Button** or **Cart Button**. For the chat button, make sure the **Style** tab is selected. Click **Small**, **Medium** or **Large**. Under **Position**, click **Left** or **Right**. To use your brand colors, check **Use brand settings**. To pick your own, clear **Use brand settings**, then set **Primary Color** and **Secondary Color**. For each color, click the swatch and choose a color, or type a hex value in the text field. Check the **Desktop** and **Mobile** previews, then click **Save**. ### Set the chat button's form text Click **Chat Button**, then click the **Content** tab. Enter the **Form Title**, **Form Description**, **Button Text** and **Success Text**. Click **Save**. ## FAQ If you see **Missing required fields**, the chat button is visible and one of its four **Content** fields is empty. The **Content** tab opens for you. If the **Chat Button** section is closed, click it, then fill in the empty fields. Or turn on the chat button's **Hide Button**. If **Save** isn't there, your role doesn't have the **Company Settings** switch that starts with **Edit company-wide settings**. You can still see the preview, but you can't open the **Chat Button** or **Cart Button** sections. If you see **Failed to save settings**, some of your changes may still have been saved, so reload the screen to check. Then ask an admin to check that your role has every switch listed under [Where to find it](#where-to-find-it), and try again. If saving keeps failing, contact support. Email Fluid support at [help@fluid.app](mailto:help@fluid.app). The [Getting help](/help/getting-help) page lists what to include in your request. The checkbox is unavailable until your brand colors load. While it's checked and unavailable, **Primary Color** and **Secondary Color** don't appear, so you can't pick your own colors. Reload the screen. If it stays unavailable, contact support. Saving [Brand Guidelines](/help/admin/settings/brand-guidelines) updates a button's colors only if the button was saved with **Use brand settings** checked. If a button with **Use brand settings** checked hasn't picked up your new colors, open this screen and click **Save**. A button with **Use brand settings** cleared keeps its own colors. ## Related pages * [Settings](/help/admin/settings) * [Brand Guidelines](/help/admin/settings/brand-guidelines) * [Cart](/help/admin/settings/cart): the cart drawer, whose position and colors change when you save this screen * [Roles](/help/admin/settings/roles)