> ## 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 a theme's published version history from its connected Git repo > Returns the recent commits on the theme's connected Git repository, newest first. Themes are DB-canonical: Fluid writes one commit per publish, so this log is the theme's published version history. `author_name` is the committing identity, which for anything Fluid pushed is the Fluid GitHub App. The person who published is named in `message`. Read-only — this endpoint never provisions or repairs a repository. ## OpenAPI ````yaml /api-reference/themes-v0.yaml get /api/application_themes/{id}/git_versions openapi: 3.1.0 info: title: Fluid Themes API version: v0 contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app security: [] paths: /api/application_themes/{id}/git_versions: get: tags: - application-themes summary: List a theme's published version history from its connected Git repo description: | Returns the recent commits on the theme's connected Git repository, newest first. Themes are DB-canonical: Fluid writes one commit per publish, so this log is the theme's published version history. `author_name` is the committing identity, which for anything Fluid pushed is the Fluid GitHub App. The person who published is named in `message`. Read-only — this endpoint never provisions or repairs a repository. operationId: listApplicationThemeGitVersions parameters: - name: id in: path required: true schema: type: integer description: Application theme ID - name: limit in: query required: false schema: type: integer description: Maximum versions to return. Defaults to 25, clamped to 100. responses: '200': description: Success. An empty list means the repository has no commits yet. content: application/json: schema: type: object properties: git_versions: type: array items: $ref: '#/components/schemas/ApplicationThemeGitVersion' current_sha: type: - string - 'null' description: >- The commit the repository was last synced to, or null when nothing has synced yet. syncing: type: boolean description: >- True while a push to the repository is in flight. Publishing mirrors to Git through a background job, so for a few seconds afterwards the newest commit does not exist yet. Clients should show a syncing state and poll until this clears rather than treating the list as final. sync_failing: type: boolean description: >- True when the repository's last push failed. The listed commits are still real and still restorable — the newest theme state simply is not among them yet — so clients should render the history with a warning rather than treating the theme as disconnected. required: - git_versions - current_sha - syncing - sync_failing example: git_versions: - sha: 4b7d2e9a1c3f5e7b9d0a2c4e6f8b1d3a5c7e9f0b short_sha: 4b7d2e9 message: >- Michael Scott: Publish theme Scranton Storefront (0192f4c1-8a3b-7c4d-9e2f-1a2b3c4d5e6f) author_name: mist-we-commerce[bot] committed_at: '2026-09-18T16:41:02Z' html_url: >- https://github.com/fluid-gitsync/theme-48213/commit/4b7d2e9a1c3f5e7b9d0a2c4e6f8b1d3a5c7e9f0b current: true - sha: 9f3c1e7b2a4d6f8e0c1b3a5d7e9f2c4b6a8d0e1f short_sha: 9f3c1e7 message: >- Pam Beesly: Publish theme Scranton Storefront (0192f4c1-8a3b-7c4d-9e2f-1a2b3c4d5e6f) author_name: mist-we-commerce[bot] committed_at: '2026-09-15T09:04:37Z' html_url: >- https://github.com/fluid-gitsync/theme-48213/commit/9f3c1e7b2a4d6f8e0c1b3a5d7e9f2c4b6a8d0e1f current: false current_sha: 4b7d2e9a1c3f5e7b9d0a2c4e6f8b1d3a5c7e9f0b syncing: false sync_failing: false meta: request_id: 3f9c2a7e-6b1d-4e8a-9c52-7d0e4b1a2f63 timestamp: '2026-09-18T16:40:56Z' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' '404': description: Theme not found in the current company content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: The theme has no repository yet, or it is not connected. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '502': description: The Git provider returned an error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - bearer_auth: [] components: schemas: ApplicationThemeGitVersion: type: object description: One commit in a theme's published version history. properties: sha: type: string description: Full commit SHA example: a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0 short_sha: type: string description: Abbreviated commit SHA, for display example: a1b2c3d message: type: string description: Commit message. Fluid-authored publishes name the acting user here. example: >- Ana Diaz: Publish theme Aurora (0192f4c1-8a3b-7c4d-9e2f-1a2b3c4d5e6f) author_name: type: - string - 'null' description: >- Committing identity. For Fluid-authored publishes this is the Fluid GitHub App, not the person who published. example: mist-we-commerce[bot] committed_at: type: - string - 'null' format: date-time description: When the commit was authored example: '2026-08-04T10:00:00Z' html_url: type: - string - 'null' description: Link to the commit on the Git provider example: >- https://github.com/fluid-gitsync/theme-877/commit/a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0 current: type: boolean description: >- Whether this commit is the one the repository was last synced to. False for every entry when nothing has synced yet. required: - sha - short_sha - message - author_name - committed_at - html_url - current UnauthorizedResponse: type: object properties: message: type: string required: - message ErrorResponse: type: object required: - error_message - errors - meta properties: error_message: $ref: '#/components/schemas/ErrorMessage' errors: $ref: '#/components/schemas/ErrorBag' meta: $ref: '#/components/schemas/Meta' ErrorMessage: description: An API error message represented as text or structured JSON. anyOf: - type: string - $ref: '#/components/schemas/ErrorBag' - type: 'null' 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' Meta: type: object properties: request_id: type: - string - 'null' timestamp: type: string format: date-time ErrorValue: description: A validation or API error value. anyOf: - type: string - type: array items: type: string - type: object additionalProperties: $ref: '#/components/schemas/JsonValue' 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' securitySchemes: bearer_auth: type: http scheme: bearer description: Bearer token authentication ````