Limits: how much you can print through the APIHome & Business
20 API actions a month on Home and unlimited on Business, 60 jobs a minute, a fair-use notice that never blocks, and no per-job charge.
Home: 20 API actions a month. Business: unlimited.
- Home includes 20 API actions a month, enough to connect an app and try it properly.
- An action is a call that does something: sending a print job, adding a household, emailing a batch, or changing what's loaded.
- Reading is free. Listing printers and checking whether a job printed never count, so polling a job's status doesn't burn the month.
- The print bridge never counts.
- A refused or failed call doesn't use one up.
- The month is your own calendar month, and the allowance comes back on the 1st.
- When Home's actions are used up, a call that would count gets
429with"code": "api_quota", thelimit, how many wereused, andresetsAt. Reading still works. - Business is unlimited. Printing through the API isn't counted against a quota or billed per job. Queueing a job costs Laberty a tiny fraction of a cent, so a meter would cost more to run and explain than it could ever recover.
GET /api/agent/status shows the numbers: "apiActionsPerMonth" (20 on Home, null for unlimited) and "apiActionsThisMonth".
The guards that do exist
They're there to catch a runaway loop in someone's code, not to ration a busy shop.
| Guard | Value | What happens |
|---|---|---|
| Rate limit | 60 print jobs a minute per account | 429, with Retry-After: 60. Every job queued in the account in the last minute counts |
| Fair use | 10,000 jobs a month per account | Nothing is blocked. The Laberty team gets one notification, so an unusual integration gets noticed |
| Payload size | About 1 MB | 413. A label is a few KB |
| Copies | 1 to 50 per job | Values outside that are clamped, not refused |
| Printers | 1 on Free, 2 on Home, unlimited on Business | Checked when a printer is added. There's a ceiling of 50 as a typo-catcher |
| API actions | 20 a month on Home, unlimited on Business | 429 with "code": "api_quota". Reads and bridge calls don't count |
| API keys | 3 on Home, unlimited on Business | Checked when a key is made. Revoked keys don't count. A ceiling of 200 catches a runaway script |
Reading isn't rate limited or counted. Only calls that do something are.
Live numbers for your app
"limits": { "jobsPerMinute": 60, "fairUseJobsPerMonth": 10000, "jobsThisMonth": 214, "apiActionsPerMonth": 20, "apiActionsThisMonth": 12, "metered": false }That's part of GET /api/agent/status, so your app can show the month's count if it wants to.
Polling politely
- Check a job's status once every second or two at most. The bridge only looks for work every five seconds.
- Stop after a minute or so, and tell the user the printer hasn't picked the job up.
How long jobs are kept
- A finished job's content (the label or receipt itself) is deleted after 7 days.
- The job record is deleted after 30 days.
- Queued and claimed jobs are never deleted, however old. A stuck job is something to look at.
If you need a record for longer than a month, keep one in your own app.
Still stuck?
Contact support and tell us what you tried. We reply by email, usually within 1–2 business days.