> ## 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. # Enrollments > Build enrollment packs that bundle a product, a subscription, agreements and a fee, then schedule or publish them on your storefront. Use the **Enrollments** screen to manage your company's enrollment packs. A pack bundles a one-time product, a subscription product, legal agreements and an optional fee. When a shopper adds a pack to their cart, the cart becomes an enrollment. ## Where to find it In the admin sidebar, under **Storefront**, select **Enrollments**. To open this screen, your role needs **View only** or **Full access** for **Enrollments**. To create, edit or delete packs, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Enrollments** is in the **Commerce** card. Open the card and set access from the **Enrollments** area's menu, not the card's. ## What's on the screen **Add Enrollment** is at the top of the page if your role can create packs. Below it is the list of packs. * The **All**, **Published**, **Scheduled** and **Draft** tabs filter the list by status. * Use the search box to find a pack. * The filter panel has **Status** and **Country Availability**. Choose values and click **Apply Filters**. **Country Availability** takes one country at a time. The list has these columns: * **Preview**: the pack's primary image. * **Title**: click it to open the pack. You can sort by this column. * **Status**: **Published**, **Draft**, or **Scheduled** with the date and time it goes live. * **Countries**: flags for the countries the pack is limited to. **All** means the pack has no country limit. * **Date Modified**: when the pack was last changed. You can sort by this column. Each row's actions menu has **Edit**, **Duplicate** and **Delete**. Select rows to use the same menu in the table header, labeled with the count, such as **Duplicate 3 rows**. A banner above the list lets you try a new version of the table. Click **Try it** to switch, and **Switch back** to return. In the new table, the status and country filters are in the **Filters** menu. ## Create an enrollment pack On the **Enrollments** screen, click **Add Enrollment**. The **New Enrollment** page opens with the status set to **Draft**. In the **Enrollment Details** card, enter a **Title** and a **Description**. Both are required. **Member Type** sets the member type that buyers of this pack enroll into. If you leave it unset, the pack takes your company's default rep type when it's saved. Under **Media**, click **Upload Images** and choose up to 10 images at a time. JPG, PNG, GIF, WebP, BMP and SVG files up to 10MB are supported. The first image is the primary image. To change it, hover over another image and click its star icon. To remove an image, click its trash icon and confirm. In the **Pack Details** card, click **Select Product** and pick one product variant. The pack needs a product, a subscription, or both. Click **Select Subscription**. The list shows only products that have subscription plans. After you pick a variant, choose a plan from **Select plan** in the **Frequency** column. A subscription can't be saved without a plan. In the **Agreements** card, turn on the switch for each legal page buyers should see. Active agreements are grouped as **Optional**, **Required** or **Footer**, based on how each agreement is set up. Drag an agreement to reorder it within its group. To add or change legal pages, click **Manage All Legal Pages**. In the **Enrollment Cost** card, enter an **Enrollment Fee (Optional)** in USD. The fee is shown in the currency of the country the buyer selects at checkout. The **Initial Costs** summary shows the product price, the fee, and the subscription price and frequency. In the **Countries** card, choose the countries where the pack is available. Leave it empty to offer the pack in every country you sell in. In the **Theme Template** card, choose the template the pack's page uses. If your theme has no enrollment template, choose **Create Template**. Click **Create Enrollment**. The button is available once the pack has a title, a description and a product or subscription. The pack's page opens and a confirmation message appears. The **Metafields** card and the **SEO And Link Sharing** card are optional. The SEO card previews how the pack appears in a Google search result and in a text message, and lets you change its SEO image and text. ## Edit a pack In the list, click the pack's title, or choose **Edit** from its actions menu. Change any card on the page. Click **Save**. The button is available when you have unsaved changes. The pack's page also has: * **Preview**: opens the pack on your storefront in a new tab. * **Translations**: edit the **Enrollment Title** and **Description** for each of your languages. On narrower screens, it's in the actions menu. * **Analytics**: on a saved pack, shows **Page Views**, **Shares**, **Page Speed** and **Content Compliance**. Click a metric for details. * The actions menu, with **Duplicate**, **Reset Cache** and **Delete**. **Reset Cache** refreshes the pack's cached storefront page. ## Publish or schedule a pack Open the pack from the list. In the **Status** card, choose **Published** to make the pack live, or **Draft** to hide it. To publish later, choose **Scheduled**, pick a date and time, and click **Schedule Activation**. Click **Save**, or **Create Enrollment** for a new pack. Scheduling isn't a privacy setting. Before its scheduled date, a pack is already reachable by direct link. Until then, it doesn't appear in storefront listings and search engines can't index it. ## Duplicate a pack Choose **Duplicate** from a pack's actions menu in the list, or from the actions menu on the pack's page. The copy gets the original's title with **(Duplicate)** added. It keeps the product, subscription, agreements, images, countries, fee, status and SEO settings. From the pack's page, the copy opens when it's ready. From the list, the list refreshes and returns to its first page, and a confirmation message shows how many packs were copied. The copy has the same status as the original, so a copy of a published pack is published too. Change its status before you edit it if you don't want it live. ## Delete a pack In the list, choose **Delete** from the pack's actions menu. To delete several packs, select their rows and choose **Delete** from the table header's menu. You can also choose **Delete** from the actions menu on the pack's page. In the confirmation dialog, click **Delete**. Deleting a pack can't be undone. ## Frequently asked questions The pack needs a **Title**, a **Description**, and a product or subscription. On a saved pack, **Save** is also grayed out until you change something. If you can't change any fields, your role doesn't have **Full access** for **Enrollments**. Choose a plan from **Select plan** next to the subscription product. A subscription product without a plan can't be saved. Yes. The product and subscription pickers list products you've already created. A product appears in the subscription picker only if it has at least one subscription plan. See [Products](/help/admin/products) and [Subscription Plans](/help/admin/settings/subscription-plans). The pack has no country limit, so it's available in every country you sell in. To limit it, choose countries in the pack's **Countries** card. The **Agreements** card lists your company's legal pages. Whether an agreement is optional, required or shown in the footer comes from the agreement itself. To change that, or to add a new one, click **Manage All Legal Pages**. See [Agreements](/help/admin/settings/agreements). ## Related pages * [Storefront](/help/admin/storefront) * [Products](/help/admin/products) * [Subscription Plans](/help/admin/settings/subscription-plans) * [Agreements](/help/admin/settings/agreements) * [Forms](/help/admin/forms) * [Member Types](/help/admin/settings/member-types) * [Roles](/help/admin/settings/roles) * [We-Commerce](/concepts/we-commerce) * [Country availability](/storefront/country-availability) * [Visibility](/storefront/visibility) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.