POST requests sent to your registered endpoint whenever something relevant happens. You subscribe to the events you care about and act on them however your integration requires.
Channel events
Channel events notify your system when the sales channel catalog changes. Use them to keep your local channel mapping in sync — channel IDs are required when injecting orders and when processing publication events.channel.updated
A channel was created or its configuration changed.
channel.deleted
A channel was removed from Fire.
channels.sync
Bulk sync — full channel catalog in batches of up to 50.
Store events
Store events notify your system when store configurations change. Fire supports single-store updates, explicit deletions, and bulk syncs for onboarding or mass changes.store.updated
A store was created or its configuration changed.
store.deleted
A store was removed from Fire.
stores.sync
Bulk sync — up to 50 stores per batch.
Menu events
Menu events carry the full catalog definition for a specific store and channel — categories, products, modifier groups, and schedules. The payload is ready to be forwarded to downstream systems.menu.updated
A menu was created or updated. Also used to signal menu removal (empty payload).
menus.sync
Bulk sync — menus for multiple stores in batches of up to 50.
Product events
product.updated
One or more products were updated across all stores where they appear.
product.price_updated
A price changed for one or more products, scoped to the affected stores and channels.
product.availability_changed
A product was activated or deactivated in one or more stores.
Order events
order.status_changed
An order’s status changed inside Fire.
Event envelope
Every event carries these fields underevent:
Some events also carry
event.timezone (the originating account’s timezone) in
addition to the fields above. Check each event’s own reference page for its exact
envelope before relying on a field not listed here.Delivery
Fire posts each event asapplication/json to the endpoint you configure per
integration from the dashboard (Aggregators → Developer tools → Aggregator
integrations) — you provide the host, and the path is configurable per integration,
for example https://yourapp.com/webhooks/menu-updated. Delivery is signed with
HMAC-SHA256 (see Authentication); there’s no OAuth handshake on
this path, unlike the API’s Bearer token flow.
Request headers
Deduplication
Use theevent.id field to detect and discard duplicate deliveries. Fire may deliver the same event more than once in case of retries.
Responding
Return any2xx within 10 seconds to acknowledge receipt. Process asynchronously to avoid timeouts.