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.
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’s 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 changed. 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.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
All events share the same top-level structure:| Field | Type | Description |
|---|---|---|
event | string | Event type identifier |
id | string | Unique event ID — use for deduplication |
created_at | string | ISO 8601 timestamp |
data | object | Event-specific payload |
Request headers
| Header | Description |
|---|---|
Content-Type | application/json |
X-Fire-Event | Event type (e.g. menu.updated) |
X-Fire-Signature | HMAC-SHA256 signature — see Authentication |
X-Fire-Delivery | Unique delivery attempt ID |
Deduplication
Use theid 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.