> ## 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. # Turning your mobile app into a brand ambassador > Make every part of your company's app reflect your brand, give your field team what they need each day, and keep the app fresh. Your mobile app is an extension of your brand. It shapes how reps and customers experience your company every day. This guide shows how to make your app reflect your mission and values. ## Build a strategic foundation Before you think about design, define your app's core purpose. What should your reps get done when they open it each day? Prioritize the features that serve your mission, such as: * Product education and ordering * Team communication and support * Rep performance * Targeted training * Social sharing and recruiting Choose features that serve your reps' daily needs and reinforce your brand values. ## Create content that drives engagement Great content tells your brand's story and keeps reps coming back. Every piece, from product demos to success stories, should reinforce what makes your company unique. ### What makes content meaningful Deliver real value through: * Product demonstrations and tutorials * Success stories and testimonials * Training resources and guides * Company news and announcements * Recognition and achievements Mix content types. Combine eye-catching photos, engaging videos and helpful documents to keep your audience interested and informed. ### Visual quality matters Professional presentation builds trust. Your visual content should include: * High-quality product photos * Videos that stop the scroll * Consistent branding And follow the technical basics: * Use the right image sizes. * Design for phones. * Keep image quality high. ## Design for brand consistency Your app should feel familiar to anyone who knows your company. Set your logos, colors, fonts and brand voice in the admin's [Brand Guidelines](/help/admin/settings/brand-guidelines), and build your app's screens with [Home Tabs](/help/admin/mobile/home), [Share Tabs](/help/admin/mobile/share) and [Shop Tabs](/help/admin/mobile/shop). Brand consistency goes beyond looks. The way people use your app should reflect your brand's personality, whether that's energetic and bold, sophisticated and premium, or professional yet approachable. Consider how to: * Structure navigation so it feels natural * Organize content to tell your brand story * Design widgets that catch attention * Set up features that simplify daily tasks * Make sharing easy ## Empower your field team Success in direct selling comes from having the right tools at the right time. Make your app the first thing your field leaders open each morning. ### Build their knowledge base Make your app a learning hub. Start with: * Quick-start onboarding that gets new team members selling fast * Short product trainings they can watch between appointments * Step-by-step business-building guides * Compliance guidelines * Leadership lessons from your top performers Make training easy to find when your team needs it. Create playlists for different situations: | Playlist | Description | | - | - | | New rep launch | Their first 30 days, in easy steps | | Business builder track | Advanced strategies for serious entrepreneurs | | Product expert path | Deep dives into your product line | ### Give them the right tools What does your field team need to succeed today? Fluid's mobile app gives them: * **Insight:** their own analytics, recent activity, and a leaderboard * **Customer connections:** their contacts, follow-up suggestions in **Catch Up**, and a to-do list * **Momentum:** upcoming events and company announcements Add the matching widgets, such as **Analytics**, **Recent Activity**, **Leaderboard**, **Catchup**, **To-Do List**, **Calendar** and **Announcements**, to your app's Home screen in [Home Tabs](/help/admin/mobile/home). ## Keep it relevant Your app should feel alive, with something new whenever your team opens it. ### Keep content fresh Don't let your app become yesterday's news. Surprise your team with: * Flash promotions * Behind-the-scenes looks at new products * Unexpected recognition * Leaderboard updates * Company news Time your content well: * Monday motivation to start the week * Midweek training refreshers * Friday celebrations * Weekend sharing prompts ### Turn data into action Your app shows what your field team needs. **Track what matters:** * Which content gets the most engagement? * When do reps use training? * Which features get used most? * Where do people drop off? **Then act on it:** * Promote your best content. * Retire or refresh stale material. * Add the content people ask for. * Remove clutter. The best apps evolve with their users. Review your results every month to spot trends and opportunities. ## Create a unified experience Your app should fit your overall digital strategy while giving reps something unique on the go. With careful attention to branding, content and features, it serves your field team and strengthens their connection to your brand. Your app grows with your business. Review and refresh its content, features and design regularly, so it keeps meeting your organization's needs. ## Frequently asked questions Focus on these areas to create a consistent brand experience for your team and customers. **Strategic foundation** | Element | Purpose | What to do | How to measure it | | - | - | - | - | | Core features | Daily value | Product education and ordering, team communication, performance and goals, social sharing and recruiting | How many people use each feature, and how often | | Brand values | Mission alignment | Prioritize features, plan content and recognize achievements in line with your values | Brand consistency, satisfaction and team feedback | | User journey | Getting things done | Clear navigation, clear paths, simple processes and help in context | Time to complete tasks, errors and support requests | **Visual identity** | Element | Requirements | Best practices | | - | - | - | | Colors | Your brand palette | Use them consistently, keep good contrast, and test on every device and in dark mode. A common guideline is 60% main color, 30% secondary and 10% accent. | | Logo | Brand recognition | Place it where it's clearly visible, at the right size, such as in the header and in shared content. | | Typography | Your brand fonts | Use readable sizes (at least 16 px for body text), a clear hierarchy and few font families. | Set your logos, colors and fonts in [Brand Guidelines](/help/admin/settings/brand-guidelines). **User experience** | Element | Focus | What to do | | - | - | - | | Onboarding | First impression | A welcome sequence, feature discovery and quick wins | | Navigation | Efficiency | Put priority features first, and make recent activity easy to find | | Personalization | Relevance | Show pages to the right people with access rules by rank, country, language and member type, in [Home Tabs](/help/admin/mobile/home) | Consistency across every touchpoint matters. Your app should feel like a natural extension of your brand, not a separate thing. ## Related pages * [Brand Guidelines](/help/admin/settings/brand-guidelines) * [Mobile App](/help/admin/mobile) * [App design essentials](/help/playbook/essential-elements-for-successful-app-design) * [App engagement](/help/playbook/maximizing-app-engagement-your-strategy-guide) ## 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.