> ## 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. # Playlists > Create playlists of media and pages, tag products and enrollment packs, schedule them, and share or embed them on your storefront. A playlist groups media and pages into one storefront page you can share or embed, with products and enrollment packs tagged alongside. Use the **Playlists** screen to create, edit, schedule and delete them. ## Where to find it In the admin sidebar, under **Storefront**, select **Playlists**. To open this screen, your role needs **View only** or **Full access** for **Playlists**. To create, edit or delete playlists, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Playlists** is in the **Content & Website** card. Open the card and set access from the **Playlists** area's menu, not the card's. ## What's on the screen **Create Playlist** is at the top of the page. * The **All**, **Published**, **Scheduled** and **Draft** tabs filter the list by status. * Use the search box to find a playlist. * Click the **Title** column header to sort by title. * Use the previous and next controls at the bottom to page through the list. The list has these columns: * **Preview**: the playlist's image, or an empty frame when it has none. * **Title**: the playlist's title, or **Untitled**. * **Status**: **Published**, **Draft**, or **Scheduled** with the date and time it goes live. * **Countries**: flags for the countries the playlist is available in, with **+2** and so on when there are more. **All** means it isn't limited to any country. * **Owner**: **Company** for your company's playlists, or the member's name for a playlist a member made. * **Date Modified**: when the playlist last changed. Click a playlist to open it. Each row's actions menu has **Edit** and **Delete**. Select rows to delete several at once from the table header's menu, which reads **Delete 2 rows** and so on. A banner above the list lets you try a new version of the table. Click **Try it** to switch, or **Switch back** to return. The new table adds **Status** and **Country** filters. Your choice is saved in your browser. ## The playlist page The same page opens when you create a playlist, click a playlist in the list, or choose **Edit**. A new playlist's page is titled **New Playlist**. A saved playlist's page is titled **Playlist Details**, with its status badge next to its name in the breadcrumb. The main column holds: * **Playlist**: a preview of the playlist's media and pages, one at a time, with arrows when there's more than one. Click the preview to view it full screen. It appears once the playlist is saved. * **Playlist Details**: **Title** (required), **Description**, and **Media**, the image used when the playlist is shared. * **Playlist Items**: the media and pages in the playlist, in order. * **Tagged Products**: products and enrollment packs shown alongside the playlist. * **Metafields**: the custom fields your company defines for playlists. Each field has its own **Save**. **Manage Definitions** opens the [Metadata Definitions](/help/admin/settings/metadata-definitions) settings. The cards on the right: * **Status**: **Published**, **Draft** or **Scheduled**. A new playlist starts as **Draft**. * **SEO And Link Sharing**: a preview of how the playlist looks when its link is shared. Click **Edit** to change the SEO title, description and image. * **Countries**: the countries the playlist is available in. Leave it empty to make it available in every country you sell in. * **Theme Template**: the template from your theme that displays the playlist's page. * Analytics: **Shares**, **Page Speed** and **Content Compliance** for a saved playlist, plus **Page Views** when there's data. Click a metric for details. On a saved playlist, the top of the page also has an actions menu with **Delete**, and the **Embed**, **Translations** and **Preview** buttons. ## Tasks ### Create a playlist On the **Playlists** screen, click **Create Playlist**. Enter a **Title**. Add a **Description** and choose **Media** if you want them. Fluid builds the playlist's URL from the title. In **Playlist Items**, click **Add Item**, then choose the media and pages to include. In **Tagged Products**, click **Add Item**, then choose the products and enrollment packs to show with the playlist. Choose a **Status**, limit **Countries** if you need to, and choose a **Theme Template**. Click **Save**. If your active theme has no default playlist template, a dialog offers to create one. Click **Create template** to continue, or **Not now** to leave the playlist unsaved. When it's created, a confirmation message appears and the playlist's page opens. ### Edit a playlist In the list, click the playlist, or choose **Edit** from its actions menu. Change the details, status, countries, template or SEO. Click **Save**. A confirmation message appears and you stay on the page. On a saved playlist, items you add or remove in **Playlist Items** and **Tagged Products** are saved right away. To reorder items, drag them in their table, then click **Save**. To remove an item, open its row's menu and choose **Delete Item**. **Edit Item** opens the item's own page, such as the media item or product. ### Schedule a playlist On the playlist's page, in the **Status** card, choose **Scheduled**. Pick when the playlist should go live and click **Schedule Activation**. The card shows the scheduled date and time. Click **Save**. Scheduling isn't a privacy setting. Before the scheduled date, anyone with the playlist's direct link can still open it. The date controls when it appears in listings and can be indexed by search engines. ### Share, embed or translate a playlist On a saved playlist's page: * Click **Preview** to open the playlist on your storefront in a new tab. * Click **Embed** to get embed code for your website or blog, then copy it from the **Embed Playlist** window. * Click **Translations** to translate the **Playlist Title**, **Description** and **Playlist Image** into your company's active languages. ### Delete a playlist In the list, choose **Delete** from the playlist's actions menu. You can also open the playlist and choose **Delete** from the actions menu at the top of the page. In the **Delete Playlist** dialog, click **Delete**. Deleting a playlist can't be undone. ## Frequently asked questions **Save** stays grayed out until you change something. If you've made changes and it won't save, check that **Title** isn't empty. Your role can view playlists but doesn't have **Full access** for **Playlists**. The fields are grayed out and there's no **Save** button. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). The list includes playlists that members made for themselves. The **Owner** column shows the member's name for those, and **Company** for your company's playlists. The list no longer shows them. Open a playlist to see its items. ## Related pages * [Storefront](/help/admin/storefront) * [Media](/help/admin/media) * [Pages](/help/admin/pages) * [Products](/help/admin/products) * [Enrollments](/help/admin/enrollments) * [Visibility and scheduling](/storefront/visibility) * [Country availability](/storefront/country-availability) * [Translations](/storefront/translations) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.