> ## 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. # Webhook Logs > See whether each webhook delivery succeeded, check the payload and your endpoint's reply, and retrigger failed events. Webhook Logs lists each webhook event Fluid has tried to deliver for your company. Use it to see whether an endpoint accepted a delivery, and to check the payload and response Fluid recorded. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **System**, select **Webhooks**. On the Webhooks screen, in the banner below the page title, click **View Webhook Logs**. Webhook Logs has no item of its own in the Settings sidebar or in Settings search. To open this screen, your role needs view access to **Developer**. On the [Roles](/help/admin/settings/roles) screen, set **Developer** to **View only**, or turn on its **View API keys and webhook endpoints** switch. To retrigger events, also turn on **Manage webhooks and API configuration**. ## What's on the screen The table has four tabs: **All**, **Success**, **Failed** and **Pending**. It opens on **All** and lists events newest first. The **Success**, **Failed** and **Pending** tabs currently show no events, so stay on **All** and use the **Status** badge to find the events you need. Each row has these columns: * **Event**: the event name, such as `order_created`. The event's unique identifier appears in small text below it. * **Object**: the type and ID of the record the event is about, such as `Order #1042` or `Cart #2210`. For orders, the number is Fluid's record ID, not the order number. * **Status**: a colored badge that shows the delivery result. * **Response Code**: the HTTP status code the endpoint returned. It shows `-` when no code was recorded. * **Created At**: the date and time Fluid logged the event, in your browser's time zone. The **Status** badge has three values: * **Success** (green): the endpoint returned `200`, `201`, `202` or `204`. * **Failed** (red): any other response code was recorded, including other `2xx` codes. * **Pending** (yellow): no response code was recorded. To narrow the list, type part of an event name, such as `order`, in the search box above the table. ### Event details To open an event, click the three-dot menu on its row, then click **View Details**. A side panel opens. Its title is **Webhook Event:** followed by the event name, and it has these sections: * **Event Details**: the event's **Identifier**, **Status**, **Response Code** and **Created At**. * **Payload**: the JSON Fluid recorded for the delivery. For its structure, see [Register and handle webhooks](/api/guides/webhooks). * **Response**: what Fluid recorded about the reply, as JSON. This is usually the status code and body the endpoint returned. It can instead show why Fluid got no reply, or why the request wasn't sent. **Payload** and **Response** appear only when Fluid recorded them. At the bottom of the panel are a **Close** button and, for events with the **Failed** status, a **Retrigger** button. ## Retrigger a failed event **Retrigger** resends the event's original data to every active webhook subscribed to that event, not only the endpoint that failed. Endpoints that already accepted the event receive it again. On the **All** tab, find an event with the red **Failed** badge. Click the three-dot menu on its row, then click **View Details**. At the bottom of the side panel, click **Retrigger**. Fluid sends the event again, but the side panel stays open and still shows **Retrigger**. Click **Close** to return to the table, where each new delivery appears as its own row at the top of the list. The original row keeps its **Failed** status. Don't click **Retrigger** again unless you mean to resend the event to every endpoint. If no new row appears, see [Retrigger didn't add a new row](#retrigger-no-new-row). ## Troubleshooting Open the event with **View Details**. The **Response Code** and **Response** show what the endpoint returned. Fix the endpoint, or the webhook's settings on the [Webhooks](/help/admin/settings/webhooks) screen, then retrigger the event. If your endpoint processed the event but returned a code other than those listed for **Success**, the event still shows as **Failed**. To avoid this, have your endpoint return `200`. For how your endpoint should respond, see [Register and handle webhooks](/api/guides/webhooks). **Pending** means Fluid recorded no response code for the delivery. This happens when your endpoint couldn't be reached or didn't reply in time, or when Fluid didn't send the request, for example because the webhook URL isn't valid, doesn't use HTTPS, or points to a private host. Open the event with **View Details**. If a **Response** section appears, it may give the reason. Fluid doesn't retry a failed delivery to your webhooks on its own. **Retrigger** isn't available for **Pending** events, so you can't resend this event from Webhook Logs. To make sure later events arrive, check that your endpoint is reachable and replies promptly. Then check the webhook's settings on the [Webhooks](/help/admin/settings/webhooks) screen. **Retrigger** shows no confirmation or error message. If no new row appears after you close the panel, check these: * A webhook for this event is still active on the [Webhooks](/help/admin/settings/webhooks) screen. * The record the event is about, such as the order, still exists. * Your role has the **Manage webhooks and API configuration** switch turned on for **Developer** on the [Roles](/help/admin/settings/roles) screen. Webhook deliveries are queued. They usually go out in near real time, but can lag 5 to 10 minutes when the queue is backed up. An event appears here when Fluid attempts the delivery. Your webhooks send an event only while they're active and subscribed to it. Check the webhook on the [Webhooks](/help/admin/settings/webhooks) screen. Make sure you're on the **All** tab. If you searched, clear the search box. Search matches event names only, so an order number or ID finds nothing. ## Related pages * [Settings](/help/admin/settings) * [Webhooks](/help/admin/settings/webhooks): create and manage the webhooks that send these events. * [Register and handle webhooks](/api/guides/webhooks): the delivery format and how your endpoint should respond. * [Roles](/help/admin/settings/roles): set the permissions this screen needs.