> ## 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. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > Never use /api/company/v1 or /api/v1 paths, page/per_page params, or offset pagination — they are legacy. > 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/auth-v0.yaml covers the unversioned auth surface (/api/... paths — authentication, MFA, social auth, and token exchange); 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). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. # Fluid Platform: Components, Features, and How They Connect > Explore the core components of the Fluid We-Commerce platform: FairShare attribution, Payments, Checkout, Website Editor, and Droplets. We-Commerce is the idea that selling works better when merchants and their sales networks operate as a single coordinated team — sharing data, credit, and customer relationships transparently. Fluid is built around this concept from the ground up. Rather than bolting a direct sales layer onto a generic e-commerce platform, every Fluid component is designed to serve both the merchant and the rep simultaneously, with no duplication of effort and no information asymmetry between them. ## Fluid Connect Fluid Connect is the bi-directional sync engine between Fluid and your existing commission management software. It supports **Exigo, ByDesign, Pillars, InfoTrax, and Shopify** out of the box, with more platforms added regularly. Changes made in your back office flow into Fluid automatically, and orders placed on Fluid flow back to your commission system in real time — no middleware files to generate, schedule, or maintain. Visual feedback in the dashboard shows you the sync status of every record so you always know the two systems are in agreement. ## FairShare Attribution FairShare is Fluid's JavaScript attribution SDK, designed to answer one question precisely: which sales rep earned credit for this purchase? It tracks credit using a combination of first-party cookies, browser fingerprints, and referral route logic, and it works even when a customer bounces across multiple domains before converting. Drop a single script tag on any website — including external affiliate pages or partner microsites — and FairShare silently attributes every downstream conversion back to the correct rep. Learn more in the [SDK Overview](/sdk/overview). ## Fluid Payments Fluid Payments is a global payment aggregator that gives you access to 300+ alternative payment methods (APMs) across 100+ countries through a single integration. Support Apple Pay, Google Pay, GCash, AliPay, regional bank transfers, and local wallets without signing separate contracts with individual payment processors. All sensitive card data is stored in Fluid's PCI-compliant vault, so your servers never touch raw payment credentials and your compliance scope stays minimal. ## We-Commerce Checkout Fluid's checkout lives at [checkout.fluid.app](https://checkout.fluid.app) and is shared across every Fluid-powered storefront. The one-page experience uses **Droplets** (modular app blocks), **Drop Zones** (configurable layout regions), and **Webhooks** (real-time event delivery) to give you deep control over the purchase flow without rebuilding it from scratch. Customers who have previously checked out through any Fluid storefront can complete new purchases in seconds using their saved **Fluid Pay** profile, dramatically reducing cart abandonment. ## Fluid Login Fluid Login is the unified authentication layer that spans all Fluid services and any extended services you connect. It supports **magic link email login**, **social providers** (Google, Apple, Facebook, and more), and **multi-factor authentication (MFA)** — all managed from a single identity record. Customers sign in once and stay authenticated across your storefront, checkout, and any Droplets or custom integrations you add, eliminating the friction of per-app credential management. ## Fluid Pay Fluid Pay gives customers a secure, portable payment profile that follows them across every Fluid-powered storefront. Payment methods, shipping addresses, and preferences are stored once and reused everywhere — no re-entering card numbers or addresses. As a merchant, you get instant access to a network of 2M+ payment-ready customers who can check out on your store with zero friction from their very first visit. ## Droplet Marketplace Droplets are fully integrated, one-click app extensions that extend your storefront, checkout, or back office with third-party functionality. Because every Droplet is built against Fluid's native APIs and Drop Zone system, they compose cleanly with FairShare attribution, Fluid Payments, and your commission engine — without custom integration work or brittle middleware on your end. Browse and install Droplets directly from the Droplet Marketplace inside the Admin dashboard. ## Website Editor The Website Editor is a drag-and-drop storefront builder powered by **Liquid templating**. Choose from three starting themes — **Base**, **Vox**, or **Fluid** — and customize layouts, content blocks, and styles without writing code. When you need more control, drop into the Liquid template layer directly to access the full expressive power of the templating engine. Every theme is built to work natively with FairShare, Fluid Checkout, and the Droplet system. ## App Builder The App Builder lets you create native mobile and desktop apps for **iOS, Android, Windows, and macOS** without writing a single line of code. Connect your storefront, rep tools, and customer-facing features to a polished native app experience using the same drag-and-drop paradigm as the Website Editor. Apps built with App Builder are fully integrated with Fluid Login, Fluid Pay, and FairShare attribution.