Print infrastructure API

Hosted print templates for platforms.

Send JSON to one endpoint. We render your template and deliver it to the thermal and label printers across your fleet. No print servers, no drivers, no byte-level command formats.

Compliance label rendered by eatabit

One schema in. A designed artifact out.

Same endpoint, same payload shape. The template decides the layout, the stock and the command set — ESC/POS, TSPL, Star or raster.

POST /v20/jobs

{
  "printerId": "f9d43179-9c10-4502-8f62-892740a65318",
  "webhook_url": "https://example.com/eatabit/webhook",
  "webhook_method": "POST",
  "orderData": {
    "patient": "Robert Alvarez",
    "product": "Sunset Kush Whole Flower",
    "weight": "3.5g",
    "batch": "SW-FLW-260614",
    "...": "..."
  }
}

→ 201 queued · TSPL · printed 2.7s
Rendered output

3×2 label · continuous roll

Typography, spacing, barcodes, logos and conditional sections live in the template — versioned by you, not assembled byte by byte in your codebase.

Device choice never blocks a rollout

Your venues have a mixed fleet. That is our problem, not yours.

Their printers

Already deployed

Supported Star CloudPRNT and Epson Server Direct Print models already sitting in the venue. Register and print — the compatibility list is on the pricing page.

Hardware from us

Configured, drop-shipped

Receipt and label devices supplied ready to run, sent straight to the venue. Nothing to set up on site.

Mixed fleets

Both, one integration

Old devices and new ones under the same schema, so a rollout never waits on hardware parity.

Built for the part you don't want to think about

Delivery through firewalls and NAT

Printers reach out to us. No inbound ports, no VPN, no on-site print server.

Status webhooks

Accepted, printed, failed, paper out — per job and per printer, back into your system.

Offline queueing and retries

A venue drops its connection, jobs hold, and they print when it returns.

One API across Star and Epson

CloudPRNT and Server Direct Print sit behind the same endpoint, so your integration never branches on the vendor.

Where it runs today

Order ticket printed in English
Order ticket printed in Chinese

Restaurants & ordering

Kitchen tickets and customer receipts, multi-station routing, duplicate copies, modifiers and item notes that reflow instead of clipping. One template, any character set the venue needs.

Florist receipt rendered by eatabit, with the store logo and a scannable order barcode

Retail & fulfillment

Labels and receipts from the same integration, on thermal or label stock, with barcodes rendered from the payload.

Dispensary patient label
Dispensary compliance label

Cannabis

Compliance labels applied at dispensing, patient labels and manifests. Required symbols and fixed legal copy live in the template, versioned per jurisdiction.

What integration looks like

01 · you own

Integrate the API

One endpoint, one auth model, one payload shape. Days, not a quarter.

02 · together

Design your templates

A one-time engagement covering the layouts, per-brand theming and any regulated copy.

03 · we own

Provisioning and delivery

Printer registration, fleet monitoring, retries and the printer command sets.

Pricing

Costs scale with your fleet, not your revenue

Buy our printers or connect the ones your venues already run. No per-venue minimums, no device-count commitment.

eatabit printer · pay once

$375

eatabit printer · pay monthly

$175 + $10/mo

Your own printer

$7/mo

Tell us what's in the field

How many venues, which printers are there today, and roughly how much you print. That's enough for a real number and a rollout plan.