> ## 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. > To host a small project on Fluid (a landing page, event page, calculator or dashboard), follow /sites/quickstart: npm create @fluid-app/fluid-site my-site (or npx @fluid-app/create-fluid-site my-site), fluid login, then fluid deploy prints the public URL. Launch a Site unless the project needs a custom domain, server rendering or heavy server code, which make it an App (a Mist app); /sites/site-or-app has the rule, and POST /api/company/v2026-10/project-launch-recommendations applies it. With only the Fluid MCP server (its Site write tools are limited to Fluid root admins today; see /sites/deploy-from-claude), use site_create, then site_deploy (from a chat with no shell, in one call with the files inline: site_template_get for a starter, then site_deploy with each path's content; or a built folder in two calls: send the manifest, PUT the listed uploads, call again with the bundle_id to get the url), then, only after the person confirms they want it public, site_visibility_set. site_logs, site_traffic, site_env_list/set/unset, site_seo_get/set and the site_branch tools cover logs, traffic, env vars, SEO and preview branches; a member builds their own Sites with the my_site_* tools. The MCP server can't publish server functions or convert a Site to an App, so use the fluid sites CLI for those. A Site can serve light server code: each functions/.ts, declared in config/functions.json with access public, signed_in or key (and an optional UTC cron schedule), answers at /api/ on the Site's own host; publish it with fluid deploy (the MCP site_deploy tool does not carry functions). See /sites/functions and /sites/rest-api. > 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. # Cowork tasks > Create, list and change the tickets on your company's Cowork board with the Cowork API, from your own code or a Site's server function. Cowork is your company's shared board of work. Each ticket on it is a task: people file it, plan it, assign it and finish it, Mist can work on it, and your company can send it to an agency. The Mist task board and Cowork in the Fluid admin are built on the [Cowork API](https://docs.fluid.app/api-reference/cowork-tasks/list-the-companys-work.md), so anything they do with a task, your code can do too. This guide covers creating a task, reading the board's tasks and changing one. The API reference covers the rest: discussions, attachments, Mist runs and agency requests. ## Before you start Every Cowork endpoint needs a Bearer token for a person, sent as `Authorization: Bearer `. The token must belong to a company admin. A company API token is refused with `403`, because Cowork records every write against the person who made it. The person's role needs the permission for what you do: | To | Permission | | - | - | | Create a task | `multiplayer_tasks.create`, or `application_themes.update` | | Read tasks | `multiplayer_tasks.view`, or `application_themes.view` | | Change a task | `multiplayer_tasks.update`, or `application_themes.update` | ## Create a task Send the task to [Submit standalone company work](https://docs.fluid.app/api-reference/cowork-tasks/submit-standalone-company-work.md): ```bash theme={null} curl -X POST https://api.fluid.app/api/v202604/multiplayer/tasks \ -H "Authorization: Bearer $FLUID_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "task": { "client_id": "intake-form-4821", "title": "Update the spring launch banner", "description": "The banner still shows last week'\''s dates.", "due_on": "2026-11-20" } }' ``` * `client_id` is your own identity for this submission, unique within the company. It takes letters, digits, `_` and `-`. Sending the same submission again returns the task already stored, so a retry never makes a second ticket. A different submission with a `client_id` already used answers `409`. * `title` is required, up to 255 characters. * `description` is optional, up to 10,000 characters. * `due_on` is optional: a calendar day, `YYYY-MM-DD`. A day that doesn't exist, such as `2026-02-30`, is refused with `422`. The answer is `201` with the new task under `task`. Keep its `id` and its `lock_version`: you need both to change it. A new task starts `open`. ## Read the tasks [List the company's work](https://docs.fluid.app/api-reference/cowork-tasks/list-the-companys-work.md) returns undeleted tasks, the most recently updated first: ```bash theme={null} curl "https://api.fluid.app/api/v202604/multiplayer/tasks?filter[status]=open,needs_info&page[limit]=50" \ -H "Authorization: Bearer $FLUID_TOKEN" ``` * Results use cursor pagination. Ask for up to 100 tasks with `page[limit]` (25 by default), and pass the cursor from `meta.pagination.next_cursor` as `page[cursor]` for the next page. * `filter[status]` keeps the statuses you list, comma-separated. * `filter[assignee]` keeps tasks assigned to one person by their user id, to nobody (`unassigned`), or to Mist (`agent`). * `sort` is `updated` (the default), `board` for the order the board draws a column, or `due`. ## Change a task Each change below carries `expected_version`: the `lock_version` you last read. If someone changed the task since, the change is refused with `409`, and the answer includes the current task, so retry against that one. [Change what the company's work says](https://docs.fluid.app/api-reference/cowork-tasks/change-what-the-companys-work-says.md) changes the title, description, kind, priority or due date. Send only what changes: ```bash theme={null} curl -X PATCH https://api.fluid.app/api/v202604/multiplayer/tasks/$TASK_ID \ -H "Authorization: Bearer $FLUID_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "task": { "expected_version": 0, "priority": "high" } }' ``` `priority` is `urgent`, `high`, `medium`, `low`, or `null`. `kind` is `bug`, `change`, `feature`, `design`, `support`, or `null`. Status and owner have routes of their own: * [Record a person's verdict on the company's work](https://docs.fluid.app/api-reference/cowork-tasks/record-a-persons-verdict-on-the-companys-work.md) moves the task with `status_change`. Its `status` is `open`, `needs_info`, `in_progress`, `review` or `skipped`. In a company with Cowork on, only the people working a ticket move it, such as its assignee. Anyone else is refused with `403`. * [Say who owns the company's work](https://docs.fluid.app/api-reference/cowork-tasks/say-who-owns-the-companys-work.md) assigns the task with `assignment`. Its `assignee` is `{ "kind": "user", "user_id": 42 }` for an admin of the company, or `null` for nobody. ## Create tasks from a Site On a company Site, the page can call Cowork itself, as the admin who has it open. Declare `cowork: write` (and `cowork: read` to list tickets) in `config/access.json`, have your company allow `cowork` under **Visitor data**, and call `/cowork/tasks` with `fluid.api`. Each call does what the visitor could do with their own sign-in, so a visitor who can't use Cowork gets `403`. See [File a Cowork ticket](https://docs.fluid.app/sites/member-api.md#file-a-cowork-ticket). That only reaches Cowork as the visitor, on a company Site. To file tickets for visitors who can't use Cowork themselves, or from a member's own Site, use a [server function](https://docs.fluid.app/sites/functions.md) instead. A function has no Fluid credential of its own that reaches Cowork, so keep an admin's token as a [secret](https://docs.fluid.app/sites/env-vars.md) and call the API with `fetch`: ```ts functions/file-ticket.ts theme={null} export default async function (request: Request, ctx: any): Promise { if (request.method !== "POST") { return Response.json({ error: "method_not_allowed" }, { status: 405 }); } const viewer = ctx.caller.kind === "page" ? ctx.caller.viewer : null; if (viewer === null) return Response.json({ error: "sign_in_required" }, { status: 401 }); const { title, details } = await request.json(); if (typeof title !== "string" || title.length === 0 || title.length > 255) { return Response.json({ error: "invalid" }, { status: 422 }); } const res = await fetch("https://api.fluid.app/api/v202604/multiplayer/tasks", { method: "POST", headers: { Authorization: `Bearer ${ctx.secrets.COWORK_TOKEN}`, "Content-Type": "application/json" }, body: JSON.stringify({ task: { client_id: `site-${crypto.randomUUID()}`, title, description: `${details ?? ""}\n\nFiled by ${viewer.name} from ${ctx.site.handle}.`, }, }), }); return new Response(res.body, { status: res.status, headers: { "Content-Type": "application/json" } }); } ``` Give the function `signed_in` access in `config/functions.json`, so only signed-in visitors can file. Every task it makes is created as the admin whose token it holds, so the function names the visitor in the description. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.