> ## 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. # Files > Upload files to your company's file library, copy their links and variations, and organize them with tags. Use the **Files** screen to manage the files your company stores in Fluid: images, videos, audio, text files, documents and more. ## Where to find it In the admin sidebar, under **Content**, select **Files**. To open this screen and see your files, your role needs **View only** or **Full access** for both **Files** and **Media**. To upload, rename, replace or delete files, it needs **Full access** for both. On the [Roles](/help/admin/settings/roles) screen, **Files** and **Media** are in the **Content & Website** card. Open the card and set access from each area's menu, not the card's. ## What's on the screen The top of the page has **Upload File(s)**. Below it is the file list: * The **All**, **Images**, **Videos**, **Audio**, **Text**, **Documents** and **Other** tabs narrow the list. **All** doesn't list files in the **Text** or **Other** categories. * Search with the **Search...** box. * Click the filter button (funnel icon) to filter by **Tags**, then click **Apply Filters**. * Columns: **Preview**, **Name**, **Category**, **Created** and **Size**. A file's tags show under its name. The preview shows a thumbnail for images, the first frame for videos and the first page for PDFs. * Click a row to open the file's details page. Each row also has these buttons. Hover over a button to see its name. * **Copy asset link** (link icon): copies the file's link. * **Transform asset** (wand icon): opens the transform window. See [Transform a file](#transform-a-file). * **Edit tags** (tag icon): adds or removes tags. See [Tag files](#tag-files). * The **⋮** menu: **Replace asset** and **Delete**. ## Upload files Click **Upload File(s)**. The upload window opens on the option to upload from your computer. Select up to 10 files. The size limit is 100 MB. Confirm your selection in the upload window. A message confirms how many files were uploaded. ## View a file's details Click a file in the list. Its details page shows the file's title at the top, a preview, and these cards: * **Variations** (images and videos only): ready-made versions of the file, each with a link you can copy. * **Details**: the **Title**, the **Default URL** with a copy button, the **MIME type** and the **Size**. * **Actions**: **Transform** and **Replace**. * **Tags**: the file's tags. The preview shows images, plays videos and displays PDFs and text files. For other files, it shows **No preview available**. ## Copy a link * To copy the file's own link, click **Copy asset link** in its row, or the copy button next to **Default URL** on its details page. * To copy a variation's link, open the file and, in the **Variations** card, click the copy icon on that variation's thumbnail. A message confirms each copy. These variations are available: | File type | Variations | | :- | :- | | Image | **Square (512×512)**, **Widescreen (1280×720)**, **Low quality preview**, **High quality**, **Grayscale**, **Blurred** | | Video | **Low quality**, **High quality**, **Poster frame**, **Short clip** | ## Transform a file Click **Transform asset** in the file's row, or **Transform** in the **Actions** card on its details page. The transform window opens. When you finish, the link to the transformed version is copied to your clipboard. ## Rename a file Click the file in the list. In the **Details** card, click **Edit title** (pencil icon) and type the new title. To discard your change, press Escape or click **Cancel** (X icon). Click **Save** at the top of the page. **Save** is available once the title has changed, and the title can't be blank. ## Replace a file In the file's row, open the **⋮** menu and choose **Replace asset**. On the details page, click **Replace** in the **Actions** card. Pick the new file in the window that opens. An **Asset replaced** message appears. The file keeps the same link after you replace it. ## Tag files * In the list, click **Edit tags** (tag icon) in the file's row. Type a tag in the **Add tag...** box and press Enter. * On the details page, type a tag in the **Tags** card and press Enter. A tag is also added when you click away from the box. To remove a tag, click the **×** next to it. Each change saves right away. Tags are saved in lowercase, and a tag the file already has isn't added again. ## Delete a file In the file's row, open the **⋮** menu and choose **Delete**. On the details page, open the **⋮** menu at the top of the page and choose **Delete**. In the **Are you sure?** or **Delete asset** dialog, click **Delete**. If you deleted the file from its details page, you return to the file list. Deleting a file is permanent, and its links stop working. ## Frequently asked questions The **All** tab doesn't list files in the **Text** or **Other** categories. Open the **Text** or **Other** tab to see them. Click the filter button and enter the tags in **Tags**. Separate them with semicolons, such as `summer;sale`, to show files that have all of them. Separate them with commas, such as `summer,sale`, to show files that have any of them. Then click **Apply Filters**. Your role doesn't have **Full access** for both **Files** and **Media**. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). ## Related pages * [Content](/help/admin/content) * [Media](/help/admin/media) * [Forms](/help/admin/forms) * [Roles](/help/admin/settings/roles) * [DAM Picker SDK](/guides/dam-picker) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.