> ## 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. > 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. > 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 where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination. > 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 — 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. # List form elements > Lists the elements of one of your company's forms, lowest position first. The list includes elements that later edits deactivated, which keep their answers; the response doesn't mark which elements are active, so use `form_components` on the form for the current layout. Needs a company admin token. This list is paginated by page number. Send `page` (default 1) and `per_page` (default 20); `pagination` in the response reports the current page, total pages, and total count. Element types a form can contain, as stored in each component's `element_type`: - `short_text_entry`: a single line of text. - `long_text_entry`: a paragraph of text. - `number_entry`: a number. The builder's minimum and maximum digit settings (`min`, `max`) are saved with the element but are not enforced when the form is answered at checkout. - `multiple_choice_entry`: one choice from `multiple_choice_options`. - `yes_no_entry`: a yes or no answer from `yes_no_options`. - `checkbox`: a single checkbox. - `file_upload`: a file the respondent uploads. The answer is the file's URL. - `input`: a prebuilt identity field. Its `puck_type` names which one: `email`, `legal_name`, `full_name`, `phone_number`, `date_of_birth`, or `ssn`. - `header`, `information`, `section_label`, `helper_text`, `error_text`, `page_break`, and `button`: layout and text. They collect nothing. - `file_download`: a file the respondent can download. It collects nothing. Checkout also renders the older `text`, `date`, `number`, `email`, `legal_name`, `ssn`, and `date_of_birth` types. It skips any type it doesn't recognize. ## OpenAPI ````yaml /api-reference/forms-v0.yaml get /api/forms/{form_id}/form_elements openapi: 3.1.0 info: description: >- Manage your company's forms: build them, choose where they appear, share or embed them, and read, export, and follow up on their responses. A form is either a **post-purchase** form, which enrollment checkout shows after payment to buyers in the form's countries, or a **general** form, which you share by link, embed on a website, or send by email. Its fields are **form elements**. Each submission is a **respondent** that holds one **response** per answered element. Every operation takes a Bearer token (`Authorization: Bearer `) for your company. Reading operations need the forms view permission, and writing operations need the forms update permission, except **Respond to a form**, which any member of the company can call. Root admins and droplet tokens skip these permission checks. **Respond to a form** also accepts unauthenticated calls, but those are deprecated: to collect answers from the public, generate a public token and use the Fluid Public SDK API's token-addressed forms operations, or the hosted share and embed URLs. Answers to elements marked sensitive are masked as `********` unless the caller holds the forms view-sensitive permission, is a root admin, or uses a droplet token. title: Fluid Forms API version: v0 contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app - url: https://{company}.fluid.app description: Production server with company subdomain variables: company: default: myco description: Company subdomain security: [] tags: - name: forms description: >- Build forms, choose where they appear, share or embed them with a public token, and read, export, and follow up on their responses. - name: form-elements description: The fields and layout blocks that make up a form. paths: /api/forms/{form_id}/form_elements: get: tags: - form-elements summary: List form elements description: >- Lists the elements of one of your company's forms, lowest position first. The list includes elements that later edits deactivated, which keep their answers; the response doesn't mark which elements are active, so use `form_components` on the form for the current layout. Needs a company admin token. This list is paginated by page number. Send `page` (default 1) and `per_page` (default 20); `pagination` in the response reports the current page, total pages, and total count. Element types a form can contain, as stored in each component's `element_type`: - `short_text_entry`: a single line of text. - `long_text_entry`: a paragraph of text. - `number_entry`: a number. The builder's minimum and maximum digit settings (`min`, `max`) are saved with the element but are not enforced when the form is answered at checkout. - `multiple_choice_entry`: one choice from `multiple_choice_options`. - `yes_no_entry`: a yes or no answer from `yes_no_options`. - `checkbox`: a single checkbox. - `file_upload`: a file the respondent uploads. The answer is the file's URL. - `input`: a prebuilt identity field. Its `puck_type` names which one: `email`, `legal_name`, `full_name`, `phone_number`, `date_of_birth`, or `ssn`. - `header`, `information`, `section_label`, `helper_text`, `error_text`, `page_break`, and `button`: layout and text. They collect nothing. - `file_download`: a file the respondent can download. It collects nothing. Checkout also renders the older `text`, `date`, `number`, `email`, `legal_name`, `ssn`, and `date_of_birth` types. It skips any type it doesn't recognize. operationId: forms_v0_list_form_elements parameters: - name: form_id in: path required: true description: ID of the form. schema: type: integer - name: page in: query required: false description: Page number, starting at 1. Defaults to 1. schema: type: integer - name: per_page in: query required: false description: Number of elements per page. Defaults to 20. schema: type: integer - name: filterrific in: query required: false description: >- Not applied by the server. Elements are always sorted by position, lowest first. schema: type: string responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/FormElementListResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/StandardUnauthorizedResponse' '404': description: Not found content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' security: - bearer_auth: [] components: schemas: FormElementListResponse: type: object properties: data: description: The form elements on this page, lowest position first. type: array items: type: object properties: id: description: >- ID of the form element. Answers refer to it as `form_element_id`. type: integer metadata: description: >- The element's settings as the builder saved them, such as its label, options, and `required` flag. type: object properties: label: description: The question or label shown to the respondent. type: string placeholder: description: Placeholder text shown in an empty field. type: string required: description: >- Whether the respondent must answer. At checkout, the form can't be submitted until every required field is answered, and the enrollment stays incomplete until it is. **Respond to a form** doesn't check it. type: boolean required: - label - placeholder - required additionalProperties: false position: description: Zero-based position of the element in the form. type: integer title: description: >- The element's label, its header text, or its type when it has neither. type: string type: description: >- The element type, such as `short_text_entry` or `multiple_choice_entry`. See the operation description for every type. type: string required: - id - metadata - position - title - type additionalProperties: false filters: description: The sort options for form elements. type: object properties: sorted_by: description: >- Sort options as `[label, value]` pairs. This endpoint always returns elements lowest position first. type: array items: type: array items: type: string required: - sorted_by additionalProperties: false meta: $ref: '#/components/schemas/Meta' description: Request metadata. pagination: description: Where this page sits in the full list. type: object properties: current_page: description: The page returned, starting at 1. type: integer per_page: description: The page size used for this response. type: integer total_count: description: Number of records across all pages. type: integer total_pages: description: Number of pages at the requested page size. type: integer required: - current_page - per_page - total_count - total_pages additionalProperties: false required: - data - filters - meta - pagination additionalProperties: false 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: description: Human-readable error message, when the endpoint returns one. type: string error: $ref: '#/components/schemas/ErrorMessage' description: >- Error message or details, when the endpoint returns them under this key. error_message: $ref: '#/components/schemas/ErrorMessage' description: >- Human-readable summary of the error, such as `Form not found` or `Invalid parameters`. errors: $ref: '#/components/schemas/ErrorBag' description: >- Error details, usually keyed by field. For example, a request for the retired pre-purchase type returns a message under `form_type`. meta: $ref: '#/components/schemas/Meta' description: Request metadata. additionalProperties: $ref: '#/components/schemas/JsonValue' Meta: description: Request metadata returned with the response. type: object properties: request_id: description: Identifier of this request, for support and log correlation. type: - string - 'null' timestamp: description: When the server built the response, in ISO 8601. type: string format: date-time 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' 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 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.