> ## 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. # Mastering shareable content: a guide for direct sellers > Give your team photos, videos and documents worth sharing, keep them consistent and compliant, and use what you learn to improve your content mix. The right content turns casual browsers into loyal customers. This guide covers what to give your team to share, how to keep it consistent and compliant, and how to tell what's working. ## Why shareable content matters Shareable content is your digital storefront. Every piece your team shares shapes how customers see your brand. When you give reps carefully chosen content to share, your message stays consistent while their connections stay personal. Consistency helps you: * Build brand recognition and trust * Stay compliant across channels * Give reps professional resources they can use right away ## Content that converts ### Visual stories that sell Visual content makes an instant connection. The most effective mix includes: **Photos:** * Before-and-after results * Lifestyle images that inspire action * Real people using real products * Behind-the-scenes glimpses of your culture **Videos,** about 1 to 3 minutes long: * Quick tutorials that solve problems * Unscripted testimonials * Live product demonstrations * Team celebrations that show your culture ### Resources that build credibility Back up your visual content with: * Well-designed product catalogs * Step-by-step training guides * Roadmaps for new team members * Compliance documentation ## Hook viewers in the first 3 seconds You have about three seconds to stop the scroll. Start with movement, open with something intriguing, and lead with your strongest result. Then keep the attention you've earned: * Keep videos short and to the point. * Add captions. Many people watch with the sound off. * End with a clear call to action. ## Make sharing easy for your team Reps share more when the content is easy to find and easy to send. In the mobile app, reps share from the Share screen, which your company builds in the admin's [Share Tabs](/help/admin/mobile/share). Give them: * Content that's ready to share from their phones * Up-to-date versions as soon as you change something * Wording your company has approved Then help them get good at sharing, with training sessions, best practices such as this Playbook, and feedback on what works. ## Measure what matters Watch these signals: * **Views** tell you what captures attention. * **How often reps share** shows team adoption. * **Engagement** shows content quality. * **Orders** show what really works. Use what you learn to: 1. Find your top-performing content. 2. Improve when and how often you share. 3. Refine your content mix. 4. Adjust your training. ## Play it safe: compliance guidelines **Do:** * Share real, verified experiences. * Focus on lifestyle benefits. * Stay within the claims your company has approved. * Use clear, compliant language. **Don't:** * Make income claims or guarantees. * Make medical claims. * Use hard-sell tactics. * Compare yourself to competitors. ## Use Fluid to share smarter * **Playlists** put content in a deliberate order, to guide each prospect from first look to purchase. See [Smart playlists](/help/playbook/transform-your-sales-with-smart-playlists). * **Catch Up** in the mobile app suggests follow-ups when contacts engage, for example when someone views a page a rep shared or starts a video without finishing it. Your company chooses which suggestions are on in [Catchups](/help/admin/settings/catch-ups). ## Your action plan 1. **Audit and plan.** Take stock of your content and find the gaps. Plan new material that fills them and supports your goals. 2. **Set your team up.** Organize what reps share in the app, and make sure everyone knows where to find it. 3. **Monitor and adapt.** Track your key signals, gather feedback, and keep refining your approach. The most effective content strategy balances professional polish with authentic connection. Keep it real, keep it compliant, and measure what works. ## Frequently asked questions **Photos** | Category | Purpose | Best practices | | - | - | - | | Before and after | Show results | Real results, consistent lighting, a side-by-side format | | Lifestyle | Create connection | Authentic moments, natural settings, relatable scenes, diverse people | | Product in use | Show the value | Clear demonstrations, several angles, a size reference | | Culture | Build community | Team celebrations, behind the scenes, real team members | **Videos** | Type | Length | Focus | Best practices | | - | - | - | - | | Tutorials | 1 to 3 minutes | Quick solutions | Step by step, clear visuals, on-screen text | | Testimonials | 1 to 2 minutes | Real stories | A natural setting, unscripted, key points on screen | | Demonstrations | 2 to 3 minutes | Clear benefits | Close-ups, several angles, usage tips | | Team content | 1 to 2 minutes | Culture and community | Candid moments, energy and enthusiasm | **Recommended specs.** These are general guidelines, not limits that Fluid enforces: * Images at least 1200 × 1200 pixels, as JPG or PNG * Video at 1080p or higher, as MP4 * A 1:1 or 9:16 aspect ratio, which works best on phones Hook viewers in the first 3 seconds with movement, intrigue or a strong result, and make your first frame your most compelling one. Include your brand elements subtly but consistently, so people learn to recognize you. ## Related pages * [Scroll-stopping video](/help/playbook/creating-scroll-stopping-video-content) * [Smart playlists](/help/playbook/transform-your-sales-with-smart-playlists) * [Media](/help/admin/media) * [Share Tabs](/help/admin/mobile/share) ## Get help Email Fluid support at [help@fluid.app](mailto:help@fluid.app). The [Getting help](/help/getting-help) page lists what to include in your request. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.