> ## 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. # Creating scroll-stopping video content > Hook viewers in the first seconds, plan the right kinds of video, get the technical basics right, and use what viewers do to improve. Videos that catch attention start conversations. This guide covers how to hook viewers, what to film, and how to learn from what they watch. ## The 3-second challenge People scroll fast, so you have only a few seconds to make an impact. Hook your audience right away: * Start with movement. * Open with an intriguing question. * Show your product in action. * Lead with your best result. Think of your opening like a newspaper headline: it has to grab attention and promise value. ## Content that converts Include three kinds of video. ### Before-and-after stories Nothing sells like transformation. Show: * Product results * Real lifestyle changes * Highlights from your business journey Authenticity matters more than polish. Real stories resonate. ### Quick tips and tutorials Become the go-to expert with: * 30-second product demonstrations * Simple how-to guides * Daily tips that solve common problems The best tutorials feel like advice from a friend, not a lecture. ### Behind the scenes Build trust through transparency: * Product unboxings * Day-in-the-life clips * Team celebrations and milestones ## Get the technical basics right **Lighting:** * Face natural light. * Avoid harsh overhead lighting. * Consider a simple ring light. **Sound:** * Record in a quiet space. * Speak with energy and clarity. * Always add captions. Many people watch with the sound off. **Framing:** * Keep the camera steady. * Film training content in landscape. * Film social content in portrait. ## A simple structure Plan your video like a short movie: 1. **Hook, about 3 seconds:** grab attention with something unexpected. 2. **Problem, about 5 seconds:** name your viewer's pain point. 3. **Solution, about 10 seconds:** show how you can help. 4. **Proof, about 10 seconds:** show real results. 5. **Call to action, about 5 seconds:** tell viewers exactly what to do next. Aim for 30 to 45 seconds in total. Shorter is often better. ## Share it with Fluid 1. Choose your best video. 2. Write a caption that sparks curiosity. 3. Include a clear call to action. 4. When you send it to a specific person, share it as a SmartLink, so you can see when they watch. 5. Share it on more than one channel. ## Boost engagement ### Test and learn * Try different video lengths. * Test different thumbnails. * Experiment with posting times. * Compare different types of content. Let your results guide what you make next. ### Get the timing right * Find out when your audience is most active. * Post consistently in those windows. * Test different days of the week. * Consider your audience's time zone. ### Follow up fast The moment someone watches your video is your best chance to connect. In the mobile app, **Catch Up** can suggest a follow-up when a contact starts one of your videos but doesn't finish it, if your company turns that suggestion on in [Catchups](/help/admin/settings/catch-ups). Then: * Answer comments and questions while interest is high. * Share related content. * Start a real conversation. The faster you engage with viewers, the more likely they are to become loyal followers and customers. ## Mistakes to avoid * Language that's too sales-focused * Poor lighting or shaky footage * Long, complicated explanations * Generic content that isn't personal ## Track your results Watch: * How much of each video people watch * How often people click through * Which videos lead to sales * When people engage Your first video won't be perfect, and that's fine. Authenticity often beats perfection. Start creating, start sharing, and refine as you learn. ## Frequently asked questions Focus on the first 3 seconds. Start with movement, open with a question, show the product in action, lead with your best result, use text on screen for people watching without sound, and break the pattern viewers expect. **Hooks by type of video** | Type | Hook strategy | Example | | - | - | - | | Product demo | Show the end result first | "Look what this can do in 30 seconds!" | | Tutorial | Name a common problem | "Tired of \[a pain point]? Here's a 30-second fix." | | Story | Lead with the transformation | "How I went from skeptic to fan in one month" | | Lifestyle | Create a curiosity gap | "The morning routine that changed everything" | | Behind the scenes | Offer exclusive access | "What really happens before we ship" | | Quick tip | Share a surprising fact | "The number one mistake people make with \[product]" | **Make the first frame count** | Element | Best practice | Example | | - | - | - | | Thumbnail | A high-contrast image | A before-and-after split screen | | Text on screen | 3 or 4 words at most | "Watch this first" | | Movement | Dynamic action | The product at work | | Faces | Genuine emotion | An authentic reaction | | Colors | Your brand palette | Consistent with your identity | Test different hooks with the same content to find what works for your audience. If the first frame wouldn't stop the scroll as a still image, it won't work as a video either. See [The 3-second challenge](#the-3-second-challenge). ## Related pages * [Shareable content](/help/playbook/mastering-shareable-content-a-guide-for-direct-sellers) * [Authentic conversations](/help/playbook/beyond-the-sales-pitch-creating-authentic-digital-conversations-that-convert) * [Media](/help/admin/media) ## 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.