> ## 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. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > Never use /api/company/v1 or /api/v1 paths, page/per_page params, or offset pagination — they are legacy. > 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/auth-v0.yaml covers the unversioned auth surface (/api/... paths — authentication, MFA, social auth, and token exchange); 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). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. # Create company event > Add a new event for the company with details like title, dates, venue, and optional media content. ## OpenAPI ````yaml /api-reference/webhooks-v0.yaml post /api/company/events openapi: 3.1.0 info: title: Fluid Webhooks API description: >- Webhook subscriptions, callback registrations, webhook/callback schemas, and company events. version: v0 contact: email: support@fluid.app license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.fluid.app - url: https://{company}.fluid.app description: Production server with company subdomain variables: company: default: myco description: Company subdomain security: [] tags: - name: webhooks description: >- Webhook subscriptions — create, list, update, delete, and inspect the most recent delivered event per resource. - name: webhooks-resources description: The catalog of resources (and their events) a webhook may subscribe to. - name: webhook-schemas description: >- Published JSON payload schemas for webhook events, keyed by event identifier. - name: callback-registrations description: >- Synchronous callback registrations that let a company or droplet respond to Fluid callbacks (e.g. tax, shipping). - name: callback-definitions description: The catalog of callback definitions a registration can target. - name: callback-schemas description: Request/response schemas for each callback definition. - name: company-events description: >- Company calendar events surfaced to members, with optional country-scoped notifications. paths: /api/company/events: post: tags: - company-events summary: Create company event description: >- Add a new event for the company with details like title, dates, venue, and optional media content. operationId: webhooks_v0_create_company_event requestBody: required: true content: application/json: schema: type: object required: - event description: >- Event attributes are nested under a required `event` key; omitting it returns 400. properties: event: type: object description: >- Event attributes accepted by the controller. title, description, start, end, and time_zone are required by the Event model, so an event missing any of them returns 422. properties: title: type: string description: type: string venue: type: string url: type: string user_id: type: integer company_id: type: integer start_date: type: string description: Event start date, e.g. "2026-04-01". end_date: type: string description: Event end date, e.g. "2026-04-02". start_time: type: string description: Event start time, e.g. "09:00". end_time: type: string description: Event end time, e.g. "17:00". active: type: boolean time_zone: type: string description: IANA time zone name, e.g. "UTC". send_notification: type: boolean available_countries: type: array description: ISO country codes the event is scoped to. items: type: string country_ids: type: array items: type: integer images_attributes: type: array items: type: object properties: id: type: integer image_url: type: string position: type: integer _destroy: type: boolean responses: '200': description: Event created content: application/json: schema: $ref: '#/components/schemas/WebhookCompanyEvent' '400': description: Missing required parameters (no `event` key) content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' '422': description: Validation failed (missing or invalid event attributes) content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' security: - bearer_auth: [] components: schemas: WebhookCompanyEvent: type: object properties: active: type: boolean canonical_time_zone: type: string color: type: string countries: type: array items: $ref: '#/components/schemas/JsonValue' description: type: object properties: body: type: string created_at: type: string format: date-time id: type: integer locale: type: 'null' name: type: string record_id: type: integer record_type: type: string updated_at: type: string format: date-time required: - body - created_at - id - locale - name - record_id - record_type - updated_at additionalProperties: false end: type: string format: date-time id: type: integer image_url: type: 'null' images: type: array items: $ref: '#/components/schemas/JsonValue' is_all_day: type: boolean notification_sent_at: type: 'null' send_notification: type: boolean start: type: string format: date-time status: type: 'null' time_zone: type: string title: type: string url: type: 'null' user_id: type: 'null' venue: type: 'null' required: - active - canonical_time_zone - color - countries - description - end - id - image_url - images - is_all_day - notification_sent_at - send_notification - start - status - time_zone - title - url - user_id - venue additionalProperties: false StandardErrorResponse: description: >- Common legacy error response envelope. Older endpoints may return one or more of these fields depending on the controller path. type: object properties: message: type: string error: $ref: '#/components/schemas/ErrorMessage' error_message: $ref: '#/components/schemas/ErrorMessage' errors: $ref: '#/components/schemas/ErrorBag' meta: $ref: '#/components/schemas/Meta' additionalProperties: $ref: '#/components/schemas/JsonValue' UnauthorizedResponse: type: object properties: message: type: string required: - message JsonValue: description: >- Any valid JSON value for provider, integration, theme, metadata, or other dynamic payloads whose keys are not fixed by the API contract. anyOf: - type: string - type: number - type: boolean - type: 'null' - type: array items: $ref: '#/components/schemas/JsonValue' - type: object additionalProperties: $ref: '#/components/schemas/JsonValue' ErrorMessage: description: An API error message represented as text or structured JSON. anyOf: - type: string - $ref: '#/components/schemas/ErrorBag' - type: 'null' ErrorBag: description: >- Validation errors keyed by field, a list of errors, a single error message, or null when no structured error details are available. anyOf: - type: string - type: array items: $ref: '#/components/schemas/ErrorValue' - type: object additionalProperties: $ref: '#/components/schemas/ErrorValue' - type: 'null' Meta: type: object properties: request_id: type: - string - 'null' timestamp: type: string format: date-time ErrorValue: description: A validation or API error value. anyOf: - type: string - type: array items: type: string - type: object additionalProperties: $ref: '#/components/schemas/JsonValue' securitySchemes: bearer_auth: type: http scheme: bearer description: Bearer token authentication ````