> ## 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. # Sign a direct upload > Signs an upload of one image, video, PDF or presentation to a path in the member's own storage namespace and records its receipt. The signature expires after 15 minutes. Declared sizes over the type's limit (images 10 MB, videos 100 MB, documents 25 MB) are refused. Responses are never stored. ## OpenAPI ````yaml /api-reference/member-content-v2026-10.yaml post /api/member/v2026-10/media/uploads openapi: 3.1.0 info: title: Fluid Member API v2026-10 — Content description: >- The signed-in member's own media and playlists: list, read, write, and delete, including direct media uploads and media creation. The bearer credential determines the member and company; no path, query or body parameter can change either. Only rep-eligible memberships may use these endpoints; other memberships receive 403. Foreign, deleted, and malformed identifiers return 404. Playlist items are separate operations outside this contract. Upload bytes never pass through this API: `POST /media/uploads` signs a direct upload bound to one path in the member's own storage namespace, the client posts the file to the returned URL with the returned fields, and `POST /media` then verifies the stored object and creates the medium, consuming the upload once. contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary version: 2026-10 servers: - url: https://api.fluid.app description: Production API server - url: https://api.fluid.test description: Local development server security: - MemberBearer: [] tags: - name: media description: The signed-in member's own uploaded media. x-fluid-section: Members - name: playlists description: Ordered collections of media the member assembles to share. x-fluid-section: Members - name: shares description: Tracked links the member created, and what happened to them. x-fluid-section: Members - name: playlist-items description: Items and ordering in a member-owned playlist. x-fluid-section: Members - name: search description: Ranked search across the company's public storefront catalogue. x-fluid-section: Members - name: media-uploads description: Signed direct uploads that become the member's media. x-fluid-section: Members paths: /api/member/v2026-10/media/uploads: post: tags: - media-uploads summary: Sign a direct upload description: >- Signs an upload of one image, video, PDF or presentation to a path in the member's own storage namespace and records its receipt. The signature expires after 15 minutes. Declared sizes over the type's limit (images 10 MB, videos 100 MB, documents 25 MB) are refused. Responses are never stored. operationId: member_media_uploads_create requestBody: required: true content: application/json: schema: type: object description: The file about to be uploaded. additionalProperties: false required: - content_type - filename properties: content_type: type: string minLength: 1 maxLength: 255 pattern: >- ^[^\u0000]*[^\u0000\u0009-\u000D\u0020\u0085\u00A0\u1680\u2000-\u200A\u2028\u2029\u202F\u205F\u3000][^\u0000]*$ description: >- MIME type of the file, containing at least one non-whitespace character and no NUL. filename: type: string minLength: 1 maxLength: 255 pattern: >- ^[^\u0000]*[^\u0000\u0009-\u000D\u0020\u0085\u00A0\u1680\u2000-\u200A\u2028\u2029\u202F\u205F\u3000][^\u0000]*$ description: >- Original file name, containing at least one non-whitespace character and no NUL; it is sanitized and prefixed to keep paths unique. byte_size: type: integer minimum: 1 description: >- Size in bytes. When given, the stored file must match it exactly. example: content_type: video/mp4 filename: morning-routine.mp4 byte_size: 48213000 responses: '201': description: The signed upload. headers: Cache-Control: $ref: '#/components/headers/CacheControl' content: application/json: schema: $ref: '#/components/schemas/UploadEnvelope' example: status: 201 data: upload_id: 0199a3f2-5b0d-7c3a-8f09-2a1b0c9d8e7f url: https://upload.imagekit.io/api/v2/files/upload fields: token: >- eyJhbGciOiJIUzI1NiJ9.eyJmb2xkZXIiOiJjb21wYW5pZXMvLi4uIn0.signature fileName: Xk3p9QaB_morning-routine.mp4 folder: >- companies/0199a1b2-0000-7000-8000-000000000001/members/0199a1b2-0000-7000-8000-000000000002/uploads/videos useUniqueFileName: 'false' overwriteFile: 'false' expires_at: '2026-09-30T18:39:05Z' meta: request_uuid: 0199a3f2-7a10-7c3e-8f21-4d5e6f708192 timestamp: '2026-09-30T18:24:05Z' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '422': $ref: '#/components/responses/Invalid' '503': $ref: '#/components/responses/UploadUnavailable' components: headers: CacheControl: description: >- Standard HTTP Cache-Control directive. Private for member reads; no-store for search and uploads. Media reads send max-age=0, so a client revalidates with If-None-Match on every use. schema: type: string example: max-age=0, private schemas: UploadEnvelope: type: object description: One signed upload. properties: status: type: integer description: HTTP response status. data: $ref: '#/components/schemas/Upload' meta: $ref: '#/components/schemas/ResponseMeta' required: - status - data - meta Upload: type: object description: >- A signed direct upload. POST the file as multipart form data to `url`, sending every entry of `fields` unchanged plus the file as `file`, before `expires_at`. Then create the medium with `upload_id`. additionalProperties: false properties: upload_id: type: string format: uuid description: Receipt id; send it to POST /media once the file is stored. url: type: string format: uri description: Where to post the file. fields: type: object description: Signed form fields to post with the file, unchanged. additionalProperties: type: string expires_at: type: string format: date-time description: >- When the signature expires. POST /media accepts the upload for one hour after this. required: - upload_id - url - fields - expires_at ResponseMeta: type: object description: Envelope metadata present on every response. properties: request_uuid: type: string format: uuid description: Server-generated UUIDv7 uniquely identifying this response. timestamp: type: string format: date-time description: ISO 8601 timestamp at which the server produced the response. required: - request_uuid - timestamp additionalProperties: true ErrorEnvelope: type: object description: Standard error envelope. properties: status: type: integer description: HTTP status code (mirrors the response status line). error: type: object description: The error message and field-keyed details. properties: message: type: string description: Human-readable error message. details: type: object description: Field-keyed error details. additionalProperties: true required: - message - details meta: $ref: '#/components/schemas/ResponseMeta' required: - status - error - meta responses: BadRequest: description: The JSON request body is malformed. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' Unauthorized: description: Missing or unusable member credential. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' Forbidden: description: >- The membership cannot share content, or the credential is read-only and the request writes. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' Invalid: description: >- Unsupported parameter, invalid value, or a validation failure, with field-keyed details. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' UploadUnavailable: description: >- Upload storage is unavailable or could not be asked; retry later. An upload is never consumed by this response. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' securitySchemes: MemberBearer: type: http scheme: bearer description: | A member credential in the `Authorization: Bearer` header: a member session JWT, a portal JWT whose login is linked to a membership in that company, or an opaque member token. The credential alone identifies the member and company. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.