Skip to main content
POST
Returns the end-of-day report for a store, already laid out for the paper width you ask for. Its subject is a business day, not a sale, which is why it has its own endpoint and its own path. It is the same contract as Print an order document — same paper.lines vocabulary, same template block, same freshness block. Read that page for the line types; this one only covers what is different.
The report is built from the day’s closing snapshot: totals, taxes broken down, one row per payment method, one row per channel, transactions, average ticket, peak hour, and the cancellations for the day.
This is the day close, not the cash count. Declared values, float and the cashier’s signature belong to the cash reconciliation, which is a different document with a different source — see cash reconciliations.

The day has to be closed

If the store has not closed that business day, the call fails with 409 PRINT_DAY_NOT_CLOSED. Printing a close that did not happen would be inventing it. Fire’s preview screen tolerates an open day — it draws placeholders so the template can be designed — but a register cannot.

Authentication

string
required
Your Fire API key with the printing:read scope. The key must be vendor-scoped — system-only keys are rejected with 403.
printing:read is a new scope. Existing keys do not have it — grant it in the Fire dashboard before your first call.

Path parameters

string
required
UUID of the store. Unlike the order endpoint — where the store comes with the order — here it comes from you, so Fire verifies it belongs to your key’s account and vendor before reading anything. A store outside your scope answers 403.
string
required
YYYY-MM-DD. The operational day, which is not the calendar day: a day that opens on the 2nd and closes at 3 a.m. on the 3rd is still the 2nd.

Body

object
required
number
Width of the label column, between 6 and 24.
number
1 to 5. Default 1.
number
Reprint with a specific template version. Send templateId with it.
string
Which template that version belongs to. See the reprinting note on the order endpoint.

What is different in the response

The envelope is identical. These blocks carry different values:
object
string[]
The same block as on the order endpoint, with the same codes — see its table. The template ones apply here (TEMPLATE_FELL_BACK_TO_SEED, TEMPLATE_UNREADABLE, TEMPLATE_VERSION_AMBIGUOUS); the fiscal ones never do, because a day close does not go to the tax authority.
object

Errors