One HTTP request turns ZPL into a label image. There is no printer in the loop, no driver to install and no account needed to try it — and when the renderer has to skip something, it says so in a response header instead of drawing a wrong label quietly.
Send the ZPL as the raw request body. The path carries the print density and the label size, so the same code can be checked at the resolution the target printer actually runs at.
curl -X POST "https://labelixa.com/v1/printers/8dpmm/labels/4x6/0/" \
-H "Content-Type: text/plain" \
--data-binary $'^XA\n^FO50,50^A0N,40,40^FDLabelixa^FS\n^FO50,120^BY2^BCN,80,Y,N,N^FD1234567890^FS\n^XZ' \
-o label.png -D -The body is the image. Everything the renderer noticed while drawing is in the headers, which is what makes the call usable from a script: a CI step can fail on a warning without parsing the picture.
| Header | What it tells you |
|---|---|
Content-Type | image/png by default; send Accept: application/pdf for a PDF. |
X-Warnings | Present only when the renderer skipped or could not fully draw something — an unknown command, a field outside the label. |
X-Total-Count | How many labels the submitted code produces; an index selects one of them. |
X-Plan | The plan the request was counted against — free for an anonymous call. |
X-RateLimit-Remaining | Renders left in the current window. |
An anonymous call is counted against the free plan and limited per IP. An API key moves the call onto the account's own quota.
| Plan | Requests per second | Labels per month |
|---|---|---|
| free | 3 | 5,000 |
| starter | 5 | 25,000 |
| pro | 10 | 100,000 |
| business | 20 | 500,000 |
| enterprise | 20 | by agreement |
ZPL is not the only input. EPL, TSPL and CPCL have their own render and diagnostics endpoints, with the same idea: code in, image out, findings in a structured response.
| Language | Endpoint |
|---|---|
| ZPL | /v1/printers/{dpmm}dpmm/labels/{width}x{height}/{index}/ |
| EPL | /v1/epl/render |
| TSPL | /v1/tspl/render |
| CPCL | /v1/cpcl/render |
A renderer draws what the code says on a screen. A printer adds its own firmware, resident fonts, media and calibration. Use the preview to catch the mistakes that are in the code — a field off the label, a barcode that cannot encode its data, a command the firmware will ignore — and keep a test print for the ones that are in the hardware. No online renderer, this one included, can promise pixel identity with a physical label.
Open the browser preview → Read the API reference → Connect an AI assistant (MCP) →
No. Anonymous calls work and are rate-limited per IP. An API key is what moves a call onto an account's quota, raises the limits and lets usage be attributed.
Yes — send Accept: application/pdf. The same request otherwise, the same path.
The label is still rendered and the response carries an X-Warnings header naming what was skipped. If you want the findings as JSON — with a code, a severity and a position — post the same code to the diagnostics endpoint instead.
No, and no renderer can honestly claim that. The preview shows what the code draws; the printer adds firmware, fonts, media and calibration. It catches code mistakes, not hardware ones.