> ## 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 droplet installations > List the droplets installed on your company, newest first. Uninstalled installations are left out; installations that are still being uninstalled appear with `active: false`. Call it with a company admin's Bearer token, or a company API or partner token, that has the `droplets.view` permission. Other callers get 401. Results are paginated with `page` and `per_page` (default 10, maximum 100). Pass `category` with a droplet category slug to only return installations of droplets in that category. ## OpenAPI ````yaml /api-reference/integrations-v0.yaml get /api/droplet_installations openapi: 3.1.0 info: title: Fluid Integrations API version: v0 contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app security: [] tags: - name: droplets description: >- Create, list, and manage droplets — the apps a company publishes to the Fluid marketplace or builds for its own use. x-fluid-section: Droplets - name: droplet-installations description: >- Install droplets on a company, manage those installations, and let an installed droplet redeem its one-time exchange token for its credentials. x-fluid-section: Droplets paths: /api/droplet_installations: get: tags: - droplet-installations summary: List droplet installations description: >- List the droplets installed on your company, newest first. Uninstalled installations are left out; installations that are still being uninstalled appear with `active: false`. Call it with a company admin's Bearer token, or a company API or partner token, that has the `droplets.view` permission. Other callers get 401. Results are paginated with `page` and `per_page` (default 10, maximum 100). Pass `category` with a droplet category slug to only return installations of droplets in that category. operationId: integrations_v0_index_droplet_installations parameters: - name: page in: query required: false description: Page number for pagination schema: type: integer - name: per_page in: query required: false description: 'Number of records per page (max: 100)' schema: type: integer - name: category in: query required: false description: Filter by droplet category schema: type: string responses: '200': description: Success content: application/json: schema: $ref: >- #/components/schemas/IndexDropletInstallationsResponse200ApplicationJsonSchema example: droplet_installations: - uuid: dri_9Hc3LmQ7vT2xNp5KwB8rYf4ZjD6sAg1Ue id: 48213 droplet_uuid: drp_4Tq8nXw2KfL9mRv3BpZ6cYh1JdS7aGe5u droplet_name: Middle-Out Order Analytics active: true scopes: - orders - products - uuid: dri_2Wn6RkX9bP4tLq7HzC3mVy8FsJ5dGa0Ne id: 47906 droplet_uuid: drp_8Lm3QwZ6tR1vKx9NbH4cYp7FjS2dAe5Gu droplet_name: Scranton Shipping Rates active: false scopes: - orders meta: request_id: 7e2c9b41-3f8a-4d15-b6e0-9a4c21d7f583 timestamp: '2026-09-14T15:32:08Z' pagination: current_page: 1 total_pages: 1 total_count: 2 per_page: 10 '401': description: unauthorized - non-admin users cannot access content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' security: - bearer_auth: [] components: schemas: IndexDropletInstallationsResponse200ApplicationJsonSchema: type: object required: - droplet_installations - meta properties: droplet_installations: type: array items: title: DropletInstallation type: object required: - uuid - id - droplet_uuid - droplet_name - active - scopes properties: uuid: type: string id: type: integer droplet_uuid: type: string droplet_name: type: - string - 'null' active: type: boolean default: true scopes: type: array items: type: string meta: type: object required: - request_id - timestamp - pagination properties: request_id: type: - string - 'null' timestamp: type: string format: date-time pagination: $ref: '#/components/schemas/Pagination' UnauthorizedResponse: type: object required: - message properties: message: type: string Pagination: type: object required: - current_page - total_pages - total_count - per_page properties: current_page: type: integer total_pages: type: integer total_count: type: integer per_page: type: integer securitySchemes: bearer_auth: type: http scheme: bearer description: Bearer token authentication ````