> ## 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. # Messaging > Message your reps and customers, create public, team and broadcast channels, schedule messages, and manage channel members from the admin. Use the **Messaging** screen to read and answer your conversations, set up channels, and plan messages to send later. ## Where to find it In the admin sidebar, select **Messaging**. To open this screen, your role needs **View only** or **Full access** for **Messaging**. To start conversations, send, schedule or pin messages, add reactions, and create or manage channels, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Messaging** is in the **Tools & Messaging** card. Open the card and set access from the **Messaging** area's menu, not the card's. ## What's on the screen The screen opens your most recent conversation. Your conversations are listed on the left, grouped in sections. Sections with no conversations are hidden once your conversations have loaded: * **SMS** and **Emails**: SMS and email conversations sent and received through Fluid. * **Public Channels**: channels whose members come from filters, which can include anyone in your organization. * **Private Channels**: channels that only their members can view and post in. The team channels you create are listed here. * **Broadcast Channels**: channels where only certain members can post. Your company's announcements channel is listed first. * **Downline**: messages to an entire downline. If you have a downline of your own, your downline conversation is listed first. It's a Pro feature: without Pro, clicking it opens **Unlock Downline Messaging** instead. * **Bots**: conversations with automated bots. * **Direct Messages**: messages sent to you, or to a group you're in. Each section shows up to 10 conversations, then **Show All**. Click a section's name to collapse it. Conversations with unread messages stay visible. A pencil icon marks a conversation with an unsent draft. At the bottom of the list are a menu button, with **Contacts** and **Scheduled Messages**, and **New**, which starts a message or a channel. Above an open conversation are **Back** and **Forward**, the conversation's name, and the **More options** menu. The menu has **Pinned Messages** and, in a channel, **Channel Members** and, with **Full access**, **Channel Settings**. ## Send a new message Click **New**, then **Message**. The **New Message** screen opens. In **To:**, start typing a name. Type `@` first to search only people, or `#` to search only channels. You can pick several people or one channel, but not both. Type your message and press Enter, or click the send button. If you already have a conversation with the people you picked, the message is added to it. The conversation opens. To reply, open the conversation and type in the message box at the bottom. ### Write messages * Click into the message box to show the formatting toolbar: **Bold**, **Italic**, **Strikethrough**, **Add Link**, **Bullet List** and **Numbered List**. SMS and email conversations don't have the toolbar. * **Add Link** opens the **Add link** dialog. Enter the **Text** to show and the full web address in **Link**, including `https://`, then click **Save**. Web addresses you type or paste also become links. * Click **Attach file**, or drag files onto the message box. A file larger than 1 GB shows **File is too large** and isn't attached. You can send attachments without text. * Click **Add emoji** to insert an emoji, or type `@` to mention a member of the conversation. * By default, Enter sends and Shift+Enter starts a new line. Once you've typed something, click **Enter to Send** next to the send button to swap them. ## Schedule a message In the conversation, type the message and add any attachments. Click the arrow next to the send button. The **Schedule send** menu lists the next four weekday times at 9:00 AM or 1:00 PM, such as **Tomorrow at 9:00 AM**. Choose a suggested time. Or choose **Custom date & time…**, pick a date and a time at least a minute from now, and click **Schedule message**. Times are in your computer's time zone. A banner above the message box shows when the conversation's next scheduled message goes out. Click the banner to open **Scheduled Messages**. ## Manage scheduled messages To see the messages you've scheduled, click the menu button at the bottom of the conversation list and choose **Scheduled Messages**. Each row shows the conversation, the start of the message and its send time. **Overdue** means the send time passed more than 10 minutes ago, and **Failed** means more than 2 hours ago. A **Failed** message won't be sent. Use **Send now**, or delete it. Each row's **More options** menu has **Go to conversation**. With **Full access**, it also has: * **Edit message**: opens the conversation with the message in the message box. Make your changes and click the check button (**Save scheduled message**). The send time stays the same, and you return to **Scheduled Messages**. * **Send now**: in **Send Message Now?**, click **Send Now**. The message is sent and the conversation opens. * **Delete message**: see [Delete a scheduled message](#delete-a-scheduled-message). ## Create a channel Click **New**, then **Channel**. The **New Channel** panel opens. Enter a **Channel Name** and, if you like, a **Channel Description** of up to 120 characters. To change the channel's icon, click it and pick an emoji. Under **Visibility**, choose **Public**, **Team** or **Broadcast**. You can't change the type after you create the channel. See [Which channel type should I use?](#choose-channel-type) Then click **Add Users**. For a public or broadcast channel, use **Filter Users** to add people by **Country**, **Language**, **Rank** or **Member Type**, or **Add All Users** to add everyone in your organization. Each has a switch to add future members automatically. For a team channel, use **Search Users** to add people by name. Click **Create Channel**. The new channel opens. **Create Channel** stays unavailable until you've added at least one person, chosen a filter, or chosen **Add All Users**. A filter appears only if your company has options for it. Channel names show in lowercase, with hyphens in place of spaces. If you pick exactly the same people as an existing team channel or group message, Fluid doesn't create a new one, and the panel shows **This conversation already exists**. Click **Open Conversation** to go to it. ## Manage a channel Open the channel and choose **Channel Members** from **More options**, or **Channel Settings** if your role has **Full access**. With **Full access**, a **Channel Settings** button also appears at the start of the channel's history. The channel panel has two tabs. **Members** lists the channel's members, with a count on the tab. Use **Search members** to find someone. With **Full access**: * To remove someone, hover over their row, open the **Member options** menu, choose **Remove From Channel**, then click **Remove**. You can't remove yourself. On a public or broadcast channel, you can't add a removed member back from this screen. * On a team channel, click **Add Members**, search for people, and click **Add**. Public and broadcast channels don't have **Add Members**. **Settings** shows the **Channel Icon**, **Channel Name**, **Channel Description**, and a **Channel Type** card with the type and who created the channel. With **Full access**, change the icon, name or description and click **Save Changes**. The name must not already be taken. Without **Full access**, the tab is read-only. ## Pin messages Hover over a message and open its menu to choose **Pin message**, **Unpin message** or **Copy link to message**. Pinned messages are marked **Pinned**. Next to the menu, you can add an emoji reaction, except in SMS and email conversations. To see a conversation's pinned messages, choose **Pinned Messages** from **More options**. The menu shows how many there are. Click a pinned message to jump to it in the conversation. ## Delete channels and scheduled messages You can delete a whole channel, or a scheduled message before it's sent. This screen has no archive option, and you can't delete a message once it's sent. ### Delete a channel In the channel, choose **Channel Settings** from **More options**. In the **Delete Channel** card, click **Delete Channel**, then click **Delete**. You return to the **Messaging** screen. Deleting a channel removes it and all of its messages for every member. Delete a channel only when nobody needs its history, such as a test channel or a duplicate. Deleting a channel needs **Full access**. Your company's announcements channel can't be deleted, renamed or given a new icon. You can change its description. ### Delete a scheduled message Open **Scheduled Messages** and find the message. From the row's **More options** menu, choose **Delete message**, then click **Delete**. A deleted scheduled message is gone for good. You can't undo it. ## Frequently asked questions * **Public**: members come from the filters you set, or from everyone in your organization, and every member can post. Listed under **Public Channels**. * **Team**: only the people you add can view the channel. Listed under **Private Channels**. * **Broadcast**: admins post, and everyone else can only read, as in your company's announcements channel. Listed under **Broadcast Channels**. Click **New** at the bottom of the conversation list, then **Message**. In **To:**, type `@` and a name to find people, or `#` and a name to find a channel. See [Send a new message](#send-a-new-message). **Add Members** is only on team channels, and only for roles with **Full access** for **Messaging**. A public or broadcast channel gets its members from the filters or the **Add All Users** choice made when it was created. If there's no message box, your role doesn't have **Full access** for **Messaging**. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). If the conversation shows **You don't have permission to send messages to this conversation.**, sending is turned off for you in that conversation. ## Related pages * [Roles](/help/admin/settings/roles) * [Contacts](/help/admin/contacts) * [Mobile app](/help/mobile) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.