> ## 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. # Posts > Write and manage your storefront's blog posts: content, author and date, status and scheduling, SEO, countries, theme template and translations. Use the **Posts** screen to write blog posts for your storefront and control when and where they appear. ## Where to find it In the admin sidebar, under **Storefront**, select **Posts**. To open this screen, your role needs **View only** or **Full access** for **Posts**. To create, edit or delete posts, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Posts** is in the **Content & Website** card. Open the card and set access from the **Posts** area's menu, not the card's. ## What's on the screen **Add Post** is at the top of the screen. * The **All**, **Published**, **Scheduled**, **Draft** and **Archived** tabs filter the list by status. * Use the search box to find posts. * **Filters** has **Status** and **Country**. The **Status** filter and the tabs stay in step. **Country** shows the posts available in the country you pick; **All Countries** clears it. The list has these columns: * **Preview**: the post's image, or an empty frame if it has none. * **Title**: click it, or anywhere else on the row, to open the post. A post with no title shows **Untitled**. You can sort by this column. * **Status**: **Published**, **Draft**, **Archived**, or **Scheduled** with its publish date and time. * **Countries**: flags for the countries the post is available in, with **+** and a number when there are more than two. **All** means the post has no country restriction and is available everywhere you sell. * **Publish Date**: the date set in the post's **Publish Date** field, or a dash if it has none. Each row's actions menu has **Edit** and **Delete**. Select several rows to delete them together with **Delete**. ## Create a post On the **Posts** screen, click **Add Post**. The **Create Post** screen opens. In the **Post Details** card, enter a **Title**. It's required. Enter the **Description** in the text editor. Under **Media**, click **Select Image** to choose the post's image: JPG, PNG, GIF, WebP, BMP or SVG, up to 10MB. In the **Additional Details** card, enter a **Summary**, a **Publish Date** and an **Author** if you use them. **Publish Date** is the post's date, shown in the list; it doesn't schedule the post. Leave **Active** on (see [Status and the Active switch](#status-and-the-active-switch)). In the **Countries** card, leave the field empty to make the post available everywhere you sell, or choose specific countries. In the **Theme Template** card, your active theme's default post template is selected for you. Choose another if you need to. If your theme has no post templates yet, choose **Create Template** from the list. This adds a template named **New Post Template**, with placeholder content, to your active theme and selects it for the post. You need an active theme. In the **SEO And Link Sharing** card, click **Edit**. See [Set SEO and the post URL](#set-seo-and-the-post-url). A new post starts as **Published** in the **Status** card. Click **Publish** to create the post and make it live. To keep it hidden while you work on it, open the menu next to **Publish** and choose **Save as Draft**. The buttons are grayed out until the post has a title. A confirmation message appears and the post's detail screen opens. ## Status and the Active switch The **Status** card on the right sets where the post is in its life: * **Published**: live and visible to the public. * **Draft**: hidden from public view. * **Scheduled**: goes live automatically at a date and time you choose. See [Schedule a post](#schedule-a-post). * **Archived**: retired and hidden from public view. The **Active** switch in **Additional Details** is separate. Turn it off to hide the post everywhere, whatever its status. A banner above the **Post Details** card tells you when the post is a draft, archived, scheduled or turned off. ## Edit a post In the list, click the post's title, or choose **Edit** from its actions menu. The **Post Details** screen opens with the post's title and status badge at the top. Change the fields in the **Post Details** and **Additional Details** cards and the cards on the right. Click **Save**. For a draft, the button reads **Save Draft**. A confirmation message appears and you stay on the post. To change a saved post's status, for example to **Archived**, choose another status in the **Status** card and click **Save** (**Save Draft** if you chose **Draft**). To publish a draft, open the menu next to **Save Draft** and choose **Publish Now**. It saves your changes and publishes the post. The top of a saved post also has: * **Actions**: a menu with **Publish Now** (shown for scheduled posts) and **Delete Post**. **Publish Now** saves your changes and publishes the post right away. * **Translations**: see [Translate a post](#translate-a-post). * **Preview**: opens the post on your storefront in a new tab. It's grayed out until the post has a storefront URL. To change a saved post's template, choose one in the **Theme Template** card and click **Save**. The **Metafields** card below **Additional Details** shows the metafields defined for posts. **Manage Definitions** takes you to [Metadata Definitions](/help/admin/settings/metadata-definitions) in Settings. The **Posts** link at the top of a post takes you back to the list with the search, tab and filters you left it with. ## Schedule a post On the post, in the **Status** card, choose **Scheduled**. A date and time picker opens below it. Choose a date and time in the future, then click **Schedule Activation**. The card shows **Scheduled for activation** with the date and time. Click **Save**, or **Schedule** for a new post. If you save a scheduled post with no date or a date in the past, an error message appears and nothing is saved. To publish a scheduled post early, choose **Publish Now** from the **Actions** menu. Scheduling isn't a privacy setting. The date controls when the post appears in listings and can be indexed by search engines, but anyone with the direct link can open it before then. To keep a post out of public listings while you work on it, use **Draft**. ## Set SEO and the post URL In the **SEO And Link Sharing** card, click **Edit**. The panel has the same fields and limits as for pages: **Title Tag**, **Meta Description**, **Use custom slug** with **URL Slug**, and **Search engine visibility**. See [Set SEO and the page URL](/help/admin/pages#set-seo-and-the-page-url) for the details. **Done** stays grayed out until the **Title Tag** has at least 3 characters and the **Meta Description** at least 5. Click **Done**, then save the post. The **URL** field shows the post's address on your storefront, under `/home/blog/`. If you don't set an SEO image, the post's image from **Media** is used. ## Translate a post On a saved post, click **Translations**. You can translate the **Title**, **Description**, **Summary** and **Post Image** for each of your company's active languages. Click **Save** in the translations panel. Translations are saved there, separately from the post's **Save** button. **Language Settings** opens your [Languages](/help/admin/settings/languages) settings in a new tab. For more, see [Translate a page](/help/admin/pages#translate-a-page). ## Delete a post In the list, choose **Delete** from the post's actions menu. To delete several posts, select their rows and choose **Delete**. On a post, choose **Delete Post** from the **Actions** menu. In the confirmation dialog, click **Delete** (or **Delete Post**). From a post, you return to the list. Deleting a post can't be undone. To take a post down but keep it, set its status to **Archived** instead. ## Analytics Once a post is saved, the **Analytics** card on the right shows **Page Views**, **Shares**, **Page Speed** and **Content Compliance**, as it does for pages. Click a metric for details. See [Analytics](/help/admin/pages#analytics). ## Frequently asked questions No. **Publish Date** is the post's date, shown in the list. It doesn't control when the post goes live. To publish a post later, choose **Scheduled** in the **Status** card. See [Schedule a post](#schedule-a-post). New posts start with the status **Published**. To create a post without publishing it, choose **Save as Draft** from the menu next to **Publish**. To unpublish a saved post, change its status to **Draft** and click **Save Draft**. Your role can view posts but isn't allowed to edit them, so you can't change their fields and there's no **Save** button. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). ## Related pages * [Storefront](/help/admin/storefront) * [Pages](/help/admin/pages) * [Metadata Definitions](/help/admin/settings/metadata-definitions) * [Roles](/help/admin/settings/roles) * [Storefront resources: posts (developer guide)](/storefront/resources#posts) * [Visibility, drafts, and scheduling](/storefront/visibility) * [SEO](/storefront/seo) * [Slugs and URLs](/storefront/slugs-and-urls) * [Country availability](/storefront/country-availability) * [Translations](/storefront/translations) * [Metafields](/storefront/metafields) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.