> ## 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. # Maximizing the Fluid mobile app for sales > Use the mobile app to stay in touch with customers and your team, make the most of events, share content and keep learning. The mobile app puts your business in your pocket. Use it to connect with customers, keep up with your team, share content and track your results. ## Get started Download your company's app from the App Store or Google Play. Sign in with your email address. Your home screen is set up by your company. Take a moment to see what's there, such as your recent activity and your results. ## Stay in touch Messaging in the app keeps you connected in three ways: * **Customer and contact messages.** Answer questions quickly and personally, and keep each conversation in one place. * **Team chats.** Start a team or group message to share wins and best practices, coordinate activities, and learn from each other. * **Broadcast channels.** Follow company-wide updates, such as product launches, promotions, training opportunities and recognition. Your company posts in these channels, and everyone else reads. ## Make the most of events Your company's events appear in the app's calendar. From an event, you can add it to your phone's calendar, copy its details to share with your contacts, and join it through its link. If your company turns on an event's notifications, Fluid also reminds you about an hour before it starts. Before an event: 1. Share it with your contacts early. 2. Explain what attendees will learn or get. 3. Invite people personally, not just with a broadcast. The most successful events combine education with excitement. Give attendees something to learn and something to celebrate. ## Share your story Your content can make a real difference when you share it well. Share: * Before-and-after results * Product demonstrations that solve real problems * Success stories that inspire action * Results that show what's possible When you share with a specific person, send it as a SmartLink. What they do with your content then shows in their activity, so you can focus your follow-up where it matters most. ## Keep learning Your company's trainings are in the app. Make time for them, and focus on: * **Business fundamentals and daily operations**, the core skills your business is built on. * **Product knowledge**, so you can show real value in every conversation. * **Professional skills** such as leadership and communication, which help you build your team. * **Compliance**, so you always work within your company's and your industry's guidelines. ## Build a daily routine **In the morning:** 1. Check your home screen and your results. 2. Reply to priority messages. 3. Check upcoming events. 4. Continue a training. **During the day:** * Share content when your audience is most active. * Follow up with prospects while they're still interested. * Keep your team's energy high with regular check-ins. **At the end of the day:** 1. Review your results. 2. Plan tomorrow's priorities. 3. Look ahead to upcoming events. 4. Clear completed tasks. Aim to make at least 5 meaningful customer connections every day. ## Measure what matters Keep an eye on: * Sales and how they're trending * Event attendance * How people interact with your content * Team activity * Customer satisfaction Use the app's analytics to track your progress toward your goals, spot what's working, adjust your approach, and celebrate your team's wins. ## Frequently asked questions Brand teams create events in the admin's [Events](/help/admin/events) screen. Make each part count: | Part of the event | Best practice | Why it matters | | - | - | - | | Title | Compelling and action-oriented | Sparks interest right away | | Dates and time zone | Pick them carefully, in the right time zone | Makes it easy to attend, wherever people are | | Location or link | Easy to reach, or a working online meeting link | Helps people show up | | Images | Eye-catching event graphics | Creates excitement | | Description | A clear reason to attend | Motivates people to come | | Countries | Only the countries the event is for | Reaches the right audience | Plan the event in phases: | Phase | Key actions | | - | - | | 2 to 3 weeks before | Create the event, write the description, choose images and set the countries. Plan interactive moments, success stories and a clear call to action. | | 1 to 2 weeks before | Start promoting it, and encourage your team to share it. You can also send a push notification about the event from its page in the admin. It goes to every active rep and admin, so use it only for company-wide events. | | On the day | Fluid reminds reps in the event's countries about an hour before it starts, if the event's notifications are on. Test your technology, prepare your materials, and welcome people as they arrive. | | Afterward | Share the recording and resources, thank attendees, gather feedback and testimonials, and plan what's next. | Great events start strong, stay interactive, and end with clear next steps. They deliver clear value, solve real problems and inspire action. Leave attendees both educated and energized. ## Related pages * [Events](/help/admin/events) * [Messaging](/help/admin/messages) * [Authentic conversations](/help/playbook/beyond-the-sales-pitch-creating-authentic-digital-conversations-that-convert) * [Mobile app](/help/mobile) ## Get help Email Fluid support at [help@fluid.app](mailto:help@fluid.app). The [Getting help](/help/getting-help) page lists what to include in your request. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.