> ## 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. > 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. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/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. > Navigation menu management is documented in themes/navigation-menus. These unversioned admin endpoints (/api/menus and nested menu_items) are verified against the implementation but are not yet in the synced OpenAPI specs. Use that reference for menu payloads and its flat page/per_page pagination; missing spec coverage does not make these endpoints unavailable. > 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. # Fluid Fair Share > Choose which rep earns commission on multi-rep shared links, sponsored re-orders, orphaned orders, and enrollment orders. Use the Fair Share screen to decide how commission is attributed for orders that come through shared links. To learn how Fair Share works out which rep's link a customer came from, see [FairShare: sales rep attribution](/concepts/fair-share). ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Company**, select **Fair Share**. To open the screen, your role needs at least **View only** for **Company Settings**, in the **Settings** card on the role's **Permissions** tab. See [Roles](/help/admin/settings/roles). ## What's on the screen Below the **Fluid Fair Share** banner, the screen has four setting cards and an **Attribution Placement** reference card. Each setting card has an **Attribution Target** list where you pick one option. ### Shared links (multi-rep) The **Shared Links (multi-rep)** card decides who gets commission when a customer clicks two or more reps' links before buying. * **First Touch**: Attribution goes to the first rep whose link was clicked before purchase. * **Last Touch** (recommended): Attribution goes to the final rep whose link was clicked before purchase. * **Most Activity**: Attribution goes to the rep whose shared link generated the most activity from the customer. ### Sponsored customer re-orders The **Sponsored Customer Re-Orders** card decides who earns commission when a sponsored customer buys through another rep's link. * **Sponsor** (recommended): Commission goes to the customer's sponsor, even if they click another rep's link. * **Sharing Rep**: Commission goes to the rep whose link the customer used for the re-order, regardless of sponsor. * **Share Rep & Reassign**: Commission goes to the rep whose link was used, and the customer's sponsor record is reassigned to that rep. ### Orphaned orders The **Orphaned Orders** card decides how commission is attributed when a sale occurs through a non-representative shared link. An orphaned order is one with no sponsor and no rep's link to credit. * **Leave Orphaned**: The sale remains unattributed and no rep receives commission. * **Select single rep for all orphans**: Every unattributed sale is assigned to one rep that you choose. When you select this option, a **Select Rep** field appears under it. * **Random Top Sharer** (recommended): Unattributed sales are randomly distributed among the reps with the highest recent share activity. ### Enrollment orders The **Enrollment Orders** card decides who earns commission on enrollment orders. * **New Rep**: Commission goes to the customer who placed the enrollment order and became a new rep. * **Current Sponsor**: Commission on enrollment orders goes to the customer's current sponsor. ### Attribution placement The **Attribution Placement** card has nothing to set. It explains that Fair Share detects a rep's username for attribution whether it's in the subdomain or in the path of a link. It shows these examples: * `username.example.com/home/shop` * `example.com/username/shop` The card's **Attribution Placement Documentation** link opens the [FairShare SDK overview](/sdk/overview). ## Change an attribution setting To change these settings, your role needs **Full access** for **Company Settings**. Without it, the options are disabled and **Save** doesn't appear. In the card for the situation you want to change, select an option under **Attribution Target**. If you select **Select single rep for all orphans** on the **Orphaned Orders** card, a **Select Rep** field appears. Search by name or email, then select the rep from the results. Choose a rep before you click **Save**. If you save without one, orphaned orders stay unattributed. To pick a different rep later, click **Edit** on the **Representative** card and search again. Click **Save** in the top-right corner of the screen. One save applies your selections in all four cards. A **Fair Share settings saved** message confirms the save. If you leave the screen without saving, your selections aren't applied. ## Related pages * [Settings](/help/admin/settings) * [Domains](/help/admin/settings/domains): turn on **Wildcard Subdomains** to give each rep their own subdomain * [Roles](/help/admin/settings/roles) * [FairShare: sales rep attribution](/concepts/fair-share)