> ## 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. # Get one template, with its Liquid body > The only endpoint on this surface that serves template `content`, and it serves exactly one. Together with the templates list this reaches the same data as the v0 bulk response without any request being forced to 5.5MB. Scoped through the theme, so a template belonging to another company's theme 404s. ## OpenAPI ````yaml /api-reference/themes-v2026-04.yaml get /api/v202604/themes/{theme_id}/templates/{id} openapi: 3.1.0 info: title: Fluid Themes API description: |- **The versioned themes surface.** Themes v0 (`/api/application_themes`) remains in place and unchanged — the theme editor and the Fluid CLI consume it and depend on its shape, including the heavy fields this version omits. That immovability is why this version exists: here the DEFAULT response is the lean one. Concretely, measured against production: - `GET /api/application_themes` returns the deprecated theme-level stylesheet columns on every row. For a three-theme company that is a 185KB response of which `global_stylesheet` alone is 182KB. - `GET /api/application_themes/active` renders every template with its Liquid `content`. On a 245-template theme that is 5.5MB, 96.5% of it template bodies, when callers typically need only `id`, `themeable_type` and `default` to resolve a single template. The path segment here is `themes`, not `application_themes`. version: v2026-04 contact: email: support@fluid.app servers: - url: https://api.fluid.app security: - bearer_auth: [] tags: - name: themes description: Theme listing and the active theme. - name: preview comments description: |- Comments pinned to an element on a theme's preview, and their replies. A comment is addressed by the client-generated `client_id` rather than a row id: that is the identity every client already holds, so a retry after a dropped response is the same request rather than a new one. Creating a comment or a reply twice under one id is a success that changes nothing. There is one route per operation rather than a single write of the whole comment set. `status` is a last-writer-wins register keyed on `status_at_ms`, so a write carrying an older stamp than the stored one is accepted and discarded — it answers 200 with the status unchanged, because the request did what the contract says. paths: /api/v202604/themes/{theme_id}/templates/{id}: get: tags: - themes summary: Get one template, with its Liquid body description: |- The only endpoint on this surface that serves template `content`, and it serves exactly one. Together with the templates list this reaches the same data as the v0 bulk response without any request being forced to 5.5MB. Scoped through the theme, so a template belonging to another company's theme 404s. operationId: getThemeTemplate parameters: - name: theme_id in: path required: true description: The theme the template belongs to. schema: type: integer - name: id in: path required: true description: The template's id. schema: type: integer responses: '200': description: Success content: application/json: schema: type: object properties: template: $ref: '#/components/schemas/ThemeTemplate' required: - template example: template: id: 902114 name: Home themeable_type: home_page status: active default: true global: false source: theme application_theme_id: 48213 company_id: 1405 app_extension_id: null extension_uri: null droplet_name: null country_ids: [] hide_navbar: false use_active_application_theme: false stylesheet: null stylesheet_tag_injected: true stylesheet_column_hidden: true created_at: '2026-03-02T18:11:26Z' updated_at: '2026-09-14T15:02:11Z' content: |- {% section 'hero-banner' %} {% section 'featured-products' %} {% section 'testimonials' %} variables: hero_heading: Limitless Paper in a Paperless World translations: en: hero_cta: Shop copy paper '401': description: Unauthorized '404': description: No such template on this theme security: - bearer_auth: [] components: schemas: ThemeTemplate: type: object description: A template including its Liquid `content`. properties: id: type: integer name: type: - string - 'null' content: type: - string - 'null' themeable_type: type: - string - 'null' status: type: - string - 'null' default: type: - boolean - 'null' variables: type: - object - 'null' additionalProperties: true description: Template-level Liquid variables. translations: type: - object - 'null' additionalProperties: true application_theme_id: type: - integer - 'null' company_id: type: - integer - 'null' app_extension_id: type: - integer - 'null' extension_uri: type: - string - 'null' droplet_name: type: - string - 'null' source: type: - string - 'null' global: type: - boolean - 'null' country_ids: type: - array - 'null' items: type: integer hide_navbar: type: - boolean - 'null' use_active_application_theme: type: - boolean - 'null' stylesheet: type: - string - 'null' stylesheet_tag_injected: type: - boolean - 'null' stylesheet_column_hidden: type: - boolean - 'null' created_at: type: - string - 'null' format: date-time updated_at: type: - string - 'null' format: date-time required: - id securitySchemes: bearer_auth: type: http scheme: bearer ````