> ## 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. # Media > Upload images, videos and PDFs to your media library, tag them with products, set their status and SEO, and embed them. Use the **Media** screen to manage your company's media library: images, videos and PDF documents that you can tag with products and embed. ## Where to find it In the admin sidebar, under **Storefront**, select **Media**. To open this screen, your role needs **View only** or **Full access** for **Media**. To add, duplicate, edit or delete media, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Media** is in the **Content & Website** card. Open the card and set access from the **Media** area's menu, not the card's. ## What's on the screen The top of the page has a view switcher with three views: **Table view**, **Grid view** and **Grouped by product**. Next to it are **Export**, **Bulk Upload** and **Add Media**. Grid view is the default, and the screen remembers the view you last used. On small screens, the view switcher, **Export** and **Bulk Upload** are hidden. **Export** downloads a CSV file of your media with each item's title, type, file URL and status. Each media item has a status: * **Active**: published and live. * **Inactive**: a draft, hidden from public view. * **Scheduled**: set to go live at a future date and time. ### Grid view * Search with the **Search media...** box. * Use the sort menu to sort by **Title**, **Type** or **Date Created**, **Ascending** or **Descending**. The default is **Date Created**, newest first. Sorting by **Type** groups the page into **Images**, **PDFs**, **Videos** and **Other**. * Filter with **Type** (**Image**, **Documents** or **Videos**) and **Status** (**Active** or **Inactive**). **Clear Filters** removes both. * Click a card to open it. * Hover over a card to open its menu: **Preview**, **Edit** and **Delete**. * Hover over a card and tick its checkbox to select it. Once you've selected items, **Select all** selects every item on the page, and the **selected** menu offers **Associate to Products**, **Change Status**, **Clear Selection** and **Delete**. * At the bottom, choose **Items per page** (25, 50 or 100) and move with **Previous** and **Next**. ### Table view * The **All**, **Videos**, **Images** and **Documents** tabs filter by type. * Use the search box, and the filter button for **Type** and **Status**. * Columns: **Preview**, **Title**, **Type**, **Status**, **Countries** and **Date Modified**. You can sort by **Title** and **Date Modified**. **Countries** shows **All** when the item is available in every country you sell in. * Click a row to open the item. * Each row's actions menu has **Edit**, **Associate to Products**, **Change Status** (with **Set Active** and **Set Inactive**) and **Delete**. Select rows to use the same actions on several items at once from the table header's menu, where the labels include the count, such as **Set 3 Active** or **Delete 3 rows**. ### Grouped by product This view lists your products, 12 per page, with the media tagged to each. Search with **Search products...**, and use the **Media Status** filter to show products **With Media** or **Without Media**. Click a product's header to see all its media, and click a thumbnail to open that media item. ## Add a media item Click **Add Media**. The **New Media** page opens. In the **Media** card, click **Select Media** and choose one image, video or PDF. In **Media Details**, enter a **Title** (required) and, if you want, a **Description**. For a video, you can set its thumbnail with **Select Video Frame** or **Select New Image**. In **Tagged Products**, click **Add Product** to tag up to 100 products. Set the **Status**, **SEO And Link Sharing**, **Theme Template**, **Countries** and **Tags**. A new item starts as **Published**. Leave **Countries** empty to make the item available in every country you sell in. Click **Save**. The page changes to the new item's **Media Details** page. If your active theme has no default media template and you haven't chosen a **Theme Template**, a **Your theme has no media template** dialog appears when you save. Click **Create template** to create one and save the item. If you click **Not now**, the item isn't saved. To add a call-to-action button, click **CTA Button: Off** (or **On**) in the **Media** card, turn on **Enable call-to-action button**, choose the action (**Page**, **Cart**, **Email** or **Phone**), set it up, and click **Done**. Then save the item. ## Upload several files at once Click **Bulk Upload**. Click **Select Assets** and choose up to 20 assets from your asset library. A table shows one column per file. Each file gets a **Title** from its file name, with **Active** and **Search engine listing** turned on and all your countries selected. You can change the **Title**, **Active**, **Search engine listing**, **Description**, **Products**, **Media Theme**, **Countries** and **Tags** for each file. Tick the checkbox at the top of several columns, or **Select All**. A change you make in one ticked column then applies to all of them. **Title** and **Description** can't be edited while a column is ticked. Click **Create Media**. A confirmation message appears and you return to the media list. If your active theme has no default media template, the template dialog appears after the media are created. Your media are saved either way. ## Edit a media item Click the item in any view. Its **Media Details** page opens. Change the file with **Replace Media**, or change any field or card. Click **Save**. **Save** is available once you've changed something. On a saved item, the top of the page also has **Preview**, which opens the item's storefront page in a new tab, and an **Actions** menu with: * **Duplicate**: creates a copy titled with **- Copy** added, as a **Draft**, with the same tagged products. The copy includes any changes you haven't saved, and opens when it's created. * **Embed**: shows code you can copy to embed the item on a website or blog. * **Translations**: opens a panel where you translate the **Media Title** and **Description**, and choose a different file for each language. On very wide screens, **Translations** is a separate button. * **Delete**: deletes the item. ### Set the status In the **Status** card, choose **Published**, **Draft** or **Scheduled**, then click **Save**. For **Scheduled**, pick a date and time and click **Schedule Activation**. In the media list, **Published** items show as **Active** and **Draft** items as **Inactive**. Don't use **Scheduled** to keep an item private. Use **Draft** until you want it to be reachable. ### Set the SEO and link preview In the **SEO And Link Sharing** card, click **Edit**. Set the **SEO Image**, **Title Tag** and **Meta Description**, which control how the item looks in search results and when its link is shared. The **Preview** shows how the item looks as a **Google Search Result**, a **Text Message** or on **X (formerly Twitter)**. Turn off **Search engine visibility** to keep search engines from listing the item. Click **Done**, then click **Save**. **Done** stays unavailable until the **Title Tag** has at least 3 characters and the **Meta Description** at least 5; **Cancel** closes the panel without keeping your changes. When you first add an image file, it's also used as the SEO image unless you've already set one. ## Change the status of several items In grid view, select the items' checkboxes. In table view, select the rows. In grid view, open the **selected** menu, choose **Change Status**, then **Active** or **Inactive**. In table view, open the table header's menu, choose **Change Status**, then **Set 3 Active** or **Set 3 Inactive** (the number matches your selection). In the **Change status to Active?** or **Change status to Inactive?** dialog, click **Confirm**. ## Tag products to several items Select the items in grid or table view, then choose **Associate to Products** from the selection or actions menu. Add each product you want. Each product you add is tagged to all the selected items right away. Click **Done** when you're finished. To remove a tagged product, open the media item and remove it from **Tagged Products**, then click **Save**. ## Delete media Choose **Delete** from a card's menu, a row's actions menu, or the selection menu. On an item's page, choose **Delete** from the **Actions** menu. Confirm in the dialog. Deleting media can't be undone. ## Frequently asked questions Check that you've chosen a file in the **Media** card and entered a **Title**. If you're creating an item and the **Your theme has no media template** dialog appeared, choose **Create template**. If you choose **Not now**, the item isn't saved. Your role doesn't have **Full access** for **Media**. **Bulk Upload** is also hidden on small screens. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). ## Related pages * [Storefront](/help/admin/storefront) * [Products](/help/admin/products) * [Playlists](/help/admin/playlists) * [Roles](/help/admin/settings/roles) * [SEO](/storefront/seo) * [Country availability](/storefront/country-availability) * [Translations](/storefront/translations) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.