For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Orders and events — clarified formats and behaviour
Order dates.createdAt and updatedAt on Managing the status of the order and Create orders in batch now state that dates must be in UTC ending in Z. Fractional seconds are accepted. Timezone offsets such as +01:00 are rejected.
Order metaInfo. Values can be strings, numbers or booleans, and RFC 3339 strings are stored as dates. The example now shows mixed value types.
Order updates. Each call is stored as a new entry for the order rather than replacing the previous one, so Get order details can return several entries with the same id. Orders sent to the single-order endpoint are processed as live data. To import past orders without triggering workflows, use the batch endpoint with historical: true.
Events.Create an event and Create events in batch store every event as a custom event, including cart_updated, cart_deleted and order_completed, so they don’t trigger ecommerce automations. To send ecommerce cart events, activate the ecommerce app and use the Brevo tracker or the trackEvent endpoint.
Guides.eCommerce tracker events now explains how cart and order events are processed depending on the endpoint, and documents the payloads for cart_updated and cart_deleted and how to record purchases. Track website activity now recommends recording purchases with the Orders API. Track custom events (REST) uses a custom event in its example instead of the reserved cart_updated name.
