> ## 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 recipients in a conversation > List recipients in a conversation you belong to. Returns active recipients by default; when recipient_ids is provided, includes discarded recipients so clients can resolve message authors. Supports optional search filtering by name. Callable by a company admin or rep whose role includes the messaging view permission; a conversation you are not in returns 404. Results are paginated by page number with `page` and `per_page` (default 20). The response is a two-element array: the pagination details, then the recipients in `items`. ## OpenAPI ````yaml /api-reference/messaging-v1.yaml get /api/v1/messaging/conversations/{conversation_id}/recipients openapi: 3.1.0 info: title: Fluid Messaging v1 API version: v1 contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app security: [] tags: - name: messaging---conversations description: >- Create, list, update, and manage messaging conversations (direct, group, channel, SMS, email, and bot) as the signed-in company admin or rep. x-fluid-section: Messaging paths: /api/v1/messaging/conversations/{conversation_id}/recipients: get: tags: - messaging---recipients summary: List recipients in a conversation description: >- List recipients in a conversation you belong to. Returns active recipients by default; when recipient_ids is provided, includes discarded recipients so clients can resolve message authors. Supports optional search filtering by name. Callable by a company admin or rep whose role includes the messaging view permission; a conversation you are not in returns 404. Results are paginated by page number with `page` and `per_page` (default 20). The response is a two-element array: the pagination details, then the recipients in `items`. operationId: messaging_v1_list_conversation_recipients parameters: - name: recipient_ids[] in: query schema: type: array items: type: integer required: false description: Recipient IDs to filter by (array query param) - name: search in: query schema: type: string required: false description: Search query to filter recipients by name - name: page in: query schema: type: integer required: false description: The page number to return, starting at 1. - name: per_page in: query schema: type: integer required: false description: The number of recipients per page. Defaults to 20. - name: conversation_id in: path required: true schema: type: string responses: '200': description: A page of recipients. content: application/json: schema: $ref: '#/components/schemas/MessagingRecipientPage' example: - pagination: current: 1 previous: null next: null per_page: 20 pages: 1 count: 3 - items: - id: 48117 receivable_id: 7734 receivable_type: UserCompany discarded_at: null avatar_background: F4B400 first_name: Dwight last_name: Schrute avatar_url: >- https://cdn.fluid.app/tr:h-64,w-64/users/7734/dwight-schrute.jpg image_url: https://cdn.fluid.app/users/7734/dwight-schrute.jpg status: online last_online: '2026-09-29T21:14:03Z' country_name: United States pro_user: true left_conversation_at: null blocked: false conversation_messaging_enabled?: true - id: 48121 receivable_id: 7741 receivable_type: UserCompany discarded_at: null avatar_background: 4A90D9 first_name: Jim last_name: Halpert avatar_url: >- https://cdn.fluid.app/tr:h-64,w-64/users/7741/jim-halpert.jpg image_url: https://cdn.fluid.app/users/7741/jim-halpert.jpg status: away last_online: '2026-09-30T13:02:47Z' country_name: United States pro_user: false left_conversation_at: null blocked: false conversation_messaging_enabled?: true - id: 48254 receivable_id: 19302 receivable_type: Contact discarded_at: null avatar_background: 7CB342 first_name: Holly last_name: Flax avatar_url: null image_url: null email: holly.flax@gmail.com phone: '+15705550148' country_name: United States pro_user: false left_conversation_at: null blocked: false conversation_messaging_enabled?: true '401': description: unauthorized content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' security: - bearer_auth: [] components: schemas: MessagingRecipientPage: description: >- A page of recipients, returned as a two-element array: an object holding `pagination`, then an object holding the recipients in `items`. type: array items: anyOf: - type: object properties: pagination: $ref: '#/components/schemas/MessagingConversationPagination' required: - pagination - type: object properties: items: type: array items: $ref: '#/components/schemas/MessagingConversationParticipant' required: - items UnauthorizedResponse: type: object properties: message: type: string required: - message MessagingConversationPagination: description: Page-number pagination details for a page of results. type: object properties: current: type: integer description: The page returned. previous: type: - integer - 'null' description: The previous page number, or null on the first page. next: type: - integer - 'null' description: The next page number, or null on the last page. per_page: type: integer description: The page size used. pages: type: integer description: The total number of pages. count: type: integer description: The total number of matching records. MessagingConversationParticipant: description: >- A participant in a conversation, as listed in the conversation's `recipients`. Company members carry `status` and `last_online`; contacts carry `email` and `phone` instead. type: object properties: id: type: integer description: >- The recipient ID. Pass it as `uid` to add this recipient to another conversation. receivable_id: type: - integer - 'null' receivable_type: type: - string - 'null' description: What the participant is, such as a company member or a contact. first_name: type: - string - 'null' last_name: type: - string - 'null' email: type: - string - 'null' phone: type: - string - 'null' status: type: - string - 'null' last_online: type: - string - 'null' avatar_background: type: - string - 'null' avatar_url: type: - string - 'null' image_url: type: - string - 'null' country_name: type: - string - 'null' pro_user: type: - boolean - 'null' blocked: type: - boolean - 'null' description: Whether the acting recipient has blocked this participant. left_conversation_at: type: - string - 'null' conversation_messaging_enabled?: type: - boolean - 'null' discarded_at: type: - string - 'null' required: - id additionalProperties: false securitySchemes: bearer_auth: type: http scheme: bearer description: Bearer token authentication ````