Skip to main content
Fire is a restaurant management OS that handles stores, menus, products, and sales channels — including web, app, kiosks, and delivery aggregators (Uber Eats, Rappi, and others). Fire

​
Integration model

Fire is the master system. Any external system that needs to react to changes in Fire — or inject orders into it — integrates through the same interface:
  • Fire emits webhook events whenever something changes (store, menu, or product updates that need to be published, or order status changes)
  • Fire receives orders injected by your system via the API
Your system subscribes to the events it cares about and acts on them however it needs to.
A common use case is an aggregator orchestrator — a system that connects Fire to multiple delivery platforms (Uber Eats, Rappi, etc.) and handles publication and order flow between them. The integration works the same way for any other type of client.

​
Data flows

Publication flow — Fire notifies your system of changes that must be propagated: 
Fire → Your system → (aggregators, POS, or any downstream system)
Order flow — your system sends orders into Fire: 
(aggregators or any source) → Your system → Fire

​
What you build

Your integration needs to:
ResponsibilityDirection
Expose an HTTPS endpoint to receive webhook eventsFire → Your system
Process publication events (store, menu, product)Fire → Your system
Inject orders into FireYour system → Fire
Handle order status updates from FireFire → Your system

​
Next steps

Key concepts

Understand the core building blocks of the Fire integration.

Authentication

Set up your API credentials.

Quickstart

Get your integration running end to end.

Webhook setup

Register your endpoint to receive Fire events.