> ## 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. # Warming up cold leads > Use what you know about each contact to turn cold leads into warm relationships with personal, useful follow-ups. A cold lead is someone who showed interest once and then went quiet. This guide shows how to use your contacts in Fluid to reconnect with them through personal, useful follow-ups. ## Start with your cold contacts Each contact has a status, such as **New** or **Cold**. In the mobile app, the status shows on the contact. In the admin, it's in the **Status** column of the [Contacts](/help/admin/contacts) list. Start with the contacts marked **Cold**. ## Know your contact before you reach out In the mobile app, a contact's page has four tabs. Check them before you write: * **Activity**: what the contact has done, such as pages they viewed, videos they watched and items they added to their cart. * **Tasks**: follow-ups you've planned for this contact. * **Notes**: what you talked about, their interests and their preferences. * **Profile**: their contact details. After each conversation, add a note with the key points and the products they asked about, and create a task for your next follow-up. ## Group contacts to plan your follow-ups If your app has contact groups, use them to plan your outreach. The **Groups** tab is on the **Contacts** screen. Useful ways to group contacts: | Location | Interest | Product focus | Priority | | - | - | - | - | | Region or market | How engaged they are | Product categories | High-value leads | | Local area | Website activity | What they need | Recent conversations | | Time zone | Content they viewed | Price range | Who replied before | ## Rewrite your follow-up messages Skip the generic "just checking in". Write messages that show you remember the person and what they care about. For example: > "Sarah, I noticed you were interested in our wellness collection. Here's a quick video showing how other busy parents use these products to keep their energy up..." | Instead of | Try this | Why it works | | - | - | - | | "Just checking in!" | "I thought of you when I saw this new solution for \[a challenge they mentioned]" | Shows you remember and care about their needs | | "Don't miss this amazing opportunity!" | "Based on your interest in \[something they did before], I wanted to share..." | Builds on your last conversation | | "Limited time offer!" | "Since we talked about \[topic], I wanted to make sure you knew about..." | Gives context and shows you were listening | | "Check out our latest product!" | "You mentioned struggling with \[problem]. Here's how our new \[product] helps..." | Connects your product to a need they stated | | "Don't miss out!" | "Following up on your question about \[topic] with some helpful information..." | Gives them something useful | ## Share content that re-engages Make every share feel like part of a conversation, not a presentation. **Open with something that stops the scroll:** * Before-and-after results * Quick wins * Real customer stories * Behind-the-scenes moments **Then build trust with content that helps:** * Solves a specific problem * Answers a common question * Shows your expertise * Helps them decide ## Watch for signs that a lead is warming up Track how people respond: * How often they view what you share * How quickly they reply to your messages * Whether they click your links * Whether they fill in your forms And watch for signals that they're ready for a next step: * They visit your site more often. * They spend more time with your content. * They add items to their cart. * They reply faster. ## Be patient and consistent Warming up a cold lead takes time. Focus on: 1. **Consistent value.** Build trust with helpful, relevant content. 2. **Personal communication.** Make every message about them. 3. **Patience.** Let the relationship develop at its own pace. 4. **What the data tells you.** Let their engagement guide your next step. The best follow-ups feel like a helpful check-in from a trusted advisor, not a sales pitch from a stranger. ## Frequently asked questions Replace "just checking in" with a message that mentions something specific: a challenge they told you about, a question they asked, or content they viewed. Each follow-up should give them something useful and move the relationship forward. See [Rewrite your follow-up messages](#rewrite-your-follow-up-messages) for examples. **Capture.** Ask for contact details where interested visitors already are: * **Pop-ups:** time them well and offer clear value. Show them when a visitor is about to leave or a few seconds after they arrive, and don't show more than one or two per visit. * **Forms:** keep them to four or five fields, and send an automatic reply. * **Landing pages:** give each one a single purpose, a strong call to action and fast loading on phones. Give people a reason to sign up, such as a free guide, a plan or a product comparison that fits what you sell. Test different offers to see which one works best. **Nurture.** Follow up in stages: | Stage | Timing | What to send | | - | - | - | | Welcome | Right away | A welcome video, a quick-start guide or a product overview | | Educate | Days 2 to 7 | How-to content, success stories and answers to common questions | | Engage | Week 2 | A personal check-in to learn what they need | | Convert | Weeks 3 to 4 | A special offer, a bundle or an invitation | Adjust the timing to how each person responds. Always make it easy to opt out, and respect people's privacy choices. To manage the contacts you capture, see [Contacts](/help/admin/contacts). ## Related pages * [Authentic conversations](/help/playbook/beyond-the-sales-pitch-creating-authentic-digital-conversations-that-convert) * [Contacts](/help/admin/contacts) * [Forms](/help/admin/forms) * [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.