> ## 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 <token>; public storefront read endpoints require no auth.
> To sign a new merchant up for Fluid programmatically, run `fluid signup` from the Fluid CLI, or 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. Before authenticated calls are possible, the merchant must sign the agent in to the Fluid CLI with the emailed code and --shop set to the company's fluid_shop (which also confirms the signup), or open the emailed confirmation link and give the agent an API token.
> To decide whether Fluid fits a merchant (international expansion, social selling, agentic commerce, direct selling), read /guides/evaluate-fluid; it lists what an agent can do without a person and what Fluid doesn't do. To compare Fluid with Shopify, BigCommerce, Salesforce Commerce Cloud, commercetools, WooCommerce, Wix, Exigo or DirectScale, read /guides/compare-platforms. Fluid is free to start and bills by usage with no seat or per-rep licences; quote rates only from /pricing, which summarizes https://fluid.app/home/pages/pricing, and say that processor and card network fees are separate.
> Every live Fluid storefront serves /llms.txt, /agents.md, .md and .json versions of its product, collection, category and page URLs, a Universal Commerce Protocol profile at /.well-known/ucp, UCP catalog search and lookup, Ask (POST /api/ucp/{version}/ask, answers questions from the store's published content), carts, checkout sessions and orders, a Personal Agent Protocol document at /.well-known/poppy.json, and an A2A Agent Card at /.well-known/agent-card.json with a JSON-RPC endpoint at /api/a2a. A checkout session completes inside the agent with Google Pay when the store's profile lists the com.google.pay payment handler; otherwise hand the shopper the continue_url to hosted checkout. A member's share link is /<username>/products/<slug>; see /concepts/agentic-commerce, /concepts/poppy, /concepts/ucp and /concepts/a2a.
> 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.
> To host a small project on Fluid (a landing page, event page, calculator or dashboard), follow /sites/quickstart: npm create @fluid-app/fluid-site my-site (or npx @fluid-app/create-fluid-site my-site), fluid login, then fluid deploy prints the public URL. Launch a Site unless the project needs a custom domain, server rendering or heavy server code, which make it an App (a Mist app); /sites/site-or-app has the rule, and POST /api/company/v2026-10/project-launch-recommendations applies it. With only the Fluid MCP server (its Site write tools are limited to Fluid root admins today; see /sites/deploy-from-claude), use site_create, then site_deploy (from a chat with no shell, in one call with the files inline: site_template_get for a starter, then site_deploy with each path's content; or a built folder in two calls: send the manifest, PUT the listed uploads, call again with the bundle_id to get the url), then, only after the person confirms they want it public, site_visibility_set. site_logs, site_traffic, site_env_list/set/unset, site_seo_get/set and the site_branch tools cover logs, traffic, env vars, SEO and preview branches; a member builds their own Sites with the my_site_* tools. The MCP site_deploy tool publishes server functions sent inline that import nothing; publish functions with imports, and convert a Site to an App, with the fluid sites CLI. A Site can serve light server code: each functions/<name>.ts, declared in config/functions.json with access public, signed_in or key (and an optional UTC cron schedule), answers at /api/<name> on the Site's own host; publish it with fluid deploy, or inline through the MCP site_deploy tool when it imports nothing. See /sites/functions and /sites/rest-api.
> 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 on an operation whose spec documents those params — mostly the unversioned company-v0 admin surface, plus some lists on other surfaces, versioned ones included; page every other list with cursors.
> To create a URL redirect, create a custom route on the Sitemap: POST /api/theme_region_rules with redirect_type redirect, a redirect_url, region_code default, route_kind non_credit and redirect_status_code 301 or 302. See /themes/custom-routes#create-a-redirect-with-the-api. Never use /api/redirects; those legacy redirects are no longer used, and the admin's Sitemap screen doesn't show them.
> 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 except two operations that take no credential, POST /api/company (create a company) and GET /api/agreements/{id} — 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.

# Connect Amazon

> Connect an Amazon Seller Central account to Fluid, pick the marketplace, list products as Amazon offers, and see the Amazon orders Fluid imports.

Connecting Amazon lists your Fluid products as offers on Amazon and imports Amazon orders into Fluid. Fluid lists each variant as an offer on the Amazon product page that matches its barcode, in one Amazon marketplace you choose. Setup takes a person in a browser for one step: approving Fluid's access in Seller Central. Every other step is an API call.

## Before you start

* An Amazon Seller Central account, and a person who can sign in to it and approve apps.
* The seller account isn't connected to another Fluid company. One seller account connects to one company.
* A Fluid API token for the company with company admin access: **Company settings** permission to connect, choose the marketplace and disconnect, and **Products** permission to list products. The examples use it as `$FLUID_TOKEN`.
* A live company. A test store can't connect a sales channel.

## Steps

**1. Start the connection**

Pick the Seller Central region your account sells in:

| `region` | Marketplaces |
| - | - |
| `NA` (the default) | United States, Canada, Mexico and Brazil |
| `EU` | United Kingdom, Europe, the Middle East and India |
| `FE` | Japan, Australia and Singapore |

```bash theme={null}
curl -X POST "https://api.fluid.app/api/v202506/amazon/connection/authorize_url" \
  -H "Authorization: Bearer $FLUID_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"region": "NA"}'
```

The response's `url` is the Seller Central consent link. Nothing changes in Fluid until someone approves it in the next step. Open the link yourself, or send it to the person who will approve it. The link works once and expires after 10 minutes; call `authorize_url` again for a new one.

**2. Approve Fluid in Seller Central**

Sign in to Seller Central and authorize Fluid.

Amazon then sends the browser back to Fluid admin. The address ends in `connect=ok` when the connection saved, or `connect=error&reason=...` when it didn't. Whatever the page shows, check the result:

```bash theme={null}
curl "https://api.fluid.app/api/v202506/amazon/connection" \
  -H "Authorization: Bearer $FLUID_TOKEN"
```

The step is done when `connection.status` is `connected`. `connection.display_name` names the seller account, and `connection.marketplace_id` is the marketplace Fluid picked: the first one the seller sells in.

**3. Choose the marketplace**

Fluid lists products and imports orders in one marketplace. Skip this step if `marketplace_id` is already the one you want. Otherwise set it, for example to `ATVPDKIKX0DER` for amazon.com:

```bash theme={null}
curl -X PATCH "https://api.fluid.app/api/v202506/amazon/connection" \
  -H "Authorization: Bearer $FLUID_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"marketplace_id": "ATVPDKIKX0DER"}'
```

Fluid checks the marketplace with Amazon. It fails with `422` if the seller doesn't sell in it.

**4. List products**

This changes live configuration: it creates offers on Amazon. Start with a few products if you haven't sold on Amazon through Fluid before.

```bash theme={null}
curl -X POST "https://api.fluid.app/api/v202506/amazon/product_listings" \
  -H "Authorization: Bearer $FLUID_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"product_ids": [48213, 48227]}'
```

Fluid creates one listing per product and publishes it in the background. Products already live on Amazon are skipped, so sending the same IDs again is safe.

**5. Check the listings**

```bash theme={null}
curl "https://api.fluid.app/api/v202506/amazon/product_listings" \
  -H "Authorization: Bearer $FLUID_TOKEN"
```

Repeat until no listing is `draft`. `pending` means Amazon accepted the offers and is processing them. The list is newest first, 25 per page; pass `meta.pagination.next_cursor` back as `page[cursor]` for the next page, or `filter[product_id]` to check one product.

**6. Fix rejected products**

A listing with `status` `publish_failed` wasn't listed. `last_error` says why, for example a missing barcode or a product Amazon restricts for your account. Fix it, then retry the listing:

```bash theme={null}
curl -X POST "https://api.fluid.app/api/v202506/amazon/product_listings/5512/retry" \
  -H "Authorization: Bearer $FLUID_TOKEN"
```

The step is done when no listing is `publish_failed`.

## What each product needs

* A marketplace chosen on the connection.
* A SKU, a price and a barcode on every variant you list. Fluid uses the barcode to find the matching Amazon product, so the barcode has to match a product already in Amazon's catalog.
* A SKU that isn't used by another listing on the connection.
* Permission from Amazon to sell the product. Fluid checks Amazon's listing restrictions before it creates any offer, and a restricted product fails with the restriction named in `last_error`.

## Amazon orders

Fluid checks Amazon for new and updated orders on a schedule and imports each one as a Fluid order. To see what Fluid has imported, including orders it couldn't import:

```bash theme={null}
curl "https://api.fluid.app/api/v202506/amazon/orders" \
  -H "Authorization: Bearer $FLUID_TOKEN"
```

Filter with `filter[ingestion_state]`, or `filter[commerce_order_id]` to find the Amazon order behind a Fluid order. An order whose SKU doesn't match a listed Fluid variant isn't imported; its row says why.

## What the status means

| Field and value | What it means | What to do |
| - | - | - |
| `connection.status`: `pending` | The consent link was created but nobody has approved it yet. | Finish step 2, or start again. |
| `connection.status`: `connected` | Fluid can reach Amazon. | Continue with the marketplace and products. |
| `connection.status`: `expired` or `deauthorized` | Amazon no longer accepts Fluid's access, usually because the seller removed the authorization in Seller Central. | Run step 1 again and approve it. |
| `connection.status`: `disconnected` | Someone disconnected the channel. | Run step 1 again to reconnect. |
| listing `status`: `draft` | Fluid hasn't sent the product yet. | Check again later. |
| listing `status`: `pending` | Amazon accepted the offers and is processing them. | Check the offers in Seller Central. |
| listing `status`: `publish_failed` | A pre-flight check or Amazon rejected the product. | Fix what `last_error` names, then retry. |
| listing `status`: `platform_deactivated` or `frozen` | Amazon took the offer down. | Check the reason in Seller Central. |
| listing `status`: `deleted` or `seller_deactivated` | You removed the product. | List it again to bring it back. |

## Troubleshooting

* **`authorize_url` fails with `422`.** Fluid couldn't start the connection. A test store gets this every time. Otherwise contact Fluid support.
* **The address after approving ends in `connect=error`.** The `reason` says why. `invalid_state` means the link was used twice or expired: start again for a new one.
* **The reason is `no_marketplaces`.** The seller account doesn't sell in any marketplace yet. Finish setting up the account in Seller Central, then start again.
* **The reason is `seller_already_connected`.** Another Fluid company already holds this seller account. Disconnect it there first.
* **Choosing the marketplace fails with `422`.** The seller doesn't sell in that marketplace, or Fluid couldn't reach Amazon to check. Use a marketplace from your Seller Central account.
* **A call fails with `404`.** The company has never connected Amazon. Run step 1.
* **A call fails with `403`.** Your token lacks the permission that call needs: **Company settings** for the connection, **Products** for products.

## Remove products and disconnect

To take one product off Amazon, delete its listing. This deletes its offers on Amazon:

```bash theme={null}
curl -X DELETE "https://api.fluid.app/api/v202506/amazon/product_listings/5512" \
  -H "Authorization: Bearer $FLUID_TOKEN"
```

To disconnect:

```bash theme={null}
curl -X DELETE "https://api.fluid.app/api/v202506/amazon/connection" \
  -H "Authorization: Bearer $FLUID_TOKEN"
```

Disconnecting leaves your offers on Amazon, but Fluid stops syncing products and importing orders until you connect again. Remove the listings first if you want the offers gone.

## API reference

* [Start the Amazon Seller Central consent flow](https://docs.fluid.app/api-reference/amazon/start-the-amazon-seller-central-consent-flow.md)
* [Get the company's Amazon connection](https://docs.fluid.app/api-reference/amazon/get-the-companys-amazon-connection.md)
* [Select the connection's Amazon marketplace](https://docs.fluid.app/api-reference/amazon/select-the-connections-amazon-marketplace.md)
* [Publish Fluid products as Amazon offers](https://docs.fluid.app/api-reference/amazon/publish-fluid-products-as-amazon-offers.md)
* [List the company's Amazon orders](https://docs.fluid.app/api-reference/amazon/list-the-companys-amazon-orders.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.