All six documented commerce events are published to this single channel. Authentication is the public per-brand Pixel ID supplied at init; there is no secret credential.
Invoked from the storefront via window.fermat({ method: "track", ... }).
Messages
page_view
Fired on every page load. SPAs must re-fire on route change.
Content-Type:
view_product
Fired when a user views a product detail page.
Content-Type:
add_to_cart
Fired when a user adds a product to their cart. Quantity required.
Content-Type:
remove_from_cart
Fired when a user removes a product from their cart. Quantity required.
Content-Type:
begin_checkout
Fired when the user starts the checkout process.
Content-Type:
purchase
Fired when the purchase completes (order confirmation / thank-you page).
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.