Skip to main content
This page is for whoever configures print and cancel against Fire. Kitchen operators use the Fire credentials form in the backoffice; they do not pick env vars.

​
Resolution cascade

At runtime fire-kds always walks the same list:
  1. Active vendor row for the order’s vendor (backoffice Vendor ID).
  2. Account default (empty vendor).
  3. Environment variables on the fire-kds server.
Print and cancel do not share the same env fallback: The stored API key is the same row for both jobs. Print sends Authorization: Bearer. Cancel sends x-api-key.
base_url is the Fire host only (https://br.app.fire.rest). fire-kds appends the path. A URL with /v1/print is rejected in the backoffice.

​
Fiscal print call

After credentials resolve, fire-kds requests:
  • v1 — Brazil.
  • v2 — Ecuador and later (RIDE layout in fiscalRepresentation).
The partner contract is documented in Fiscal print data. Timeout defaults to 4 seconds. 400 / 401 / 403 are permanent; other failures enqueue a retry.

​
Cancel when Fire says no

Cancel uses the same cascade, then POST to the XMART cancel adapter with x-api-key. If Fire (or the adapter) returns 4xx:
  • The operator sees Fire rejected the cancellation plus the policy detail (reasonDetail, and threshold/elapsed when present).
  • The cancel job stays failed. The ticket is not marked cancelled.
  • The same input is not retried automatically.
A later successful cancel, or a bump, is what clears the ticket from the kitchen. See Screen actions for the operator copy.

​
What this is not