# Fire Docs

## Docs

- [Aggregator order status](https://docs.fire.rest/en/api-reference/aggregator-order-status.md): Inbound endpoint your delivery aggregator (Rappi / Uber / Didi / iFood …) POSTs to as it moves an order through its delivery lifecycle. Fire mirrors the status onto the order and logs the event. Status is passthrough — the aggregator's own labels, stored verbatim.
- [Cancel order](https://docs.fire.rest/en/api-reference/cancel-order.md): Cancel an aggregator order and, when supported by the payment processor, refund the payment.
- [Expected cash](https://docs.fire.rest/en/api-reference/cash-expected.md): Compute the system-expected cash position for a store/business day, broken down by currency, payment method, channel, operator, and device. Use it as the source of truth before recording a reconciliation.
- [Cash reconciliations](https://docs.fire.rest/en/api-reference/cash-reconciliations.md): Record a cash count from your operator/cashier and let Fire compute the discrepancy against the system-tracked cash. Also returns past reconciliations via GET.
- [Channels config](https://docs.fire.rest/en/api-reference/channels-config.md): Read the active sales-channel configuration (with fulfillment types) for the vendor bound to your API key. Use it to know which channels and fulfillment combinations your integration can use.
- [Fiscal callback](https://docs.fire.rest/en/api-reference/fiscal-callback.md): Inbound endpoint your fiscal provider POSTs to when a fiscal document changes state. Multi-country (BR, CO, EC, CL, AR, VE). Updates the order's fiscal state inside Fire and — for Brazil — triggers downstream order events.
- [Fiscal print data](https://docs.fire.rest/en/api-reference/fiscal-print.md): Retrieve the printable fiscal data for an order — emitter, store, buyer, document references, and country-specific fields. Use it to render a receipt or invoice from the integration side.
- [API reference](https://docs.fire.rest/en/api-reference/introduction.md): Fire REST API reference — inject orders and query your integration configuration.
- [KDS order status](https://docs.fire.rest/en/api-reference/kds-order-status.md): Inbound endpoint your KDS POSTs to when a kitchen order changes state (preparing, ready, dispatched). Fire logs the event, deduplicates it, and enforces anti-regression so the order state never moves backwards.
- [Login](https://docs.fire.rest/en/api-reference/login.md): Exchange your client credentials for an access token. Use the returned token as a Bearer token in all subsequent API requests.
- [Inject order](https://docs.fire.rest/en/api-reference/orders.md): Inject an order into Fire. Fire manages the order lifecycle and sends status updates back via webhooks.
- [Payment methods config](https://docs.fire.rest/en/api-reference/payment-methods-config.md): Read the configured payment methods (enabled and disabled) for the vendor bound to your API key. Use it to know which payment methods your integration can offer.
- [Authentication](https://docs.fire.rest/en/authentication.md): How to authenticate requests to the Fire API and verify incoming webhook events.
- [Changelog](https://docs.fire.rest/en/changelog.md): Recent documentation and API reference updates.
- [Aggregator integrations](https://docs.fire.rest/en/configuration/backoffice-integrations.md): Configure B2B aggregator integrations in the Fire dashboard: webhook endpoints, outbound delivery, and test events.
- [Delivery & retries](https://docs.fire.rest/en/events/delivery.md): How Fire delivers events to your endpoint — timeouts, retries, dead-letter, idempotency, and authentication.
- [Integration Flows](https://docs.fire.rest/en/events/integration-flows.md): How your system subscribes to Fire events. You configure flows in the dashboard, and a flow's HTTP node owns the request that hits your endpoint.
- [order.cancelled](https://docs.fire.rest/en/events/order-cancelled.md): An injected order has been cancelled. Carries the full V4 snapshot plus a cancellation audit block with who, when, why, and the original fiscal context.
- [order.completed](https://docs.fire.rest/en/events/order-completed.md): An injected order has been fully received and paid. The most common Fire event — carries the full V4 order snapshot and the store's fiscal configuration.
- [order.invoiced](https://docs.fire.rest/en/events/order-invoiced.md): The fiscal authority has authorized the document (electronic invoice) for an order via your fiscal provider — all countries.
- [order.reversed](https://docs.fire.rest/en/events/order-reversed.md): The fiscal authority has confirmed the cancellation (reversal) of a previously authorized document via your fiscal provider — all countries.
- [order.status_updated](https://docs.fire.rest/en/events/order-status-updated.md): An order's kitchen status advanced — the KDS reported preparing, ready or dispatched.
- [Events overview](https://docs.fire.rest/en/events/overview.md): Fire is event-driven. When something meaningful happens inside Fire, an event is delivered to your endpoint via Integration Flows you configure in the dashboard.
- [store.business_day_closed](https://docs.fire.rest/en/events/store-day-closed.md): A store closed its business day — a thin event with the close identity, timing, who closed it, and a minimal store ref.
- [Handle order events](https://docs.fire.rest/en/guides/handle-order-events.md): Build a webhook endpoint that receives order.completed and order.cancelled from Fire — from zero to first event in 10 minutes.
- [Menu publication](https://docs.fire.rest/en/guides/menu-publication.md): Handle menu events from Fire: updates and bulk syncs.
- [Order injection](https://docs.fire.rest/en/guides/order-injection.md): Inject orders into Fire via the API.
- [Order status notifications](https://docs.fire.rest/en/guides/order-status.md): Receive order status updates from Fire.
- [Product publication](https://docs.fire.rest/en/guides/product-publication.md): Handle product update events from Fire.
- [Store publication](https://docs.fire.rest/en/guides/store-publication.md): Handle store events from Fire: updates, deletions, and bulk syncs.
- [Introduction](https://docs.fire.rest/en/introduction.md): Learn how to integrate with Fire, the restaurant management OS.
- [Key concepts](https://docs.fire.rest/en/key-concepts.md): Core building blocks you need to understand before integrating with Fire.
- [Windows installation](https://docs.fire.rest/en/manuals/fire-agent/installation.md): Install and uninstall Fire Agent on Windows 10/11 so the POS can print to local thermal printers.
- [Agent web tools](https://docs.fire.rest/en/manuals/fire-agent/web-tools.md): Use Fire Agent's built-in web pages to check status and run print tests.
- [Linking](https://docs.fire.rest/en/manuals/kiosk/linking.md): How to link a kiosk to a store from the Fire backoffice.
- [Authorization codes](https://docs.fire.rest/en/manuals/pos/authorization-codes.md): How manager authorization codes work in FIRE POS V2.
- [Cancellations](https://docs.fire.rest/en/manuals/pos/cancellations.md): How a cashier cancels an approved order from FIRE POS V2 with manager authorization.
- [Cashiers](https://docs.fire.rest/en/manuals/pos/cashiers.md): How to create cashiers for FIRE POS V2 and how they sign in at the terminal.
- [Linking](https://docs.fire.rest/en/manuals/pos/linking.md): How to link a POS terminal to a store from the Fire backoffice.
- [Quickstart](https://docs.fire.rest/en/quickstart.md): Get your Fire integration running end to end — receive events and inject orders.
- [channel.deleted](https://docs.fire.rest/en/webhook-reference/channel-deleted.md): Fired when a sales channel is removed from Fire.
- [channel.updated](https://docs.fire.rest/en/webhook-reference/channel-updated.md): Fired when a sales channel is created or updated in Fire.
- [channels.sync](https://docs.fire.rest/en/webhook-reference/channels-sync.md): Batch event that delivers the full channel catalog for an account. Used for initial sync and periodic reconciliation.
- [menu.updated](https://docs.fire.rest/en/webhook-reference/menu-updated.md): Fired when a menu is created or updated and must be propagated to downstream systems.
- [order.status_changed](https://docs.fire.rest/en/webhook-reference/order-status-changed.md): Fired when an order's status changes inside Fire.
- [Events overview](https://docs.fire.rest/en/webhook-reference/overview.md): All webhook events that Fire emits, organized by entity.
- [product.availability_changed](https://docs.fire.rest/en/webhook-reference/product-availability-changed.md): Fired when a product is activated or deactivated in one or more stores.
- [product.updated](https://docs.fire.rest/en/webhook-reference/product-updated.md): Fired when one or more products change. Targets all menus and stores where the affected products appear.
- [store.deleted](https://docs.fire.rest/en/webhook-reference/store-deleted.md): Fired when a store is removed from Fire.
- [store.updated](https://docs.fire.rest/en/webhook-reference/store-updated.md): Fired when a store is created or its configuration changes and must be propagated to downstream systems.
- [stores.sync](https://docs.fire.rest/en/webhook-reference/stores-sync.md): Fired when Fire needs to propagate a large batch of store configurations at once.

## OpenAPI Specs

- [openapi](https://docs.fire.rest/api-reference/openapi.json)