> ## 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 Quickstart: Account, FairShare SDK, and First API Call > Create your Fluid account, add the FairShare SDK to your website, and confirm your integration with a live API call — all in under 10 minutes. Fluid gets you from zero to a fully attributed, payment-ready storefront faster than any traditional e-commerce stack. Follow these steps to create your account, connect the FairShare attribution SDK to your website, and confirm everything is working with a live API call. The whole process takes under 10 minutes. Sign up for a Fluid account at [admin.fluid.app/sign-up](https://admin.fluid.app/sign-up). Choose your plan, enter your business details, and verify your email address. Once your account is active, you'll land in the Fluid Admin dashboard — your control centre for storefronts, reps, orders, and settings. Navigate to **Admin Settings → Developer** inside the dashboard. Generate a new API token and copy it to a secure location. You'll use this token to authenticate every request to the Fluid API. Treat it like a password — never commit it to source control or expose it in client-side code. Paste the following script tag into the `` of every page on your website. FairShare will automatically begin tracking rep referral routes, cookies, and fingerprints from the moment it loads. ```html theme={null} ``` FairShare works on any domain — including sites you don't fully control — so you can attribute sales from affiliate pages, microsites, and partner storefronts without additional configuration. Verify your token and connection by fetching your product catalogue. Run the following command in your terminal, replacing `YOUR_API_TOKEN` with the token you copied in Step 2. ```bash theme={null} curl -X GET https://api.fluid.app/api/v202604/company/products \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -H "Content-Type: application/json" ``` A successful response returns a paginated JSON array of your products. If you receive a `401 Unauthorized` error, double-check that you copied the full token and that it hasn't been revoked in the dashboard. Webhooks let Fluid push real-time events — new orders, commission updates, customer sign-ups — directly to your server instead of requiring you to poll the API. In the dashboard, go to **Admin Settings → Developer → Webhooks**, add your endpoint URL, and select the event types you want to receive. Fluid signs every webhook payload with an HMAC signature so you can verify requests are genuine. Not ready to point requests at the live API yet? Use the mock server at [docs.fluid.app/\_mock/docs/apis/swagger/](https://docs.fluid.app/_mock/docs/apis/swagger/) to explore endpoints and test request shapes without touching real data. ## What's next? Now that your account is live and FairShare is installed, explore how to secure your integration and build out your full API workflow. Learn how API tokens, OAuth flows, and webhook signatures work in Fluid. Browse the full Fluid REST API reference — products, orders, customers, commissions, and more.