All use cases
Kitchen tickets
Every station gets only the lines it cooks.
A kitchen does not want the order. The grill wants the grill items and the bar wants the drinks, each on its own ticket, each the moment the order lands. That is one printer per station and one request per station, which is the same request with a different printer id.
What comes out
*** GRILL ***
TABLE 7
20:14
2× Burger
no onion
1× Fries
FIRE NOW
An order is sent to the kitchen.
POST /v1/printers/{id}/jobs
Content-Type: text/html
<h1>*** GRILL ***</h1>
<p>TABLE 7 · 20:14</p>
<ul><li>2× Burger<br><small>no onion</small></li><li>1× Fries</li></ul>
<p><b>FIRE NOW</b></p>
201 Created · printed in 1.4s
A printer per station
Grill, fryer, bar, pass. Register each one, then send each ticket where it belongs.
Big enough to read across a kitchen
Control the type size in the HTML, or send raw ESC/POS when you want exact control over emphasis and cuts.
Reprint without reopening the order
Jobs are addressable, so a lost ticket is one more POST.