> ## 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. # Remove bot from conversation > Remove a broadcast bot from one of your company's channel conversations and post a notice that it was removed. Callable by a company admin or rep whose role includes the messaging update permission. Returns 404 when the bot is not an active broadcast bot or the conversation is not a channel in your company. ## OpenAPI ````yaml /api-reference/messaging-v1.yaml delete /api/v1/messaging/bots/{bot_id}/remove_from_conversation 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/bots/{bot_id}/remove_from_conversation: delete: tags: - messaging---bots summary: Remove bot from conversation description: >- Remove a broadcast bot from one of your company's channel conversations and post a notice that it was removed. Callable by a company admin or rep whose role includes the messaging update permission. Returns 404 when the bot is not an active broadcast bot or the conversation is not a channel in your company. operationId: messaging_v1_remove_bot_from_conversation parameters: - name: conversation_id in: query required: true description: Channel conversation ID schema: type: integer - name: bot_id in: path required: true schema: type: string responses: '200': description: >- The bot. The channel stays in its `conversations` with `removed_at` set. content: application/json: schema: $ref: '#/components/schemas/MessagingBot' example: id: 3204 title: Sales Wins description: Posts closed deals from the CRM into the sales channel type: BroadcastBot image_url: https://cdn.fluid.app/bots/3204/sales-wins.png avatar_background_color: 2E7D32 avatar_emoji: null archived_at: null recipient: id: 48190 discarded_at: null avatar_background: null first_name: Sales Wins last_name: null email: null phone: null blocked: false conversation: null conversations: - id: 90457 name: Scranton Sales Wins description: Closed deals and shout-outs from the Scranton branch avatar_url: null webhook_url: >- https://www.fluid.app/inbounds/bots/Hq4sW2mZ8kRtY7vN3pLbX9cE/48190/Tz6KfP1dQ8wVn3JxR5sYb2Lm removed_at: '2026-09-30T15:22:41Z' webhook_external_uri: null webhook_http_method: null '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/StandardUnauthorizedResponse' security: - bearer_auth: [] components: schemas: MessagingBot: description: A messaging bot. type: object properties: archived_at: type: - string - 'null' format: date-time description: When the bot was archived, or null while it is active. avatar_background_color: type: - string - 'null' description: Background color shown behind the bot's avatar. avatar_emoji: type: - string - 'null' description: Emoji shown as the bot's avatar. conversation: anyOf: - $ref: '#/components/schemas/MessagingConversation' - type: 'null' description: >- Your one-to-one conversation with the bot, or null when you have none. conversations: type: array items: $ref: '#/components/schemas/BroadcastBotConversation' description: >- Conversations the bot's recipient belongs to, such as the channels a broadcast bot posts into. description: type: - string - 'null' description: What the bot does. id: type: integer description: The bot ID. image_url: type: - string - 'null' description: URL of the bot's avatar image. recipient: anyOf: - $ref: '#/components/schemas/MessagingSlimmedRecipient' - type: 'null' description: The messaging recipient that represents the bot in conversations. title: type: string description: The bot's display name. Unique among your company's active bots. type: type: string description: >- `ResponseBot` (replies through a webhook in one-to-one conversations) or `BroadcastBot` (posts into channel conversations). webhook_external_uri: type: - string - 'null' description: >- For a response bot, the URL its webhook delivers messages to; otherwise null. webhook_http_method: type: - string - 'null' description: >- For a response bot, the HTTP method its webhook uses (`post`, `put`, or `get`); otherwise null. required: - archived_at - avatar_background_color - avatar_emoji - conversation - conversations - description - id - image_url - recipient - title - type - webhook_external_uri - webhook_http_method additionalProperties: false StandardUnauthorizedResponse: description: Common legacy unauthorized response envelope. allOf: - $ref: '#/components/schemas/StandardErrorResponse' MessagingConversation: type: object properties: announcing: type: boolean auto_add_recipients: type: boolean avatar_background_color: type: 'null' avatar_emoji: type: 'null' avatar_url: type: 'null' broadcasting: type: boolean conversation_type: type: string created_at: type: string format: date-time creator: type: 'null' description: type: 'null' draft_message: type: 'null' email_enabled?: type: boolean id: type: integer image_url: type: 'null' kind: type: string messaging_enabled?: type: boolean muted: type: boolean name: type: string pinned: type: boolean pinned_messages_count: type: integer recipients: type: array items: $ref: '#/components/schemas/MessagingConversationMember' scheduled_messages_count: type: integer sms_enabled?: type: boolean status: type: string total_recipients: type: integer type: type: string unread: type: boolean unread_messages_count: type: integer required: - announcing - auto_add_recipients - avatar_background_color - avatar_emoji - avatar_url - broadcasting - conversation_type - created_at - creator - description - draft_message - email_enabled? - id - image_url - kind - messaging_enabled? - muted - name - pinned - pinned_messages_count - recipients - scheduled_messages_count - sms_enabled? - status - total_recipients - type - unread - unread_messages_count additionalProperties: false BroadcastBotConversation: type: object properties: avatar_url: type: - string - 'null' description: type: - string - 'null' id: type: integer name: type: string removed_at: type: - string - 'null' format: date-time webhook_url: type: - string - 'null' required: - avatar_url - description - id - name - removed_at - webhook_url additionalProperties: false MessagingSlimmedRecipient: type: object properties: avatar_background: type: - string - 'null' blocked: type: - boolean - 'null' discarded_at: type: - string - 'null' format: date-time email: type: - string - 'null' first_name: type: - string - 'null' id: type: integer last_name: type: - string - 'null' phone: type: - string - 'null' required: - avatar_background - blocked - discarded_at - email - first_name - id - last_name - phone additionalProperties: false 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' MessagingConversationMember: type: object properties: avatar_background: type: - string - 'null' avatar_url: type: - string - 'null' blocked: type: - boolean - 'null' country_name: type: - string - 'null' discarded_at: type: - string - 'null' first_name: type: - string - 'null' id: type: integer image_url: type: - string - 'null' last_name: type: - string - 'null' last_online: type: - string - 'null' left_conversation_at: type: - string - 'null' pro_user: type: - boolean - 'null' receivable_id: type: - integer - 'null' receivable_type: type: string status: type: - string - 'null' required: - avatar_background - avatar_url - blocked - country_name - discarded_at - first_name - id - image_url - last_name - last_online - left_conversation_at - pro_user - receivable_id - receivable_type - status additionalProperties: false 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 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' ErrorValue: description: A validation or API error value. anyOf: - type: string - type: array items: type: string - type: object additionalProperties: $ref: '#/components/schemas/JsonValue' securitySchemes: bearer_auth: type: http scheme: bearer description: Bearer token authentication ````