> ## 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. # Landing page conversion best practices > Build landing pages that earn trust, create honest urgency and make buying easy, with tools that help visitors when they hesitate. A good landing page builds trust, gives people a reason to act, and makes buying easy. Use these practices to get more visitors to buy. ## Visual proof and social validation Customers can't handle your products before they buy, so images and social proof do the work of building trust. Combine professional product images with real customer photos and reviews. ### Product images * Show high-quality product images from several angles. * Add photos from customers using the product. * Include product demonstration videos. * Keep a professional look, but avoid photos so polished they seem fake. ### Social proof * Display real customer testimonials prominently. * Show product reviews and ratings. * Include trust badges and security certifications. * Feature endorsements or "as seen in" logos, if you have them. ## Create honest urgency A genuine reason to act now can lift conversions. Use real scarcity and clear value, never manipulative tactics, so you keep customers' trust. ### Scarcity * Show stock levels when stock is genuinely low. * Present limited-time offers honestly. * Highlight seasonal relevance. * Avoid false scarcity. It damages trust. ### Value * Focus on benefits rather than features. * Answer "How will this improve the customer's life?" * Highlight what makes your product different. * Write clear, benefit-driven headlines. ## Make buying easy The longer or more complicated the purchase, the more shoppers give up. Fluid Checkout keeps the purchase on one page, and returning customers with a saved profile can pre-fill their details. ### Checkout * Keep the **Add to Cart** or **Buy Now** button visible without scrolling. * Keep the steps to purchase to a minimum. * Show key information up front: price, shipping costs, size options and delivery times. ### Trust * Place security badges near purchase buttons. * Show your return policy clearly. * Make shipping information easy to find. * Offer ways to get help. ## Help visitors when they hesitate Engagement tools catch visitors' attention and answer their questions before they leave. ### Pop-ups * Use pop-ups for special offers, newsletter sign-ups, and visitors who are about to leave. * Keep pop-up content short and clear. * Test when and how they appear. ### Chat * Turn on your store's chat button, and write a welcoming form title and description. See [Floating Action Buttons](/help/admin/settings/floating-action-buttons). * Answer chat messages quickly. Use chat to address hesitations about buying. ### Promotional banners * Highlight current offers and time-sensitive promotions. * Use contrasting colors so they stand out. * Keep the message clear and actionable. ## Keep improving * Test and optimize page elements regularly. * Watch your conversion results. * A/B test layouts and messages. * Check every page on a phone. * Refresh your content and offers regularly. Every element should work together to reduce risk and friction for the buyer while building trust. ## Frequently asked questions **Visual trust builders** | Element | Purpose | Best practices | | - | - | - | | Hero image | First impression | Show the product in use, state the value clearly, and size it for phones | | Product gallery | Show the details | 5 to 7 shots from different angles, zoom, and a size reference | | Video | Show the value | 30- to 90-second demos, how-tos and customer testimonials | | Social proof | Build credibility | Verified reviews, trust badges and "as seen in" logos | **Urgency drivers** | Type | Example | How to use it | | - | - | - | | Limited time | "Weekend special" | Show when the offer ends | | Inventory | "Only 5 left" | Use it only when stock really is low | | Seasonal | "Holiday collection" | Match the current season | | Value | "Free shipping ends Sunday" | Focus on what the customer saves | See [Visual proof and social validation](#visual-proof-and-social-validation) and [Create honest urgency](#create-honest-urgency). ## Related pages * [Mobile shopping](/help/playbook/why-mobile-shopping-is-critical-for-conversions) * [Cart abandonment](/help/playbook/optimizing-your-cart-abandonment-strategy) * [Pages](/help/admin/pages) * [Floating Action Buttons](/help/admin/settings/floating-action-buttons) ## 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.