> ## 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. # Beyond the sales pitch: creating authentic digital conversations that convert > Share content and write messages that start real conversations with prospects, then follow up at the right moment when they engage. People respond to conversations, not pitches. This guide covers what to share, how to word your messages, and when to follow up. ## Share content that connects Whether you share through Fluid or on social media, share things the other person will find useful or interesting: * Product demonstrations * Success stories * Team achievements * Training resources * Business opportunities ### Mix your content types Each type of content does a different job. **Photos** make a quick connection. A single strong image can tell a story faster than a paragraph. Share: * Before-and-after results * Real people using real products in everyday situations * Candid team celebrations * Lifestyle images that inspire **Videos** build trust, because people can see and hear you. Share: * Short tutorials, about 1 to 3 minutes long * Unscripted testimonials that sound like a friend's recommendation * Behind-the-scenes clips * Live product demonstrations **Documents** carry detail and look professional. Share: * Product catalogs * Step-by-step training guides * Roadmaps for new team members * Event playbooks ## Write messages that start conversations ### Replace pitches with personal messages | Avoid | Try instead | | - | - | | "Amazing opportunity!" | "Sarah, remember how you mentioned..." | | "Life-changing products!" | "This addresses exactly what we discussed..." | | "Check this out!" | "Based on your interest in natural wellness..." | | "Don't miss out!" | "I thought of you when I saw this..." | ### What every message needs 1. **Personalization.** Use their name and something they told you. * "Michelle, since you're passionate about clean beauty..." * "John, following up on our conversation about growing your business..." 2. **Value first.** Lead with something that helps them. * "This quick video shows how to get the results we talked about..." * "Here's the solution we discussed for your skincare concerns..." 3. **A natural call to action.** Invite a reply without pressure. * "When you have a moment, I'd love your thoughts on this." * "Let me know if you'd like to hear more about what worked for me." ## Make videos people watch Video works because it puts a face to your message. People see real experiences and real results, which builds trust. **Before you record:** * Outline your key points, but stay natural. * Choose a clean, well-lit spot. * Test your sound. * Have your products or props ready. **While you record:** * Hook viewers in the first 3 seconds. * Keep it to 1 to 3 minutes. * Speak with energy, in your own words. * Show, don't just tell. **Before you share:** * Add captions. Many people watch with the sound off. * Include your brand elements. * End with a clear call to action. * Watch it on more than one device. ## Follow up when they engage Fluid shows you when people engage with what you share. In the mobile app, **Catch Up** suggests follow-ups, for example when a contact views a page you shared, starts a video but doesn't finish it, or hasn't ordered two days after you sent them a SmartLink. Your company chooses which suggestions are on in [Catchups](/help/admin/settings/catch-ups). To see what a specific person does with your content, share it as a SmartLink: choose the contact, then send the link by text or email, or copy it. Their activity is then tracked to that contact. When a suggestion appears: 1. Check what they engaged with. 2. Respond with something relevant to it. 3. Add value, such as an answer or a related item. 4. Suggest a next step, without pressure. 5. Keep it conversational. ## Keep your content compliant Compliance keeps you and your company safe while leaving room to be creative. **Do:** * Share real, verified experiences. * Focus on relatable, everyday moments. * Keep your messages truthful and clear. * Follow your company's guidelines. **Don't:** * Make income claims or guarantees. * Make medical or health claims. * Pressure people or use hard-sell tactics. * Compare yourself to competitors. ## Build an engagement routine **Every week:** * Post at consistent times. * Share fresh content 3 to 5 times. * Reply to comments within hours. * Review what got the most engagement. **In every post:** * Ask questions that start a discussion. * Share stories that invite replies. * Try polls and other interactive content. * Celebrate your community's successes. ## Frequently asked questions A mix of photos, videos and documents, because each does a different job. Photos make a quick connection, videos build trust, and documents carry detail. Whatever you share, keep it authentic. See [Mix your content types](#mix-your-content-types). ## Related pages * [Warming up cold leads](/help/playbook/warming-up-cold-leads) * [Smart playlists](/help/playbook/transform-your-sales-with-smart-playlists) * [Catchups](/help/admin/settings/catch-ups) * [Mobile app](/help/mobile) ## 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.