> ## 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. # Member Sites > Find the member sites in your company, open one, and review and delete the rows its members wrote in its database, including the roles that can. Use the **Member Sites** screen to see every member site in your company, a member's own sites included. Open a site to see its details and what it uses of a viewer's data. If the site keeps a database, you can also read the rows its members wrote and delete the ones that shouldn't be there. ## Where to find it In the admin sidebar, under **Website**, select **Member Sites**. > [!NOTE] > > To open this screen, your role needs **View** on **Application Themes**. To read a site's data, it also needs **View** on **Member Site Data**. To delete rows, it needs **Delete** on **Member Site Data**. See [Roles](https://docs.fluid.app/help/admin/settings/roles.md). Fluid turns member sites on for your company. If you don't see **Member Sites**, [contact support](https://docs.fluid.app/help/getting-help.md). ## The site list The list shows every site in your company, company-owned and member-owned. * The **All**, **Draft**, **Published** and **Taken down** tabs filter the list by status. * The **Owner** filter narrows it to **Company** or **Member** sites. * The box labelled **Filter this page…** narrows the page you're on by what you type. The list has these columns: **Name**, **Handle**, **Owner**, **Status**, **Visibility** and **Date Modified**. Click a row to open the site. ## A site's page A site's page shows its **Details**, an **Access** card that lists what the site uses of a viewer's data, who the site is shared with, and, when the site keeps a database, a **Data** card. ## Review a site's data A member site can keep its own data, such as RSVPs or guestbook entries. The **Data** card shows it. You see every row, whoever wrote it, whatever the site's rules say about who may read it. > [!NOTE] > > The **Data** card appears only when your role has **View** on **Member Site Data** and the site has an available database. Without the permission, or when the site has no available database, the page has no **Data** card. See [If you don't see the Data card](#if-you-dont-see-the-data-card). To read a site's data: **1. Open the site** On **Member Sites**, click the site's row. **2. Choose a table** In the **Data** card, click a table's name. The first table is chosen when the card opens. **3. Read the rows** The table lists the newest rows first, in groups of 25. Each row shows the table's columns, then the `id`, `created_by`, `created_at` and `updated_at` columns every table has. `created_by` is the id of the person who wrote the row. An empty value shows as a dash. **4. Move between pages** When a table has more than 25 rows, **Previous** and **Next** appear under it, with the range you're on, such as **26 to 50 of 61**. A long value is cut short in the table. Hold your pointer over it to see the whole value. A value that holds nested data is shown as JSON. The card can also say **This site's database has no tables.** or **This table has no rows.** If it says **Could not load the data**, click **Try again**. ## Delete a row Delete a row to remove something a member wrote, such as a spam entry. You can only delete here. You can't add a row or change one. > [!WARNING] > > A deleted row can't be restored. Your name is recorded with the deletion. **1. Find the row** Choose the table, then use **Next** and **Previous** to find the row. **2. Click Delete** Click **Delete** at the end of the row. You see this button only if your role has **Delete** on **Member Site Data**. **3. Confirm** In **Delete this row?**, click **Delete row**. Click **Cancel** to keep it. A message, **Row deleted**, confirms it. If it fails, you see **Failed to delete the row**. Try again, or check that your role still has **Delete** on **Member Site Data**. ## Give a role access to a site's data Reading and deleting rows are separate permissions, because the rows are what members wrote. Having access to **Member Sites** or to themes is not enough. 1. In the admin, click the **Settings** gear and, under **Company**, select **Roles**. 2. Open the role and type **Member Site Data** in **Search permissions...**. 3. Turn on **View** to let the role read rows. Turn on **Delete** to let it delete them. 4. Click **Save**. A role also needs **View** on **Application Themes** to open the **Member Sites** screen. See [Roles](https://docs.fluid.app/help/admin/settings/roles.md) for how roles work. ## If you don't see the Data card | What you see | Why | What to do | | - | - | - | | No **Data** card | Your role doesn't have **View** on **Member Site Data** | Ask an admin who manages roles to turn it on | | No **Data** card | The site has no database yet. A site gets one when its owner first publishes it with a `db/schema.json` | Nothing. The card appears after the owner publishes | | No **Delete** button | Your role has **View** but not **Delete** on **Member Site Data** | Ask an admin who manages roles to turn on **Delete** | | **Could not load the data** | The request failed | Click **Try again**. If it keeps failing, [contact support](https://docs.fluid.app/help/getting-help.md) | > [!NOTE] > > Email Fluid support at [help@fluid.app](mailto:help@fluid.app). The [Getting help](https://docs.fluid.app/help/getting-help.md) page lists what to include in your request. ## Download everything The screen doesn't download a site's data. To save every table and row of a site as one file, use the API. See [Download the data](https://docs.fluid.app/member-sites-v1/database.md#download-the-data) for the file and [Download a site's database](https://docs.fluid.app/api-reference/member-site-database/download-a-sites-database.md) for the request. It needs a signed-in admin with **View** on **Member Site Data**. A company API token on its own can't use it. ## Related pages * [Roles](https://docs.fluid.app/help/admin/settings/roles.md): set what each role can see and do. * [The member site database](https://docs.fluid.app/member-sites-v1/database.md): how a developer declares tables and the rules that decide who writes to them. * [Website](https://docs.fluid.app/help/admin/website.md): the other website screens. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.