Print to their printer, from your server

Embed label printing in your product. One API call reaches your user's local printer: no drivers, no dialogs, no agent to build.

Build it yourself

Months writing and maintaining a cross-platform print agent just so your app can reach a thermal printer.

Use PaperReady

It's built, and already on your users' machines. Call the API; the label prints. A cent each.

# render a saved design and print it, straight from your server curl https://paperready.studio/api/v1/print \ -H "Authorization: Bearer pr_live_…" \ -d '{"printer":"Zebra ZD421","template":"Shipping 4x6","data":{"name":"Ada Lovelace","sku":"SKU-42"}}' → 202 { "id":"…", "status":"queued", "billed":false }

Browsers can't print silently to a thermal printer. Every platform that needs it (a WMS, OMS, POS, or Shopify app) ends up rebuilding the same fragile agent. You don't have to.

Two ways to build

Local API: free, client-side
Your web page talks to the Print Bridge on the user's machine over a secure loopback connection (local.paperready.studio → 127.0.0.1 with a real cert). List printers, send a document or raw ZPL. Nothing leaves the machine. Local API reference →
Cloud API: server-to-server
Print from your backend to your users' local printers over our relay, metered at $0.01 per delivered print. Reach for this when the print trigger lives on your servers, not the browser. Cloud print API →

What the cloud API gives you

Render or pass through
POST a saved design plus data and we render it server-side to the printer's exact size, or send raw ZPL/EPL straight through. Bulk mail-merge in a single call.
Webhooks on every job
Signed webhooks fire on queued, printed, failed and expired, so your app learns the outcome without polling.
Safe retries
Idempotency keys mean a retried request never double-prints, which matters when a job crosses the network.
SDKs, OpenAPI & a playground
Zero-dependency JavaScript and Python SDKs, a full OpenAPI spec, and a live “try it” panel in the console.
Multi-tenant sub-accounts
Give each of your customers an isolated workspace and Print Bridge; all usage rolls up to your single bill. Built for platforms.

Your first print in three steps

Create an API key. Sign in with your email (no password, a one-time link that also creates your account), then open the developer console and add a key under Keys.
Pair a Print Bridge. Install the Print Bridge on the machine with the printer and pair it to your workspace with a code from the console.
Call /api/v1/print. Send a saved design + data (or raw ZPL). The job is delivered to the paired Bridge and printed. You're billed $0.01 only when it actually prints.

Print from your server, today.

Open the developer console

Free · sign in with email · no card, no commitment

Local vs cloud

	Local API	Cloud API
Print trigger	Browser / client-side	Your server
Reaches the printer via	Loopback on the user's machine	Cloud relay → user's agent
Auth	Same-origin, per-machine	API key
Server-side render & webhooks	No	Yes
Pricing	Free	$0.01 / delivered print
Status	Available now	Available now

Pricing

End-user plans never meter prints. That's a promise to shippers. The cloud API is the one place metering makes sense: $0.01 per delivered print, no monthly minimum, only for jobs that actually print (an offline printer that expires is free). One platform integration can cover thousands of endpoints. Email us before you go high-volume and we'll make sure you're set up.

Open the developer console Cloud API OpenAPI spec

Free · sign in with email · no card, no commitment

Questions

Can I print to a local printer from a website today?

Yes. The local API is live. Your page talks to the Print Bridge over a secure loopback connection and prints at true size. It's the same mechanism the PaperReady app uses. See the local API reference.

How is the cloud API different from PrintNode?

Same job (a hosted API that prints to remote local printers), but PaperReady is brand-agnostic, prints at true size by default, renders your saved designs server-side, and comes with an end-user app your customers may already run. Pricing is per delivered print on the developer tier only; end-user plans are never metered.

Do you have SDKs and webhooks?

Yes: zero-dependency JavaScript and Python SDKs, signed webhooks on every job (queued / printed / failed / expired), idempotency keys for safe retries, and a full OpenAPI spec with a try-it playground in the console.

Can I build a multi-tenant platform on it?

Yes. Sub-accounts let you give each of your customers an isolated workspace and Print Bridge; usage rolls up to your single bill. It's designed for embedding printing across many tenants.

What does it cost?

$0.01 per delivered print, no monthly minimum. Only delivered prints bill: a job to an offline printer that expires is free. There's no formal SLA yet, so email us before you build at high volume and we'll make sure you're set up.