> ## 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. > 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. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/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. > Navigation menu management is documented in themes/navigation-menus. These unversioned admin endpoints (/api/menus and nested menu_items) are verified against the implementation but are not yet in the synced OpenAPI specs. Use that reference for menu payloads and its flat page/per_page pagination; missing spec coverage does not make these endpoints unavailable. > 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. # Social Media > Save your company's social media profile links, one per platform, and edit or remove them from the Social Media settings screen. Use the **Social Media** screen to keep the addresses of your company's social media profiles in one list. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Company**, select **Social Media**. ## What's on the screen The list shows the links you've saved. Click **Add Social Media Link** at the top of the screen to add one. The list has two columns: * **Platform**: the platform's icon and name. * **URL**: the full profile address. Use the **Search...** box above the list to find a link by platform or URL. You can sort the list by **Platform**. When you haven't saved any links, the list shows **Nothing to show**. The three-dot menu at the end of each row has **Edit** and **Delete**. To open the screen, your role needs at least **View only** for **Company Settings**, in the **Settings** card. To add, edit or delete links, it needs **Full access** for **Company Settings**. Without it, you can see the list, but **Add Social Media Link** and the row's three-dot menu don't appear. See [Roles](/help/admin/settings/roles). ### Link panel fields Clicking **Add Social Media Link** opens the **New Social Media Link** panel. Choosing **Edit** on a row opens the **Edit Social Media Link** panel. Both have these fields: * **Platform**: **Facebook**, **Twitter**, **Instagram**, **Linkedin**, **Youtube**, **Tiktok** or **Pinterest**. New links start with **Facebook**. You can't change the platform when you edit a link. Each platform holds one link. Saving a link for a platform that already has one replaces it. * **URL**: your profile on that platform. This field is required. Click **Save** to save the link, or **Cancel** to close the panel without saving. ### What to enter in URL In **URL**, enter only the part of your profile address after the domain, even though the field asks for a URL. Fluid adds the platform's address in front of it: * For `https://www.facebook.com/example-shop`, enter `example-shop`. * For `https://www.linkedin.com/company/example-shop`, enter `company/example-shop`. ## Add a link Click **Add Social Media Link**. Under **Platform**, choose the platform for this link. If the platform already has a link, saving replaces it. In **URL**, enter the part of your profile address after the domain (see [What to enter in URL](#what-to-enter-in-url)). Click **Save**. The link appears in the list. If an error message appears instead, the link wasn't saved. ## Edit a link In the list, open the three-dot menu at the end of the link's row and choose **Edit**. Update **URL**, then check that it matches the part of your profile address after the domain (see [Why doesn't URL match my address when I edit a link?](#edit-url-differs)). Click **Save**. If you saved a link under the wrong platform, delete it and add it again under the right one. ## Delete a link Deleting takes effect right away. There's no confirmation step. In the list, choose **Delete** from the link's three-dot menu. The link disappears from the list. If it's still in the list, it wasn't deleted. To delete several links, select the checkbox at the start of each link's row. Then open the three-dot menu that appears at the top of the list and choose the delete option, for example **Delete 3 rows**. On a small screen, that menu appears in a bar near the bottom of the screen instead. ## FAQ The link was saved with the full profile address. Follow [Edit a link](#edit-a-link). **URL** shows the address you saved, so delete everything up to and including the domain and the slash after it. Check the rest against your profile address, then click **Save**. When you edit a link, **URL** leaves out any part of your address that starts with `?` or `#`, and some characters can appear encoded, for example `%20` for a space. Before you click **Save**, make sure **URL** matches the part of your profile address after the domain, and add back anything that's missing. ## Related pages * [Settings](/help/admin/settings) * [Roles](/help/admin/settings/roles) * [Brand Guidelines](/help/admin/settings/brand-guidelines)