> ## 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. > 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. > 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); 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. # Create a member > Creates a member (the unified customer/rep record) with the given member_type_slug. A duplicate email returns 422 with error.details.existing_member carrying the colliding member's identity summary (id, email, name, member_type_slug, phone and legacy ids), so find-or-create callers can recover the existing member without a follow-up lookup. ## OpenAPI ````yaml /api-reference/members-v2025-06.yaml post /api/v2025-06/members openapi: 3.1.0 info: title: Fluid Members v2025-06 API version: v2025-06 description: > The unified **Member** identity surface. `Member` is the durable identity record in Fluid. The older `/customers` and `/reps` responses do not carry `member_type`, so a client that needs to tell a Customer from a Rep — or from a type the company defines itself — reads it here. Member path ids accept either the native UUID or the legacy bigint (`legacy_user_company_id`), so existing links keep working. Every endpoint takes a company-admin bearer token and the relevant `members` permission, except the genealogy read, which a rep may also call for their own node or any member inside their own downline. contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app - url: https://{company}.fluid.app description: Production server with company subdomain variables: company: default: myco description: Company subdomain security: - bearer_auth: [] tags: - name: members description: Unified member identity paths: /api/v2025-06/members: post: tags: - members summary: Create a member description: >- Creates a member (the unified customer/rep record) with the given member_type_slug. A duplicate email returns 422 with error.details.existing_member carrying the colliding member's identity summary (id, email, name, member_type_slug, phone and legacy ids), so find-or-create callers can recover the existing member without a follow-up lookup. operationId: admin_v2025_06_members_post requestBody: required: true content: application/json: schema: type: object required: - member properties: member: type: object required: - email - member_type_slug properties: email: type: string member_type_slug: type: string enum: - rep - customer first_name: type: - string - 'null' last_name: type: - string - 'null' phone: type: - string - 'null' dob: type: - string - 'null' format: date description: >- Date of birth, written to the member's linked user record. username: type: - string - 'null' external_id: type: - string - 'null' account_id: type: - string - 'null' notes: type: - string - 'null' metadata: type: - object - 'null' active: type: - boolean - 'null' rank_id: type: - integer - 'null' email_marketing: type: - boolean - 'null' sms_marketing: type: - boolean - 'null' language_code: type: - string - 'null' country_code: type: - string - 'null' tax_exempt: type: boolean sales_tax_id: type: string send_invitation: type: - boolean - 'null' description: >- Whether the invitation notifier fires after creation (default true). address: type: object description: >- Sets the member's default address (`country`, not `country_code`). required: - address1 - city - state - postal_code - country properties: address1: type: string address2: type: string city: type: string state: type: string postal_code: type: string country: type: string name: type: string responses: '201': description: Created; returns the member detail (admin view). content: application/json: schema: type: object properties: member: type: object description: >- The member detail (admin view). Key identity and profile fields are enumerated; the admin view also returns additional fields (addresses, payment_methods, sponsor, placement, member_type, rank, points, orders_count, total_spent_in_base, notes). properties: id: type: string description: The member's native UUID. email: type: - string - 'null' name: type: - string - 'null' username: type: - string - 'null' first_name: type: string last_name: type: string member_type_slug: type: - string - 'null' activity_status: type: string legacy_user_company_id: type: - integer - 'null' legacy_customer_id: type: - integer - 'null' phone: type: - string - 'null' external_id: type: - string - 'null' dob: type: - string - 'null' format: date description: >- Date of birth from the member's linked user record. API-only — not included in member webhook payloads. country_code: type: - string - 'null' language_code: type: - string - 'null' metadata: type: - object - 'null' tax_exempt: type: boolean sales_tax_id: type: - string - 'null' email_marketing: type: boolean sms_marketing: type: boolean created_at: type: string format: date-time updated_at: type: string format: date-time status: type: integer meta: $ref: '#/components/schemas/Meta' additionalProperties: false '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' '403': description: >- The caller is authenticated but not permitted: a rep-tier token, or an admin/service token without the required members permission. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' '422': description: >- Validation failed, or the email already belongs to a member — the duplicate case returns error.details.email = ["already exists"] and error.details.existing_member with the colliding member's identity summary (id, email, name, member_type_slug, phone and legacy ids). content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' security: - bearer_auth: [] components: schemas: Meta: type: object properties: request_id: type: - string - 'null' timestamp: type: string format: date-time UnauthorizedResponse: type: object properties: message: type: string error_message: type: string errors: $ref: '#/components/schemas/ErrorBag' meta: $ref: '#/components/schemas/Meta' StandardErrorResponse: description: >- Common legacy error response envelope. Older endpoints may return one or more of these fields depending on the controller path. type: object properties: message: type: string error: $ref: '#/components/schemas/ErrorMessage' error_message: $ref: '#/components/schemas/ErrorMessage' errors: $ref: '#/components/schemas/ErrorBag' meta: $ref: '#/components/schemas/Meta' additionalProperties: $ref: '#/components/schemas/JsonValue' ErrorBag: description: >- Validation errors keyed by field, a list of errors, a single error message, or null when no structured error details are available. anyOf: - type: string - type: array items: $ref: '#/components/schemas/ErrorValue' - type: object additionalProperties: $ref: '#/components/schemas/ErrorValue' - type: 'null' ErrorMessage: description: An API error message represented as text or structured JSON. anyOf: - type: string - $ref: '#/components/schemas/ErrorBag' - type: 'null' JsonValue: description: >- Any valid JSON value for provider, integration, theme, metadata, or other dynamic payloads whose keys are not fixed by the API contract. anyOf: - type: string - type: number - type: boolean - type: 'null' - type: array items: $ref: '#/components/schemas/JsonValue' - type: object additionalProperties: $ref: '#/components/schemas/JsonValue' ErrorValue: description: A validation or API error value. anyOf: - type: string - type: array items: type: string - type: object additionalProperties: $ref: '#/components/schemas/JsonValue' securitySchemes: bearer_auth: type: http scheme: bearer ````