> ## 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. > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. # Lists agreements ## OpenAPI ````yaml /api-reference/company-v0.yaml get /api/agreements openapi: 3.1.0 info: title: Fluid Company API version: v0 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: [] paths: /api/agreements: get: tags: - agreements summary: Lists agreements operationId: company_v0_list_agreements parameters: - name: page in: query required: false schema: type: integer - name: per_page in: query required: false schema: type: integer - name: language_iso in: query required: false schema: type: string - name: Authorization in: header required: true schema: type: string - name: sorted_by in: query required: false example: title_asc description: > Sort the records by one of the supported attributes: - title - active - required_on_checkout - created_at - updated_at The sort attribute should be followed by one of the order directives: '_asc', '_desc' schema: type: string - name: search_query in: query required: false description: Filter agreements with their title schema: type: string - name: status in: query schema: type: string enum: - active - inactive required: false description: Filter by status responses: '200': description: Success content: application/json: schema: $ref: >- #/components/schemas/ListAgreementsResponse200ApplicationJsonSchema '401': description: unauthorized content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' security: - bearer_auth: [] components: schemas: ListAgreementsResponse200ApplicationJsonSchema: type: - object - 'null' properties: agreements: type: - array - 'null' items: $ref: '#/components/schemas/CompanyAgreement' meta: anyOf: - type: - object - 'null' properties: request_id: type: - string - number - integer - 'null' timestamp: type: - string - number - integer - 'null' pagination: $ref: '#/components/schemas/CompanyRolePagination' - type: - object - 'null' properties: request_id: type: - string - number - integer - 'null' timestamp: type: - string - number - integer - 'null' UnauthorizedResponse: type: object properties: message: type: string required: - message CompanyAgreement: type: - object - 'null' properties: id: type: - integer - string - number - 'null' title: type: - string - number - integer - 'null' active: type: - boolean - 'null' description: > Controls whether this agreement appears on the global checkout flow. When true, the agreement renders for all checkouts. When false, it is suppressed from the global checkout but still renders on any enrollment pack checkout where it has been directly attached (present in enrollment_pack_agreements). show_at_checkout: type: - boolean - 'null' default_checked: type: - boolean - 'null' required_on_checkout: type: - boolean - 'null' company_country_ids: type: - array - 'null' items: $ref: '#/components/schemas/JsonValue' description: type: - string - number - integer - 'null' show_path: type: - string - number - integer - 'null' language_iso: type: - string - number - integer - 'null' required: type: - boolean - 'null' enrollment_pack_id: type: - integer - string - number - 'null' created_at: type: - string - number - integer - 'null' format: date-time updated_at: type: - string - number - integer - 'null' format: date-time company_logo: type: - string - number - integer - 'null' attachments: type: - array - 'null' items: $ref: '#/components/schemas/CompanyAgreementAttachment' CompanyRolePagination: type: - object - 'null' properties: current_page: type: - integer - string - number - 'null' total_pages: type: - integer - string - number - 'null' total_count: type: - integer - string - number - 'null' per_page: type: - integer - string - number - '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' CompanyAgreementAttachment: type: - object - 'null' properties: id: type: - integer - string - number - 'null' url: type: - string - number - integer - 'null' filename: type: - string - number - integer - 'null' content_type: type: - string - number - integer - 'null' content_size: type: - integer - string - number - 'null' kind: type: - string - number - integer - 'null' metadata: type: - object - 'null' additionalProperties: $ref: '#/components/schemas/JsonValue' securitySchemes: bearer_auth: type: http scheme: bearer description: Bearer token authentication ````