> ## 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. # List company pricing tiers > Returns the company's pricing tiers ("Price Types" in the admin UI) in ascending tier_level order, active only by default. Exists to populate the pricing-tier picker on the member-types settings page, so it is gated on the same member_types.view permission as the member-types index rather than a tier-specific key. Requires admin tier. ## OpenAPI ````yaml /api-reference/admin-v2025-06.yaml get /api/v2025-06/pricing-tiers openapi: 3.1.0 info: title: Fluid Admin v2025-06 API version: v2025-06 contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app security: [] paths: /api/v2025-06/pricing-tiers: get: tags: - members summary: List company pricing tiers description: >- Returns the company's pricing tiers ("Price Types" in the admin UI) in ascending tier_level order, active only by default. Exists to populate the pricing-tier picker on the member-types settings page, so it is gated on the same member_types.view permission as the member-types index rather than a tier-specific key. Requires admin tier. operationId: admin_v2025_06_pricing_tiers_index parameters: - name: include_archived in: query required: false description: When true, includes archived tiers. Defaults to active tiers only. schema: type: boolean default: false responses: '200': description: >- The company's pricing tiers, ascending by tier_level; empty when none are provisioned. content: application/json: example: pricing_tiers: - id: 0192a4c1-7e2b-7c31-9f0a-5d8e3b6a1c42 name: Retail tier_level: 0 system: true archived_at: null member_type_count: 1 - id: 0192a4c1-7e2b-7d05-8b14-2f6c9a0e7d13 name: Preferred tier_level: 1 system: true archived_at: null member_type_count: 1 - id: 0192a4c1-7e2b-7e9a-a3c7-81d4f5b2e069 name: Wholesale tier_level: 2 system: true archived_at: null member_type_count: 2 - id: 0199a8e2-4c17-7b53-9d2e-6f0a3c8b5e14 name: Paper Club tier_level: 100 system: false archived_at: null member_type_count: 0 status: 200 meta: request_id: e1b7c3a9-2f64-4d08-9a5e-7c3d1b8f0e26 timestamp: '2026-09-10T11:21:40Z' schema: $ref: '#/components/schemas/PricingTiersResponse' '401': description: Missing or invalid credentials. content: application/json: schema: $ref: '#/components/schemas/ManagedMemberTypeUnauthorizedResponse' '403': description: The caller is not admin tier or lacks member_types.view permission. content: application/json: schema: $ref: '#/components/schemas/ManagedMemberTypeForbiddenResponse' security: - bearer_auth: [] components: schemas: PricingTiersResponse: type: object required: - pricing_tiers - status - meta additionalProperties: false properties: pricing_tiers: type: array items: $ref: '#/components/schemas/PricingTier' status: type: integer const: 200 meta: $ref: '#/components/schemas/Meta' ManagedMemberTypeUnauthorizedResponse: type: object required: - message additionalProperties: false properties: message: type: string ManagedMemberTypeForbiddenResponse: oneOf: - type: object required: - message additionalProperties: false properties: message: type: string - type: object required: - error additionalProperties: false properties: error: type: string PricingTier: type: object description: >- A company pricing tier ("Price Type" in the admin UI). Seeded system tiers (Retail, Preferred, Wholesale, ...) are always present and can be renamed but never archived; custom tiers are admin-created and DORMANT -- create is refused with 422 until the company's custom_price_types capability is enabled. Catalogs and member types both reference tiers with restrict_with_error, so archiving (never deleting) is the only removal, and forces reassignment of any member type still pointing at the tier. required: - id - name - tier_level - system - archived_at - member_type_count additionalProperties: false properties: id: type: string format: uuid name: type: string tier_level: type: integer description: >- The tier's ordinal within the company, ascending. Level 0 is the company's default (Retail) tier. Names are not unique across companies, so this is what distinguishes the seeded tiers. Custom tiers always allocate above 99. system: type: boolean description: >- True for a platform-seeded tier (tier_level < 100). System tiers can be renamed but never archived. archived_at: type: - string - 'null' format: date-time description: The archival timestamp, or null while the tier is active. member_type_count: type: integer description: >- The number of member types (including archived ones) currently pointing at this tier. Archiving with member types assigned requires reassign_to_pricing_tier_id. Meta: type: object properties: request_id: type: - string - 'null' timestamp: type: string format: date-time pagination: type: object description: >- Rotulus cursor-pagination metadata (Api::MetaPagination#to_h), present on cursor-paginated responses such as GET /api/v2025-06/prices. total_count is only present when the endpoint opts into a total count. properties: cursor: type: - string - 'null' limit: type: integer prev_cursor: type: - string - 'null' next_cursor: type: - string - 'null' total_count: type: integer securitySchemes: bearer_auth: type: http scheme: bearer ````