DEVELOPERS / REST API / UPDATED 17 NOV 2026
A Zebra Printer API That Works From Anywhere
A REST API for Zebra printers: send ZPL or a design with data from any server, read the job state, queue while the printer is off. Calls were run.
Production API: Pro ($24.90/month, 2,000 calls/day); a read-only sandbox is free on every plan. SDKs: npm, PyPI, Go. Printing is free and unlimited on every plan.
curl https://labelinn.com/v1/print/jobs \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-H "X-Idempotency-Key: label-10492-1" \
-d '{
"printer_id": "prt_abc123",
"payload_type": "zpl",
"payload_data": "^XA^FO50,50^A0N,40,40^FDHello from LabelInn^FS^XZ"
}'{
"data": {
"id": "job_0001",
"status": "queued",
"printer_id": "prt_abc123",
"printer_name": "Zebra ZD421 (packing bench)",
"payload_type": "zpl",
"copies": 1,
"is_test": false
}
} <- queued, not printedSHORT ANSWER
One HTTPS call prints on a Zebra anywhere: ZPL or a design with data.
A Zebra listens for ZPL on the network, and Zebra provides SDKs and printer connectivity features to build on. What you still have to build is a print service that a cloud app or ERP can call, with a queue, a job status and several sites. LabelInn is that service: the app next to the printer connects out, and your code calls POST /v1/print/jobs.
- Send raw ZPL (
payload_type: "zpl") or a design and its data ("template"). - The job waits while the printer is off and prints when it is back; read the state with
GET /v1/print/jobs/{id}. - A key that starts
sk_test_runs in a sandbox that never prints.
01 / COVERAGE
What the API covers
The calls a print integration needs, each one in the API reference.
| You need to | Call | Notes |
|---|---|---|
| Print raw ZPL | POST /v1/print/jobs with payload_type: "zpl" | payload_data up to 500 KB; copies 1 to 1000 |
| Print a visual design with your data | POST /v1/print/jobs with payload_type: "template" | design_id and data; an array of rows prints one label per row, up to 1000 |
| Print up to 100 jobs in one request | POST /v1/print/batch | Each job is accepted or refused on its own |
| Know whether it printed | GET /v1/print/jobs/{id}, or a webhook | Events such as print.job.completed and print.job.failed |
| See your printers and their state | GET /v1/fleet/printers, /v1/fleet/printers/{id}/status | Online or offline, connection type, command language |
| Know when labels or ribbon run low | GET /v1/fleet/supply-alerts | One row per low or empty supply |
| Prove what was printed | GET /v1/audit/print-history | Each print with its values |
| Avoid a double label on retry | Header X-Idempotency-Key | Same key within 24 hours returns the first job |
02 / CODE
A first call in three ways
The same ZPL job from curl, Python and Node.js, all run.
curl
curl https://labelinn.com/v1/print/jobs \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-H "X-Idempotency-Key: label-10492-1" \
-d '{
"printer_id": "prt_abc123",
"payload_type": "zpl",
"payload_data": "^XA^FO50,50^A0N,40,40^FDHello from LabelInn^FS^XZ"
}'Python
import time
from labelinn import LabelInn
client = LabelInn("sk_live_...") # Settings > API Keys
printer = next(p for p in client.fleet.list() if p["status"] == "online")
job = client.print.create(
printer_id=printer["id"],
payload_type="zpl",
payload_data=open("label.zpl", encoding="utf-8").read(),
idempotency_key="label-10492-1", # same key = same job, no second label
)
while job["status"] not in ("completed", "failed", "cancelled"):
time.sleep(2)
job = client.print.get(job["id"])
print(job["id"], job["status"])Node.js
const LabelInn = require("labelinn");
const client = new LabelInn("sk_live_..."); // Settings > API Keys
async function main() {
const printers = await client.fleet.list();
const printer = printers.find((p) => p.status === "online");
let job = await client.print.create(
{
printer_id: printer.id,
payload_type: "zpl",
payload_data: "^XA^FO50,50^A0N,40,40^FDHello from LabelInn^FS^XZ",
},
{ idempotencyKey: "label-10492-1" } // same key = same job
);
while (!["completed", "failed", "cancelled"].includes(job.status)) {
await new Promise((r) => setTimeout(r, 2000));
job = await client.print.get(job.id);
}
console.log(job.id, job.status);
}
main().catch((e) => console.error(e.status, e.code, e.message));curl 201, "status": "queued", job_0001
python job_0001 completed
node job_0001 completed03 / ZPL OR DESIGN
ZPL or a design: the same label two ways
Raw ZPL puts the layout in your code; a design keeps it in LabelInn.
{
"printer_id": "prt_abc123",
"payload_type": "zpl",
"payload_data": "^XA^CI28^PW640^LL400^FO30,30^A0N,44,44^FDOrder 10492^FS ... ^XZ"
}{
"printer_id": "prt_abc123",
"payload_type": "template",
"design_id": "dsg_shipping",
"data": { "order_id": "ORD-9876", "customer": "Maria Lopez", "barcode": "TR123456789" },
"copies": 2
}
"payload_type": "template",
"design_id": "dsg_shipping",
"copies": 2,
"total_labels": 2,
"variables_used": ["order_id", "customer", "barcode"],
"status": "queued"04 / STATES
Job states, and why a 201 is not a printed label
Printing is physical and asynchronous, so read the job.
Render and hardware errors never appear in the create response, only in the job (error_message). Poll every couple of seconds until the state is completed, failed or cancelled, or subscribe to webhooks.
A job for a printer that is off stays waitingForPrinter and prints by itself when the printer is back. After 24 hours it ends cancelled with nothing printed.
curl https://labelinn.com/v1/print/jobs/job_0001 \
-H "Authorization: Bearer sk_live_..."{ "success": true,
"data": { "id": "job_0001", "status": "completed",
"printer_id": "prt_abc123", "payload_type": "zpl",
"copies": 1, "completed_at": "2026-11-16T21:38:23.381Z",
"error_message": null } }05 / ERRORS
Errors you will meet
Codes the API source returns.
| HTTP | Code | What to do |
|---|---|---|
| 400 | INVALID_PAYLOAD_TYPE, MISSING_FIELD, PAYLOAD_TOO_LARGE, BATCH_TOO_LARGE | Fix the body. A batch is 1 to 100 jobs; payload_data is at most 500 KB. |
| 400 | PRINTER_LANGUAGE_MISMATCH | ZPL was sent to a receipt or raster-only printer (ESC/POS, Phomemo, DYMO, Brother QL). Send a design or an image instead. |
| 401 | INVALID_API_KEY | Missing or revoked key. Header: Authorization: Bearer sk_.... |
| 403 | PLAN_NO_API | The plan has no API quota. See the plan block below. |
| 404 | PRINTER_NOT_FOUND | Use an id from GET /v1/fleet/printers. |
| 409 | IDEMPOTENCY_IN_PROGRESS, IDEMPOTENCY_KEY_REUSED | Retry after Retry-After; use a new key for a different body. After a failed job use a new key too. |
| 423 | PRINTER_LOCKED | An administrator locked the printer for calibration or maintenance. |
| 429 | RATE_LIMIT_EXCEEDED, BURST_RATE_LIMIT | Wait retry_after_seconds. The limit counts requests, not labels. |
06 / SETUP
Register the Zebra once
The API prints on printers the LabelInn app has registered, with no code.
Install LabelInn on the PC the Zebra is plugged into (or on the same network). The app lists USB and network printers; a network one can also be added by IP, with 9100 as the raw port. Once it is listed it appears in GET /v1/fleet/printers with its command_language and status.
The app must be running on that PC and cloud printing switched on for the printer. The API cannot switch it on.
- Zebra GK420d, GK420t, ZD220, ZD421 and ZT231 are in the setup video.
- TSC, Toshiba, Epson and others register the same way: one request shape for all of them.

Video: connecting a Zebra to LabelInn, about one minute.
07 / TESTED
What was run for this page
Read this before you trust a snippet.
| Snippet | Run here? | Result |
|---|---|---|
| curl, Python SDK, Node.js SDK | Run with labelinn 3.1.0 (PyPI and npm) | Against a local stand-in written from functions/api/printJobs.js and docs/openapi.yaml. The calls and responses above are its output; field names match the API source. |
| Template call with data | Run against the stand-in | variables_used listed the three data keys. |
| The live service | Not called | No request went to labelinn.com and no job was created. Error codes come from the API source. |
| A physical Zebra | Not used | No printer was connected. |
08 / PLANS
What is free and what needs a plan
Try the request shapes free; printing through the API needs Pro.
FREE
$0
- Design and print labels by hand on Zebra, TSC, Toshiba and Epson printers, with no label limit
- API sandbox: a
sk_test_key, read-only, 25 calls a day (it never prints)
STARTER
$7.99 / month
- Everything in Free
- Excel and CSV data binding, workflows, automations
- API sandbox: 250 calls a day (still read-only)
PRO
$24.90 / month
- Everything in Starter
- The production API:
sk_live_keys that print, 2,000 calls a day, 60 a minute - Webhooks, watched folder, database sources
A signed-in Free user can start a 14-day trial by hand from the dashboard banner or the app’s paywall (no card): it unlocks Excel and CSV binding, bulk barcodes and the production API. It does not start by itself at signup. Yearly billing is ten months for twelve ($79.90 Starter, $249.00 Pro). All plans and limits: pricing.
QUESTIONS / FAQ
Frequently asked questions
Does Zebra have a cloud printing API?
Zebra provides SDKs and printer connectivity features that you can build a print service on. LabelInn is a ready-made REST API in front of registered printers, so an application anywhere can print to them, with a queue and a job status, across Zebra and other brands.
Can I print to a Zebra printer from a cloud server?
Yes. The LabelInn app next to the printer connects out to LabelInn; your server calls POST /v1/print/jobs and never needs network access to the printer.
How do I know if the label printed?
Read the job with GET /v1/print/jobs/{id} until its state is completed or failed, or subscribe to webhook events. A 201 only means queued.
Can I send raw ZPL?
Yes: payload_type: "zpl" and the ZPL in payload_data, up to 500 KB. The app sends it to the printer unchanged, over USB or the network. ZPL to a receipt or raster-only printer is refused with PRINTER_LANGUAGE_MISMATCH.
Is there an SDK?
Yes: official SDKs for Python (pip install labelinn), Node.js (npm install labelinn), .NET and Go, all at 3.1.0 for Python and Node.js.
Does it work with printers other than Zebra?
Yes. A design sent as a template is converted to ZPL, TSPL, TPCL or ESC/Label for the printer it is sent to, so a TSC on another site needs no code change.
Can I try it before paying?
Yes, in two ways. A sk_test_ key and the read-only sandbox are free. A signed-in Free user can start a 14-day trial by hand from the dashboard banner or the app’s paywall (no card): it unlocks Excel and CSV binding, bulk barcodes and the production API. It does not start by itself at signup.
KEEP GOING
Related
NEXT STEP / LABELINN
Give your app a Zebra printer API
Download LabelInn, register the printer once, send your first job from any server. · Free plan, no card · REST and official SDKs · Zebra, TSC, Toshiba, Epson