> ## 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, run `fluid signup` from the Fluid CLI, or 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. Before authenticated calls are possible, the merchant must sign the agent in to the Fluid CLI with the emailed code and --shop set to the company's fluid_shop (which also confirms the signup), or open the emailed confirmation link and give the agent an API token. > 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 on an operation whose spec documents those params — mostly the unversioned company-v0 admin surface, plus some lists on other surfaces, versioned ones included; page every other list with cursors. > 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 except two operations that take no credential, POST /api/company (create a company) and GET /api/agreements/{id} — 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. # Connect monday > Connect your monday account to Cowork, watch a board, then send any item to Cowork by setting its status to Cowork. Sending monday items to Cowork takes two one-time steps: connect your monday account, then watch each board you want to send from. After that, setting an item's status to **Cowork** sends it to Cowork as a ticket. Read [Connectors](https://docs.fluid.app/help/admin/cowork/connectors.md) first for how connectors behave. ## Why you watch boards monday only reports changes board by board, so Fluid has to listen to each board you send from. A board can also have several status columns, such as Status and Priority. When you watch a board, you choose which one is its **send column**: the column whose **Cowork** label sends an item. ## Prepare a board in monday On each board you want to send from: 1. Pick a **status** column to be the send column, or add a new one, for example **Send to Fluid**. 2. Add a label named **Cowork** to that column. 3. Optionally, add a **long text** column for the request. Its text becomes the ticket's description. ## Connect your monday account **1. Open Connectors** In the Fluid admin, open **Cowork** and click **Connectors** in the board's toolbar. **2. Click Connect** In the **monday** section, click **Connect**. monday opens and asks you to approve Fluid's access. **3. Approve in monday** Approve the request. You return to Connectors, and the **monday** section shows your account and name with a **Connected** badge. > [!NOTE] > > The first time anyone in a monday account connects, monday may ask for the > Fluid Cowork app to be installed on that account. Installing apps needs a > monday admin. ## Watch a board **1. Open the board list** In the **monday** section, click **Watch a board**. Your boards are listed, with boards that already have a **Cowork** label first, marked **Ready**. Use **Search boards** to find a board by name, and **Load more boards** to see more. **2. Choose the send column** Next to the board, choose its send column. On a **Ready** board, the column with the **Cowork** label is already chosen. **3. Click Watch** Click **Watch**. The board moves to **Watched boards**. If its send column has no **Cowork** label yet, a message tells you to add one in monday. ![The monday board list with a search box and a watched board](https://mintcdn.com/fluid-090e382c/7EN3agD0eenortiK/images/help/cowork/monday-board-picker.png?fit=max\&auto=format\&n=7EN3agD0eenortiK\&q=85\&s=0f8955f1cdec72bd8cd5e00f70adbae9) Search your boards. A board you already watch is marked Watched. ![The monday section listing a watched board with Stop watching](https://mintcdn.com/fluid-090e382c/7EN3agD0eenortiK/images/help/cowork/monday-watched-boards.png?fit=max\&auto=format\&n=7EN3agD0eenortiK\&q=85\&s=94e8cbbe0534ac9e38bfb706fe3ea4c9) Your watched boards, each with Stop watching. ## Send an item to Cowork On a watched board, set an item's send column to **Cowork**. Within about a minute, a Cowork ticket appears on your company's board, created by you. It carries: * the item's name as the title; * the text of the item's long text columns as the description, or a note linking to the item if it has none; * the item's board, group, and its status, date, timeline, people and dropdown values as details; * a link back to the item in monday. The ticket card shows a chip naming the board, for example **From monday · Client requests**. In the ticket, **Source** links back to the item. ![A Cowork ticket card with a From monday chip](https://mintcdn.com/fluid-090e382c/7EN3agD0eenortiK/images/help/cowork/card-from-monday.png?fit=max\&auto=format\&n=7EN3agD0eenortiK\&q=85\&s=237cc91fe435fcf79c0c678a71148cb8) A ticket sent from monday. ![A Cowork ticket from monday showing its source, request and link to the item](https://mintcdn.com/fluid-090e382c/7EN3agD0eenortiK/images/help/cowork/ticket-panel-monday-source.png?fit=max\&auto=format\&n=7EN3agD0eenortiK\&q=85\&s=c73d618b6b6cc46a04e5ccd5eb0c384a) The ticket's Source and Request, with the link back to the monday item. ### What isn't copied * **Updates** (monday's comments) are never copied. * **Text, number, email, phone, link and other columns** are left out, so values your company's ticket readers aren't meant to see stay in monday. * **Files** stay in monday. The ticket names them and links to the item. ## Stop watching or disconnect * **Stop watching:** click **Stop watching** next to a board in **Watched boards**. Fluid stops listening to that board. Tickets already created stay in Cowork. * **Disconnect:** click **Disconnect** in the **monday** section. Fluid also stops watching every board you watched, and items you send afterwards create nothing. Tickets already created stay in Cowork. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.