Home›Documentation›Labelary-compatible render endpoint

Labelary-compatible render endpoint

The render path has the same shape Labelary documents: point your existing client at a different base URL. Measured compatibility table.

The same request, a different host

The shape of the render path — including the slash after the label index — is the same. If you already have a client calling Labelary, the only change needed to try Labelixa is the base URL; body, path and headers stay where they are.

Before

curl -X POST "http://api.labelary.com/v1/printers/8dpmm/labels/4x6/0/" \
     --data-binary @label.zpl -o label.png

After

curl -X POST "https://api.labelixa.com/v1/printers/8dpmm/labels/4x6/0/" \
     --data-binary @label.zpl -o label.png

Measured compatibility

Every row below was measured against live production on 2026-09-22. The table states what Labelixa does; it makes no claim about Labelary.

What	Measured behaviour
`POST /v1/printers/{dpmm}/labels/{w}x{h}/{i}/`	200, image/png — ZPL comes from the body, no key required
Trailing slash	Optional: .../0 and .../0/ return the same image (4,921 B)
`6 \| 8 \| 12 \| 24 dpmm`	All four return 200; the same label is 4,004 / 4,921 / 7,669 / 18,156 B
`{i}` label index	Zero-based selection in a multi-label body; an out-of-range index falls back to 0 and X-Warnings says so
`Accept: application/pdf`	Returns application/pdf (same path, one header difference)
`X-Warnings`	Present when there are findings; the machine-readable form is POST /v1/diagnostics (code + severity + position)
Authentication	Anonymous use needs no key and is limited per IP (IPv6: per /64 prefix): 5,000 labels and 10,000 requests a month, 5,000 labels a day; Authorization: Bearer lbx_… spends the account's quota
`GET`	405, Allow: POST — this path accepts POST only
Label size	Inches: 4x6. A millimetre form (100x150mm) returns 422 on this path

One line changes

In most clients the base URL is a single constant. Changing that constant — in your own code or in the library you use — is enough; the part that builds the path stays untouched.

JavaScript

const BASE_URL = "https://api.labelixa.com";

Python

BASE_URL = "https://api.labelixa.com"

client.BaseAddress = new Uri("https://api.labelixa.com");

Java

String baseUrl = "https://api.labelixa.com";

Before you move a production path

Rendering engines differ in edge cases: run a handful of your own labels through both and compare the output.
Instead of parsing a header, use POST /v1/diagnostics — it returns a code, a severity and a position, so a CI step can stop on it.
EPL, TSPL and CPCL are accepted as INPUT too, so a mixed fleet needs one API.
Quotas and rate limits depend on the plan; /docs/limits is the current source.

This page is a migration guide, not a comparison. The page that puts the two services side by side: /compare/labelary-alternative