Custom integrations and working with usHome & Business

What you can build today

On Home (20 API actions a month) and Business (unlimited), these are the building blocks:

• The API. List printers and what's loaded in them. Send labels as lines of text, receipts, or your own ZPL and ESC/POS. Check whether each job printed. Read and add households, and email a batch of address labels to the member. Start with the Integration guide.
• API keys, one per app. Each app gets a key with the smallest scope it needs. Keys never expire and can be revoked one at a time. See API keys explained.
• The print bridge. One bridge on your network drives receipt printers, Zebra and other ZPL printers, and networked Brother QL printers. Your app doesn't need drivers or a container of its own. See The print bridge.
• Your own AI keys. Run Laberty's AI features on your own Anthropic or OpenAI account, and on Gemini or Grok, which are included with Business. See Bring your own AI keys.

Some things people build with these:

• A point-of-sale that prints receipts on the counter printer and order labels on a Brother QL.
• An inventory app that prints shelf labels on the 2.4 in roll, refused if the wrong roll is loaded.
• A script that adds new customers as households and emails the member a batch of address labels.

What Laberty doesn't do: run your code

Laberty doesn't accept plugins, scripts or custom code to run inside Laberty itself.

Every account runs on the same service. Code running inside it could reach other people's data, or slow the service down for everyone. Running outside code safely takes careful isolation, and doing it well would slow down everything else we build.

The API is the supported way to extend Laberty. Your code runs on your own systems. It talks to Laberty with a key you can revoke in one click, and it can only do what that key allows. If your code misbehaves, it can't take anyone else down with it.

A few things the API doesn't have today, so you can plan around them:

• No webhooks. Laberty doesn't call your app when a job finishes. Check the job's status instead (step 7 of the Integration guide).
• No per-user sign-in for apps. Apps use API keys, not a person's account.

Asking for a custom integration or a partnership

If what you need goes beyond the API, tell us. Contact support and choose A custom integration or partnership. It helps to include:

• The system you want to connect, and what it does.
• What should print, and on which printers (make and model).
• Rough volumes: jobs a day, how many printers, how many locations.
• Anything the API is missing for you.
• Your timeline.

We reply by email, usually within 1–2 business days. We can't promise to build every request. When something would help many customers, it may become part of the API for everyone.

Thinking of running Laberty yourself? That's the Founder license, which comes with no support.