> ## 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. # Contacts > Add and edit contacts, assign each one to a rep, delete the ones you no longer need, and get a CSV export of your contacts by email. Use the **Contacts** screen to keep your company's contact records up to date: each person's name, contact details and status, and the rep they're assigned to. ## Where to find it In the admin sidebar, under **People**, select **Contacts**. To open this screen, your role needs **View only** or **Full access** for **Contacts**. **View only** lets you search the list, open contacts and export them. To add, edit or delete contacts, your role needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Contacts** is in the **People** card. Open the card and set access from the **Contacts** area's menu, not the card's. ## What's on the screen The **Export** and **Add Contact** buttons are at the top of the page. Below them is the list of contacts. Use the search box above the list to find contacts by first name, last name, email or phone number. If no contacts match, **No contacts found** appears. More contacts load as you scroll down. The list has these columns: * **ID**: the contact's ID number. * **Name**: the contact's full name. * **Email** and **Phone**: the contact's email address and phone number. * **Status**: the contact's status, such as **New** or **Lead**. A dash means the contact has no value in that column. Click a contact to open its page. Each row's actions menu has **Edit**, which also opens the contact's page, and **Delete**. To select contacts, check the boxes at the start of their rows. The checkbox in the table header selects every contact loaded so far. When you select contacts, the header shows how many, such as **3 selected**, and its actions menu has a delete option for them, such as **Delete 3 rows**. On small screens, the list shows each contact's name, email and status, with no checkboxes or actions menus. Tap a contact to open it. ## Tasks ### Add a contact The **New Contact** page has the **Assign Rep** card at the top, followed by the contact's fields: * **First Name** and **Last Name**: required. * **Email**: optional. If you enter one, it must be a valid email address. * **Phone** * **Status**: **New**, **Active**, **Inactive**, **Cold**, **Lead** or **Customer**. A new contact starts as **New**. * **Full Address**, **City**, **State/Province** and **Postal Code** * **Country**: choose the country from the list. On the **Contacts** screen, click **Add Contact**. The **New Contact** page opens. This step is optional. In the **Assign Rep** card, type a rep's name or email, then select the rep from the results. Only reps appear in the results. Enter the **First Name** and **Last Name**, and fill in any other fields you need. Click **Add Contact** at the top of the page. A confirmation message appears and the contact's page opens. If **First Name** or **Last Name** is empty, a message appears under the field and the contact isn't added. To leave without adding the contact, click **Cancel**. ### Edit a contact A contact's page is titled with the contact's name. On the left, the **Contact Information** card shows the contact's saved name, status, email, phone and address, and the **Assign Rep** card is below it. On the right are the same fields as on the **New Contact** page. **Save** and an actions menu are at the top of the page. In the list, click the contact, or choose **Edit** from its actions menu. Change the fields you need. **Save** stays grayed out until you change something. Click **Save**. A confirmation message appears and you stay on the contact's page. If **First Name** or **Last Name** is empty when you click **Save**, a **Please fix the form errors before saving** message appears and nothing is saved. ### Assign or change a rep The **Assign Rep** card shows the rep the contact is assigned to, with **Clear** and **Edit** buttons. If the contact has no rep, the card shows a search box instead. In the list, click the contact. In the **Assign Rep** card, click **Edit** if the contact already has a rep. Type the rep's name or email, then select the rep from the results. To keep the current rep instead, click **Back**. Click **Save** at the top of the page. The new rep isn't saved until you do. To remove the contact's rep, click **Clear** in the **Assign Rep** card, then click **Save**. ### Export contacts On the **Contacts** screen, click **Export**. The **Export Contacts** dialog opens. Click **Export** in the dialog. A message says your file will be emailed shortly. Fluid emails you a message titled "Your Contacts export is ready". Click **Download** in the email to get the CSV file. Each row in the file is a contact, with the contact's avatar URL, first name, last name, email, phone and status. The file includes all your contacts, so check it before you share it. ### Delete contacts In the list, choose **Delete** from the contact's actions menu. To delete several contacts, select their rows and choose the delete option from the table header's actions menu, such as **Delete 3 rows**. In the **Delete contact?** dialog, click **Delete**. A confirmation message appears. You can also delete a contact from its page. Open the actions menu at the top of the page and choose **Delete**. In the **Delete Contact** dialog, click **Delete**. You return to the contacts list. Deleting a contact can't be undone. ## Frequently asked questions On the **Contacts** screen, click **Add Contact**. Enter the contact's **First Name** and **Last Name**, which are required, and any other details, such as **Email**, **Phone**, **Status**, the address and **Country**. To assign the contact to a rep, choose the rep in the **Assign Rep** card. Then click **Add Contact**. See [Add a contact](#add-a-contact). Use each contact's **Status** and rep. **Status** can be **New**, **Active**, **Inactive**, **Cold**, **Lead** or **Customer**, and the list's **Status** column shows it for every contact. To update a contact, open it, change **Status** or the rep in the **Assign Rep** card, and click **Save**. See [Edit a contact](#edit-a-contact) and [Assign or change a rep](#assign-or-change-a-rep). Adding, editing and deleting contacts needs **Full access** for **Contacts**. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). ## Related pages * [People](/help/admin/people) * [Customers](/help/admin/customers) * [Roles](/help/admin/settings/roles) * [Mobile app](/help/mobile) * [We-Commerce](/concepts/we-commerce) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.