Home›Developers›Limits and Pricing Limits and Pricing
Labelixa plan tiers, daily quotas, per-second request limits and request-size limits.
Plan tiers
| Plan | Rate | Daily ops | Ops/request | On-premise | Support response |
|---|
| Free | 3/s | 5,000 | 50 | — | — |
| Starter | 5/s | 25,000 | 50 | — | 3 business days |
| Professional | 10/s | 100,000 | 100 | — | 1 business day |
| Business | 20/s | 250,000 | 250 | — | same business day |
| Enterprise On-Premise | 20/s | by contract | 250 | yes | same business day |
The free tier needs no key, and no plan watermarks the output. Paid plans raise the limits. Current tiers can be fetched with GET /v1/plans.
Support response is a commitment about how quickly we reply, not about how quickly an issue is resolved, and it is not an availability commitment: we publish no uptime SLA. See Terms of Service §24.5-24.6.
Quota rules
One operation is one rendered label — not the number of requests. If a single API call sends a multi-label ZPL (^PQ or consecutive ^XA...^XZ blocks), that call spends as much quota as the number of labels it produces.
The quota is daily and renews every day at 00:00 UTC. An annual customer pays upfront but the quota still renews every day.
If the remaining quota is less than the number of labels the request would produce, the request is rejected upfront — no half-work.
Unused quota does not roll over to the next day.
On the annual plan you pay 10 months for 12 (2 months free). The fee is charged upfront; the quota still renews every day and does not roll over.
When the quota runs out, requests are rejected with 429 and the X-Quota-Action header says what to do: yukselt — the only route now that add-on packs are gone.
Extra usage packs have been removed
Extra operation packs are no longer sold (30 August 2026). Once quotas became daily the packs stopped making sense: a pack would cover only a small part of one day, at a unit price many times the plan's. If the daily quota is not enough, the right answer is the next plan up — cheaper and permanent. The POST /v1/addons endpoint was not removed: it returns 410 Gone that says why and points to GET /v1/plans. A 404 would not tell an existing integration whether the address was wrong or the feature was withdrawn.
Request limits
| Limit | Value |
|---|
| Request body | at most 1 MB |
| Commands per label | at most 20,000 (document total is free; multi-label documents are unaffected) |
| Label size | at most 15 inches (width/height) |
| Print density (dpmm) | 6, 8, 12, 24 |
/v1/graphics image | at most 200 KB, 2000×2000 pixels |
| Barcode data length | at most 1000 characters |
When the quota or rate limit is exceeded, the API returns HTTP 429 and a Retry-After header.
