Remote printing API
Send a label, receipt, or document from your code, and it prints on a specific printer in a specific building. No print dialog, no firewall changes, no printer-specific code.
/v1/print-jobs1.8sThe problem
Every team that ships physical goods hits the same wall: the software knows exactly what should print, and has no reliable way to make it happen on a specific machine in a specific building.
Print dialogs need a person. A warehouse at 6am does not have someone standing there clicking Print, and a kiosk browser cannot pick between eleven printers.
Nobody is going to expose a label printer to the internet or run a VPN to every store so your backend can reach port 9100.
Rasterizing a 4×6 label through a generic driver produces soft barcodes and surprise margins. Thermal printers want their own language, untouched.
Printing with no record means support tickets that end in "try printing it again." A job needs an ID and a status you can look up.
How it works
Install RocketPrint Station on a computer next to the printers you already have. It connects out to us. Your code makes one request, and we send it to the right machine.
Install RocketPrint Station on a computer that can already print — a supported Mac or Windows computer. Approve its connection in your browser. It connects out to us, so nothing has to connect in to you.
Sign in → printers registerSend ZPL, EPL, ESC/POS, a PDF, or plain text from any backend. Name one of your printers and we deliver the job to the computer it is attached to.
POST /v1/print-jobsTrack each job from pending to printing to completed, with timestamps and a real failure reason when something goes wrong.
status: completed
RocketPrintQueue + deliverBuilt for production
Six things that decide whether a print API survives contact with a real warehouse — and what each one actually does.
Send ZPL, EPL, or ESC/POS and we pass it to the printer untouched — nothing is redrawn, rescaled, or converted into a blurry barcode. We have checked the exact bytes arriving at the printer. What you send is what prints.
A disconnected computer is not a failed order. Jobs for an offline printer wait, then print in order the moment the Station app reconnects.
How queueing worksEvery job has an ID, timestamps, and a real status. When one fails, the job tells you why — no guessing, and no asking someone to try again.
Read the state modelRetry as often as you like. A repeated request returns the original job instead of printing a second label, even if the Station app restarted in between.
See the contractEvery computer, printer, job, and usage total across all your locations in one place — so support can look instead of guess.
Tour the consoleRocketPrint Station opens the connection to us and proves who it is. No open ports, no VPN, and no printer exposed to the internet.
Read the security modelPrinters and formats
Thermal label printers get their own language, untouched. Everything else prints the normal way through that computer. The full list says exactly what we have tested and what we have not.
For thermal label and receipt printers, send the printer's own language and it arrives untouched.
RocketPrint hands the file to that computer's normal printing, using the driver it already has.
optionsThe console
Printing fails in physical ways — a computer sleeps, a printer goes offline, someone renames it. This is where your team sees that happen instead of hearing about it from a customer.
For platforms
RocketPrint is built to sit inside another product. Each customer you serve gets a workspace of their own — their printers, their API keys, their jobs — while you run all of it as one account.
A workspace's API keys reach its own printers and nothing else. Customers never see each other, and you see everything.
Jobs from every workspace count toward one shared allowance on one invoice. A new customer is a workspace, not another subscription.
Ship the Station app under your name and logo, signed and auto-updating. Your customers install your software, not ours.
Questions
No. RocketPrint Station opens the connection to us and keeps it open. Nothing on your network is reachable from the internet, and you do not need to add a firewall rule.
It means your computer's print system accepted the job and the print command succeeded. It does not mean a sensor confirmed paper came out. Paper jams and empty label rolls are invisible to every print API, including ours.
The job waits. When the Station app reconnects, everything queued for it prints automatically, in the order you sent it. Your request does not fail because someone unplugged a machine.
Yes. We pass your ZPL to the printer untouched — nothing is redrawn or rescaled. We have checked the exact bytes arriving at the printer.
Yes. Send an Idempotency-Key header, and a repeated request returns the original job instead of printing a second label. The Station app keeps its own record too, so a job it already printed is never printed again — even after a restart.
Check the download page for verified Mac and Windows installers. Windows RAW labels use the spooler directly; PDFs and text use Station’s built-in renderer. Linux distribution is not available for self-service installation yet.
About five minutes
The quickstart is one install and two curl commands. Create an account and pick Launch, Orbit, or Constellation — no sales call.