> ## 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 your company's own droplets > List the droplets your company owns — the ones it created — sorted by name. Every lifecycle state is included, so draft and archived droplets appear alongside published ones. This differs from `GET /api/droplets`, which lists every droplet your company can see: published marketplace droplets, your own droplets, and droplets another company granted you access to. Call it with a Bearer token for your company. A company admin, company API token, or partner token needs the `droplets.view` permission. A droplet installation token needs the `web` scope. A public (`pub-`) token is refused with 403. Results are paginated with `page` and `per_page` (default 25, maximum 100). ## OpenAPI ````yaml /api-reference/integrations-v0.yaml get /api/droplets/company_droplets 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/droplets/company_droplets: get: tags: - droplets summary: List your company's own droplets description: >- List the droplets your company owns — the ones it created — sorted by name. Every lifecycle state is included, so draft and archived droplets appear alongside published ones. This differs from `GET /api/droplets`, which lists every droplet your company can see: published marketplace droplets, your own droplets, and droplets another company granted you access to. Call it with a Bearer token for your company. A company admin, company API token, or partner token needs the `droplets.view` permission. A droplet installation token needs the `web` scope. A public (`pub-`) token is refused with 403. Results are paginated with `page` and `per_page` (default 25, maximum 100). operationId: integrations_v0_index_company_droplets parameters: - name: page in: query required: false description: The page number to return. Starts at 1. schema: type: integer minimum: 1 - name: per_page in: query required: false description: The number of droplets per page. Defaults to 25. schema: type: integer minimum: 1 maximum: 100 - name: category in: query required: false description: Only return droplets in the droplet category with this slug. schema: type: string responses: '200': description: Your company's droplets. content: application/json: schema: $ref: >- #/components/schemas/IndexDropletsResponse200ApplicationJsonSchema example: droplets: - uuid: 4f2a9c1e-7b3d-4e8a-9f61-2c5d8b0e3a17 name: Northwind Rewards categories: - Marketing & Promotion active: true publicly_available: false embed_url: https://rewards.northwind.io/fluid/embed requested_scopes: - orders - members created_at: '2026-06-18T09:42:31Z' settings: marketplace_page: title: Northwind Rewards logo_url: https://rewards.northwind.io/assets/logo.png summary: Points and tiered rewards for every order. details_page: title: Northwind Rewards logo_url: https://rewards.northwind.io/assets/logo.png summary: >- Reward repeat customers with points they redeem at checkout. features: - name: Tiered points summary: Earn more as customers climb tiers. details: >- Set earn rates per tier and let customers see their progress in the member portal. image_url: null video_url: null service_operational_countries: - USA - CAN app_extensions: [] meta: request_id: 3b1f6c2e-8d4a-4e7b-9f05-a2c1d6e8b347 timestamp: '2026-09-30T14:05:12Z' pagination: current_page: 1 total_pages: 1 total_count: 1 per_page: 25 '401': description: The Bearer token is missing or invalid. content: application/json: schema: $ref: '#/components/schemas/StandardUnauthorizedResponse' '403': description: >- The token is not allowed to view droplets — for example, a public token, or an admin without the `droplets.view` permission. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' '422': description: A pagination parameter is out of range. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - bearer_auth: [] components: schemas: IndexDropletsResponse200ApplicationJsonSchema: type: object required: - droplets - meta properties: droplets: type: array items: $ref: '#/components/schemas/Droplet' 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' StandardUnauthorizedResponse: description: Common legacy unauthorized response envelope. allOf: - $ref: '#/components/schemas/StandardErrorResponse' StandardErrorResponse: description: >- Common legacy error response envelope. Older endpoints may return one or more of these fields depending on the controller path. type: object properties: message: type: string error: $ref: '#/components/schemas/ErrorMessage' error_message: $ref: '#/components/schemas/ErrorMessage' errors: $ref: '#/components/schemas/ErrorBag' meta: $ref: '#/components/schemas/Meta' additionalProperties: $ref: '#/components/schemas/JsonValue' ErrorResponse: type: object required: - error_message - errors - meta properties: error_message: type: string errors: $ref: '#/components/schemas/ErrorBag' meta: $ref: '#/components/schemas/Meta' Droplet: title: Droplet type: object required: - uuid - name - categories - active - publicly_available - embed_url - requested_scopes - created_at - settings - app_extensions properties: uuid: type: string name: type: string categories: type: array items: type: string active: type: boolean default: false publicly_available: type: boolean default: false embed_url: type: - string - 'null' requested_scopes: type: array items: type: string created_at: type: string format: date-time settings: $ref: '#/components/schemas/DropletSettings' app_extensions: type: array items: $ref: '#/components/schemas/JsonValue' 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 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 required: - request_id - timestamp properties: request_id: type: - string - 'null' timestamp: type: string format: date-time 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' DropletSettings: title: Droplet::Settings type: - object - 'null' properties: marketplace_page: $ref: '#/components/schemas/DropletMarketplacePage' details_page: $ref: '#/components/schemas/DropletDetailsPage' service_operational_countries: items: type: string pattern: ^[A-Z]{3}$ description: >- An array of ISO3 country codes for which the droplet is operational. A null value indicates that the service operates everywhere. An empty array indicates that the service operates nowhere. type: - array - 'null' ErrorValue: description: A validation or API error value. anyOf: - type: string - type: array items: type: string - type: object additionalProperties: $ref: '#/components/schemas/JsonValue' DropletMarketplacePage: title: Droplet::MarketplacePage type: - object - 'null' required: - title properties: title: type: string logo_url: type: - string - 'null' summary: type: - string - 'null' DropletDetailsPage: title: Droplet::DetailsPage type: - object - 'null' required: - title properties: title: type: string logo_url: type: - string - 'null' summary: type: - string - 'null' features: type: - array - 'null' items: $ref: '#/components/schemas/DropletFeature' DropletFeature: title: Droplet::Feature type: object required: - name properties: name: type: string summary: type: - string - 'null' details: type: - string - 'null' image_url: type: - string - 'null' video_url: type: - string - 'null' securitySchemes: bearer_auth: type: http scheme: bearer description: Bearer token authentication ````