Start here
The fastest path is the quickstart: create an API key, install RocketPrint Station on a computer that can already print, and send a label. Everything else here is reference material you can come back to.
How it fits together
There are three things: your backend, RocketPrint, and the Station app running next to your printers. Your backend makes one authenticated request naming a printer. We save the job, find the computer that printer is attached to, and send the job down the connection that computer already opened to us. The app prints it and reports back what happened.
You never address a printer by hostname or IP, and nothing connects in to your network. Choosing where something prints is one field in your request — an ordinary decision in your own code.
Base URL and authentication
The public API lives at https://rocketprint.io/api. Authenticate every request with an account API key in the X-API-Key header. You create keys in your account. Each one is shown once, and we only ever store a scrambled version.
Full details are in the API reference, and the security model behind them is on the security page.
Conventions
- All requests and responses are JSON.
- IDs are opaque strings. Store them; do not parse them.
- Timestamps are RFC 3339 in UTC.
- Send an
Idempotency-Keyon every job creation. It costs nothing and prevents duplicate prints. - Today you ask us for job status. Webhooks are coming.
