Skip to main content

​
Fire

Fire is the restaurant management OS and the source of truth for all restaurant data: stores, menus, products, and sales channels. Any change made in Fire is the authoritative version that must be propagated to downstream systems.

​
Your system

Your system is the integration you build. It connects to Fire by:
  • Receiving webhook events and acting on them (publishing to aggregators, syncing a POS, triggering internal workflows, etc.)
  • Injecting orders into Fire when needed
The integration interface is the same regardless of what your system does with the data.

​
Sales channels

Sales channels are the aggregators (Uber Eats, Rappi, iFood, etc.) configured inside Fire for a given store. Each channel has a unique ID within Fire. If your system needs to publish menus to aggregators or inject orders, it must fetch the channel list and map Fire channel IDs to the corresponding aggregator identifiers.

​
Webhooks

Webhooks are HTTP POST requests that Fire sends to your registered endpoint when an event occurs. Fire emits webhook events for:
  • Store updates — a store’s information changed and must be re-published
  • Menu updates — a menu was updated and must be re-published to one or more channels
  • Product updates — a product was updated and must be re-published
  • Order status changes — the status of an order changed inside Fire
Each event payload is self-contained — it includes all the data your system needs to act without additional API calls.

​
Orders

Orders are injected into Fire via the API. Each order payload must include the Fire sales channel ID so that Fire can associate it with the correct aggregator and restaurant configuration.

​
Webhook endpoint

The HTTPS URL on your side that receives Fire webhook events. You register it in the Fire dashboard under Settings → Endpoints.