> ## 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. # Sharing content > Share items from the Share tab by link, QR code or smart link, create trackable links, and see who engaged in Recent Activity. Use the **Share** tab to find the media, pages, products and other content your company provides for you to share. You can send an item to a contact, post its link anywhere, and see who engaged with it. ## Where to find it In the app, tap the **Share** tab. ## What's on the screen The top bar shows the **Share** title and a plus icon that opens the **New Shareable** menu. See [Create a trackable link](#create-a-trackable-link). Your company builds the rest of the Share tab, so it varies. If it has more than one tab, the tabs run across the top, with names your company chooses. Your Share tab may include tabs such as **Media**, **Pages**, **Products** and **Enrollments**. It may also include **Uploads** and **Playlists** tabs for your own content, which [Playlists and content](/help/mobile/playlists) covers. ### Sections Some tabs are made of sections. Each section shows a row of items under a title. * If a title has an info icon, tap it to read the section's description. * Tap the arrow button next to a title to open the section's page, where you can switch between a list and a grid. * Tap an item to open it. Press and hold an item to open its menu. See [Item menu](#item-menu). * At the bottom of the tab, a round filter button opens **Filter + Sort**. Choose a **Country** and **Language**, then tap **Apply**. The Share tab then shows content for your choices. ### Item lists Other tabs list one kind of item, such as media or products. Each item shows its **Views** and **Leads**, and products and enrollment packs show their price. Use the search box at the top to search the list. The filter button at the top opens **Filter + Sort**, where you can sort the list and filter it by **Country** and **Language**. Media lists also filter by **Tags**, **Category** and **Type**. Tap **Apply** to use your choices. ### Item menu Press and hold an item in a section to open its menu: * **Add to MySite**: show the item on your [MySite](/help/mobile/my-site). * **Add to Playlist**: add it to one of your playlists. * **Save for Later**: add it to your saved items. * **Copy Share Link**: copy the item's share link. * **Create Smart Link**: send the item to a contact. See [Send a smart link to a contact](#send-a-smart-link-to-a-contact). Playlists don't have **Add to Playlist** or **Save for Later**, and items in your saved-items section don't have **Save for Later**. Tap outside the menu to close it. ### Saved items If your Share tab has a section for your saved items, tap its arrow button to open your saved items. There you can switch between a list and a grid and drag items into a new order. Tap an item's minus button to remove it from your saved items, or its share icon to share it. ### Item pages Each kind of item has its own page: * **Media**: the picture or video at the top, with the title, a QR code, your share link and a **Share** button. Below are the description and **Visitor Detail**, which shows the item's **Views** and **Leads**. * **Product**: the same top area, then two tabs. **Related Shareable** shows the price, the description and the product's marketing media, which you can filter by type and tap to open. If your company uses reward points, it also shows the points the product earns. **Analytics** shows **Visitor Detail**. * **Page**: a preview of the page, under the banner **Preview mode. Share link for full use.** * **Enrollment pack**: the pack's pictures or video, description and price, then the products it includes. Tap **Learn More** under a product to open it. On media, product and page items, the three-dots button at the top opens the **Add To** menu. Its **MySite**, **Playlists** and **Save for Later** options work like the ones in the [item menu](#item-menu). On media, it also has **Copy to Uploads**, which copies the item to your uploads. Pages and enrollment packs have a bar at the bottom with the item's **Views** and **Leads** and a **Share Link** button. Tap the views and leads to open a map of the item's views, with its **Leads** listed below. ## Tasks ### Share an item On a media or product page, tap **Share** at the top. On a page or enrollment pack, tap **Share Link** at the bottom. The **Quick Share** drawer opens. The top of the drawer shows your share link and a QR code for it. * Tap the link to copy it. * Tap **Preview** to open the link in preview mode. * Tap **Share** to send the link with another app on your phone. * Tap **Download** to download the item's picture or file. Under **Send To Your Contacts**, search by name or email, or tap a group to show only its contacts. Tap **Send** next to a contact. Then tap the email, message or three-dots icon to send them a link made for them by email, text message or another app. After 5 seconds, the icons turn back into **Send**. The email and message icons appear only when the contact has an email address or phone number. The drawer lists up to 100 contacts at a time, so search to find others. ### Send a smart link to a contact A smart link is a link made for one contact. **Send** in the share drawer creates one. You can also start from an item in a section: Press and hold the item, then tap **Create Smart Link**. Your contacts list opens. Tap the contact. The **Method** menu opens. Tap **Send via Text** or **Send via Email** to start a message to the contact with the link in it. Each appears only if the contact has a phone number or email address. Or tap **Copy Smart Link** to open your phone's share options, where you can copy the link or send it with another app. ### Track engagement in Recent Activity Tap your profile picture at the top of **Home**, then tap **Recent Activity**. The **Activity** screen opens, and your new activity is marked as read. **All Activity** lists all your activity, and **Last 7 Days** lists the last seven days. Each entry shows the contact's name, or **Visitor** and a number when it isn't tied to a contact. It also shows the date, what happened and the item it's about. Tap an entry to see its title, date and description. * Tap the contact's name to open their page in [Contacts](/help/mobile/contacts). * For a visitor, the row reads **Someone near** and their city and state. Tap it to see the visitor's details. * If the entry is about an item, tap the item's card to open it. The visitor page has two tabs. **Activity** lists that visitor's activity. **Profile** shows details such as their **Country**, **Campaign**, **Source** and **Term**. If your Home tab has a **Recent Activity** section, tap it to open the **Activity** screen on **Last 7 Days**. ### Create a trackable link A trackable link saves a web address, such as `https://shop.example.com/spring-sale`, as an item you can share. On the **Share** tab, tap the plus icon at the top. Tap **Create Trackable Link**. Paste the web address into the field. The app fetches the page and shows a preview card with its title, description and picture. If it can't, **Cannot fetch the url. Try again.** appears. Tap **Publish**, which turns on once the preview card appears. The **Uploads** screen then opens. The **New Shareable** menu also has **Create Playlist**, and **Create Media** if your company lets you add your own media. See [Playlists and content](/help/mobile/playlists). ## Tips * Before you send something, tap **Preview** in the share drawer to see your link in preview mode. * Use **Save for Later** for items you share often, so they're together in your saved items. * While a file is uploading, the plus icon at the top of the Share tab doesn't respond. Wait for the upload to finish. ## Frequently asked questions Open the product from your **Share** tab and tap **Share**. Under **Send To Your Contacts**, tap **Send** next to the customer and choose how to send it. Later, check **Recent Activity**, or the **Activity** tab on the customer's page in [Contacts](/help/mobile/contacts). * **Recent Activity**, on your Dashboard. See [Track engagement in Recent Activity](#track-engagement-in-recent-activity). * Each item's **Views** and **Leads**, on its card in a list and on its page. For a product, they're on the **Analytics** tab. * The **Activity** tab on a contact's page in [Contacts](/help/mobile/contacts). * The **Recent Activity** section on your Home tab, if your company added one. * **General share link**: the link at the top of the share drawer. Its QR code, its **Share** button and **Copy Share Link** use the same link. It's the same no matter who you share it with, and it isn't tied to a contact. Use it for posts many people see, such as on social media. * **Smart link**: a link made for one contact. You create one when you tap **Send** next to a contact in the share drawer, or with **Create Smart Link**. Use it when you share with one person. In **Recent Activity**, an entry tied to a contact shows the contact's name. Other entries show a visitor, such as **Visitor 1234**. Open an item from the **Share** tab and tap **Share** or **Share Link**. Then copy or share your link, or send it to a contact. See [Share an item](#share-an-item) and [Send a smart link to a contact](#send-a-smart-link-to-a-contact). ## Related pages * [Getting around the app](/help/mobile/getting-around) * [Playlists and content](/help/mobile/playlists) * [MySite](/help/mobile/my-site) * [Contacts](/help/mobile/contacts) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.