> ## 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, run `fluid signup` from the Fluid CLI, or 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. Before authenticated calls are possible, the merchant must sign the agent in to the Fluid CLI with the emailed code and --shop set to the company's fluid_shop (which also confirms the signup), or open the emailed confirmation link and give the agent an API token. > After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch. > To host a small project on Fluid (a landing page, event page, calculator or dashboard), follow /sites/quickstart: npm create @fluid-app/fluid-site my-site (or npx @fluid-app/create-fluid-site my-site), fluid login, then fluid deploy prints the public URL. Launch a Site unless the project needs a custom domain, server rendering or heavy server code, which make it an App (a Mist app); /sites/site-or-app has the rule, and POST /api/company/v2026-10/project-launch-recommendations applies it. With only the Fluid MCP server (its Site write tools are limited to Fluid root admins today; see /sites/deploy-from-claude), use site_create, then site_deploy (from a chat with no shell, in one call with the files inline: site_template_get for a starter, then site_deploy with each path's content; or a built folder in two calls: send the manifest, PUT the listed uploads, call again with the bundle_id to get the url), then, only after the person confirms they want it public, site_visibility_set. site_logs, site_traffic, site_env_list/set/unset, site_seo_get/set and the site_branch tools cover logs, traffic, env vars, SEO and preview branches; a member builds their own Sites with the my_site_* tools. The MCP server can't publish server functions or convert a Site to an App, so use the fluid sites CLI for those. A Site can serve light server code: each functions/.ts, declared in config/functions.json with access public, signed_in or key (and an optional UTC cron schedule), answers at /api/ on the Site's own host; publish it with fluid deploy (the MCP site_deploy tool does not carry functions). See /sites/functions and /sites/rest-api. > 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. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only on an operation whose spec documents those params — mostly the unversioned company-v0 admin surface, plus some lists on other surfaces, versioned ones included; page every other list with cursors. > Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile. > 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 except two operations that take no credential, POST /api/company (create a company) and GET /api/agreements/{id} — 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. > The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations. > Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check. > Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times. # Read original preview context and a page of replies > Requires application_themes.view. Returns the canonical preview comment fields, including pin, anchor, before screenshot, and reply proof. Replies are ordered newest first by creation and row id. The next cursor loads older replies, so new replies remain on the first page. Work identity is null without multiplayer_tasks.view. A foreign, discarded, or reply id has the same not-found response as an unknown root id. ## OpenAPI ````yaml /api-reference/multiplayer-v2026-04.yaml get /api/v202604/multiplayer/preview-threads/{id} openapi: 3.1.0 info: title: Fluid Cowork API v2026-04 version: v2026-04 description: | Cowork is the company's shared board of work: tickets that people file, plan, assign and finish, that Mist can work on, and that a company can send to an agency to do for it. The Mist task board and Cowork in the Fluid admin are built on this API, so everything they do is available through it. **Authentication.** Every endpoint needs a Bearer token for a person: a company admin's session, or the token of their company membership. A company API token is refused with `403`, because each write is recorded against the person who made it. The permissions each endpoint needs, such as `multiplayer_tasks.create` or `multiplayer_discussions.view`, are listed on the endpoint. **Feature flags.** Discussions, preview threads and everything to do with agencies also need the company's `COWORK` flag. A company without it gets `404` from those endpoints. **Versions.** A task carries a `lock_version`. A write whose body takes `expected_version`, such as changing a task's content, priority, due date, status or assignee, compares it with the task's `lock_version`, and answers `409` with the current task when the task has changed since, so retry against that one. Each endpoint's body says whether it takes one. Moving a card on the board does not: `PUT /tasks/{id}/position` is ordered by the client's `board_position_at_ms` stamp, an older placement is discarded and answered with the current task, and placing work never changes its `lock_version`. **Agencies.** A company sends a task to an agency with an agency request. The agency's members then work it through the Agency work and Agency time endpoints, which need a person who belongs to that agency. contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app security: [] tags: - name: Cowork tasks description: >- The company's work, one task per ticket. Create, read, change and delete tasks, and read the board that draws them. x-fluid-section: Cowork - name: Task channels and attachments description: >- A task's comment channel, its images and files, and the discussions it is linked to. x-fluid-section: Cowork - name: Task assessments description: >- Mist's check of a task before work starts, the answers to its questions, and what to do when it finds a duplicate. x-fluid-section: Cowork - name: Mist runs description: >- Starting Mist on a task, Mist claiming and finishing the work, and asking Mist to review finished work. x-fluid-section: Cowork - name: Agency requests description: >- Sending a task to an agency, and the company's answers to the agency's quotes and finished work. x-fluid-section: Cowork - name: Discussions description: The company's chats with Mist, their messages, and the work they lead to. x-fluid-section: Cowork - name: Preview threads description: The theme preview comments that stand in for work on the board. x-fluid-section: Cowork - name: Agency work description: >- For an agency's members, the tickets customers sent the agency, and picking them up, quoting, declining and finishing them. x-fluid-section: Cowork - name: Agency time description: >- For an agency's members, the time they log on tickets and the timer that records it. x-fluid-section: Cowork paths: /api/v202604/multiplayer/preview-threads/{id}: get: tags: - Preview threads summary: Read original preview context and a page of replies description: >- Requires application_themes.view. Returns the canonical preview comment fields, including pin, anchor, before screenshot, and reply proof. Replies are ordered newest first by creation and row id. The next cursor loads older replies, so new replies remain on the first page. Work identity is null without multiplayer_tasks.view. A foreign, discarded, or reply id has the same not-found response as an unknown root id. operationId: getMultiplayerPreviewThread parameters: - name: id in: path required: true description: The root preview thread's database id. schema: type: integer - name: page[cursor] in: query description: Opaque cursor for the next, older page of replies. schema: type: string maxLength: 4096 - name: page[limit] in: query description: Maximum replies to return, defaulting to 25. schema: type: integer minimum: 1 maximum: 100 responses: '200': description: The original preview thread and a bounded page of replies. content: application/json: example: theme: id: 520942414 name: Acme Active Theme can_reply: true preview_comment: client_id: comment-handed-0002 assigned_at_ms: null assignee: null assigner: null author_name: Admin Acme block: null board_position: null board_position_at_ms: null body: The hero image is stretched on mobile created_at_ms: 1794505831901 id: 766115480 lock_version: 0 mentioned_project: null mentions: [] 'n': 2 page_url: /home pin: x: 50 'y': 10 ox: null oy: null priority: null priority_at_ms: null proof_baseline: url: null width: 1280 height: 720 captured_at_ms: 1755781000000 published: null replies: - client_id: reply-agent-0001 author_name: Mist body: >- In sections/hero/index.liquid I set the image to object-fit: cover. created_at_ms: 1794333087967 mentions: [] posted_by: id: '433400890' name: Admin Acme kind: user proof: route: /home files: - sections/hero.liquid checks: - label: Image size detail: Within bounds status: pass record_changes: [] data_snapshots: [] before: url: null run_id: null shot: url: null width: 2560 height: 1536 resolution: null run_checked_in_at_ms: null run_id: fixture-run section: null status: handed status_at_ms: 1755781000000 target: tag: img selector: html > body > section.hero > img text: '' html: null template_id: 132840687 theme_changed_at: null work_item: null status: 200 meta: request_uuid: null timestamp: '2026-11-12T17:51:28Z' pagination: cursor: >- eyJmIjp7InRoZW1lX3ByZXZpZXdfY29tbWVudHMuY3JlYXRlZF9hdCI6IjIwMjYtMTEtMTFUMTc6NTE6MjcuOTY4MTI1WiIsInRoZW1lX3ByZXZpZXdfY29tbWVudHMuaWQiOjQwOTQ3NzE0MH0sImQiOiJuZXh0IiwiYyI6MTc5NDUwNTg4OCwiY3MiOiJiMGE4M2I4ZjU2MzlhNmZhNGQ3YzFjZTdhYjk2YzU0NCIsIm9zIjoiMzQ1NDZkMWNlMDVkNzZjMzU3NzliMTQ4ZGMxMzRjOGQiLCJxcyI6IjYwMWQyNjg4MzViMDBjYTRhNmQ2YjYxZDI0ZmJjZjNjIn0= limit: 1 prev_cursor: >- eyJmIjp7InRoZW1lX3ByZXZpZXdfY29tbWVudHMuY3JlYXRlZF9hdCI6IjIwMjYtMTEtMTBUMTc6NTE6MjcuOTY2ODcxWiIsInRoZW1lX3ByZXZpZXdfY29tbWVudHMuaWQiOjU1NjI4NTA0OX0sImQiOiJwcmV2IiwiYyI6MTc5NDUwNTg4OCwiY3MiOiIzYWJmNjdlMzcxOWZiMmJiMTNjZGIwYjVmZTU0MTlkNiIsIm9zIjoiMzQ1NDZkMWNlMDVkNzZjMzU3NzliMTQ4ZGMxMzRjOGQiLCJxcyI6IjYwMWQyNjg4MzViMDBjYTRhNmQ2YjYxZDI0ZmJjZjNjIn0= next_cursor: null schema: type: object required: - theme - can_reply - preview_comment - status - meta properties: theme: $ref: '#/components/schemas/PreviewThreadTheme' can_reply: type: boolean description: >- Whether this reader also has application_themes.update for the existing reply route. preview_comment: $ref: '#/components/schemas/PreviewThreadDetail' status: const: 200 meta: allOf: - $ref: '#/components/schemas/Meta' - type: object required: - pagination properties: pagination: $ref: '#/components/schemas/Pagination' '401': description: Authentication is required. '403': description: >- A user session, company admin status, and application_themes.view are required. '404': description: The COWORK feature flag is off or the root thread is unavailable. content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: The reply page limit or cursor is invalid. content: application/json: schema: $ref: '#/components/schemas/Error' security: - bearer_auth: [] components: schemas: PreviewThreadTheme: type: object description: Theme that owns the original preview pin. required: - id - name properties: id: type: integer name: type: string PreviewThreadDetail: type: object description: Original preview-comment fields, with replies limited to this page. required: - id - client_id - 'n' - body - status - status_at_ms - lock_version - run_id - page_url - author_name - created_at_ms - theme_changed_at - template_id - pin - target - section - block - mentions - mentioned_project - proof_baseline - assignee - assigner - assigned_at_ms - priority - priority_at_ms - replies - work_item properties: id: type: integer client_id: type: string body: type: string 'n': type: integer status: type: string enum: - open - kept - needs_info - in_progress - handed - review - skipped resolution: type: - string - 'null' enum: - approved - closed - null description: >- How a Done (skipped) comment was decided, or null while it is not Done or was decided without a verdict. status_at_ms: type: - integer - 'null' lock_version: type: integer minimum: 0 run_id: type: - string - 'null' page_url: type: string author_name: type: - string - 'null' created_at_ms: type: integer theme_changed_at: type: - string - 'null' format: date-time description: >- When the theme was last published after this comment was created, or null when it has not been. A time here means the comment was pinned against a page that has since changed, so it may be out of date. The latest of the comment's own template, any structural template of the theme, the theme's own variables and stylesheets, and a release being put in service (a rollback included). Drafts do not count. Computed on each read and never stored. Carried by the comment only; its replies do not have it. Matches the theme's own preview comment list. template_id: type: - integer - 'null' pin: $ref: '#/components/schemas/PreviewThreadPin' target: oneOf: - $ref: '#/components/schemas/PreviewThreadTarget' - type: 'null' section: oneOf: - $ref: '#/components/schemas/PreviewThreadThemeRef' - type: 'null' block: oneOf: - $ref: '#/components/schemas/PreviewThreadThemeRef' - type: 'null' mentions: type: array items: $ref: '#/components/schemas/PreviewThreadMention' mentioned_project: oneOf: - $ref: '#/components/schemas/PreviewThreadMentionedProject' - type: 'null' proof_baseline: description: >- Before screenshot URL and dimensions, or null if no capture was recorded. oneOf: - $ref: '#/components/schemas/PreviewThreadBaseline' - type: 'null' assignee: oneOf: - $ref: '#/components/schemas/PreviewThreadPerson' - type: 'null' assigner: oneOf: - $ref: '#/components/schemas/PreviewThreadPerson' - type: 'null' assigned_at_ms: type: - integer - 'null' published: description: >- That the change Mist answered with went out in a publish, or null while none has. oneOf: - type: object required: - run_id - at_ms - publisher properties: run_id: type: string at_ms: type: integer publisher: oneOf: - $ref: '#/components/schemas/PreviewThreadPerson' - type: 'null' - type: 'null' priority: type: - string - 'null' enum: - urgent - high - medium - low - null priority_at_ms: type: - integer - 'null' work_item: description: >- Routing hint when the reader also holds multiplayer_tasks.view; otherwise null. oneOf: - $ref: '#/components/schemas/PreviewThreadWorkItem' - type: 'null' replies: type: array description: This reply page, newest first by creation time and row id. items: $ref: '#/components/schemas/PreviewThreadReply' Meta: type: object required: - request_uuid - timestamp properties: request_uuid: type: - string - 'null' timestamp: type: string format: date-time Pagination: type: object required: - cursor - limit - prev_cursor - next_cursor properties: cursor: type: - string - 'null' limit: type: integer prev_cursor: type: - string - 'null' next_cursor: type: - string - 'null' Error: type: object required: - error - status - meta properties: error: type: object required: - message - details properties: message: type: string details: type: object status: type: integer meta: $ref: '#/components/schemas/Meta' PreviewThreadPin: type: object description: Pin position on the preview, with optional offsets within its element. required: - x - 'y' - ox - oy properties: x: type: number 'y': type: number ox: type: - number - 'null' oy: type: - number - 'null' PreviewThreadTarget: type: object description: Element captured when the original pin was placed. required: - tag - selector - text - html properties: tag: type: - string - 'null' selector: type: - string - 'null' text: type: - string - 'null' html: type: - string - 'null' PreviewThreadThemeRef: type: object description: Section or block identity from the original theme render. required: - id - type properties: id: type: - string - 'null' type: type: - string - 'null' PreviewThreadMention: type: object description: A person or project named in the original comment or reply. required: - id - name properties: id: type: string name: type: string kind: type: string role: type: string additionalProperties: false PreviewThreadMentionedProject: type: object description: Project identified by the original comment's first project mention. required: - kind - ref properties: kind: type: string ref: type: string PreviewThreadBaseline: type: object description: >- Before screenshot; a null URL still records that a capture was attempted. required: - url - width - height - captured_at_ms properties: url: type: - string - 'null' width: type: - integer - 'null' height: type: - integer - 'null' captured_at_ms: type: integer PreviewThreadPerson: type: object description: >- A person assigned to the discussion or its linked work, including Mist as an agent. required: - id - name - kind properties: id: type: string name: type: - string - 'null' kind: type: string enum: - user - agent PreviewThreadWorkItem: type: object description: >- Linked work routing hint; the task endpoint remains authoritative for its state. required: - id - status - priority - run_id - lock_version - assignee properties: id: type: string format: uuid status: type: string enum: - open - kept - needs_info - in_progress - handed - review - skipped priority: type: - string - 'null' enum: - urgent - high - medium - low - null run_id: type: - string - 'null' lock_version: type: integer minimum: 0 assignee: oneOf: - $ref: '#/components/schemas/PreviewThreadPerson' - type: 'null' PreviewThreadReply: type: object description: Original reply with screenshot and proof when recorded. required: - client_id - run_id - body - author_name - posted_by - created_at_ms - mentions - shot - proof properties: client_id: type: string run_id: type: - string - 'null' body: type: string author_name: type: - string - 'null' posted_by: description: >- The person who posted an agent reply, or null on a person's reply and on an agent reply stored before posters were recorded. oneOf: - $ref: '#/components/schemas/PreviewThreadPerson' - type: 'null' created_at_ms: type: integer mentions: type: array items: $ref: '#/components/schemas/PreviewThreadMention' shot: oneOf: - $ref: '#/components/schemas/PreviewThreadShot' - type: 'null' proof: oneOf: - $ref: '#/components/schemas/PreviewThreadProof' - type: 'null' PreviewThreadShot: type: object description: Reply screenshot; a null URL means the capture is no longer retrievable. required: - url - width - height properties: url: type: - string - 'null' width: type: - integer - 'null' height: type: - integer - 'null' PreviewThreadProof: type: object description: Route, prior image, changed paths, and checks recorded with a reply. required: - route - before - files - checks properties: route: type: - string - 'null' before: oneOf: - type: object required: - url properties: url: type: - string - 'null' - type: 'null' files: type: array items: type: string checks: type: array items: $ref: '#/components/schemas/PreviewThreadProofCheck' record_changes: type: array description: >- The company records the run changed through the API; empty when it changed none. items: $ref: '#/components/schemas/ReplyRecordChange' data_snapshots: type: array description: >- The reads Mist named before its work, read again after; empty when it named none. items: $ref: '#/components/schemas/ReplyDataSnapshot' PreviewThreadProofCheck: type: object description: One mechanical check recorded alongside a reply's proof. required: - label - status properties: label: type: string status: type: string enum: - pass - warn - fail detail: type: string ReplyRecordChange: type: object required: - label properties: label: type: string method: type: string path: type: string outcome: type: string fields: type: array items: $ref: '#/components/schemas/RecordChangeField' before_missing: type: string after_missing: type: string truncated: type: boolean values_withheld: type: boolean readOnly: true description: True when this reader is not a person signed in to the company. ReplyDataSnapshot: type: object required: - label properties: label: type: string path: type: string rows: type: array items: $ref: '#/components/schemas/RecordChangeField' series: type: object properties: name: type: string before: type: array items: $ref: '#/components/schemas/DataSnapshotPoint' after: type: array items: $ref: '#/components/schemas/DataSnapshotPoint' before_at: type: string after_at: type: string before_missing: type: string after_missing: type: string truncated: type: boolean values_withheld: type: boolean readOnly: true description: True when this reader is not a person signed in to the company. RecordChangeField: type: object required: - path properties: path: type: string before: type: string after: type: string DataSnapshotPoint: type: object required: - x - 'y' properties: x: type: string maxLength: 60 'y': type: number securitySchemes: bearer_auth: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.