Start here
The fastest path is the quickstart: create an API key, install the agent on a machine that can already print, and POST a label. Everything else on this page is reference material you can come back to.
The mental model
There are three things: your backend, RocketPrint, and an agent running next to your printers. Your backend makes one authenticated request naming a printer. We persist the job, find the station that owns that printer, and dispatch the job down a connection the station opened outward. The agent prints it and reports back what happened.
You never address a printer by hostname or IP, and nothing connects inward to your network. Routing is a field in your request — which means choosing where something prints is 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 organization API key in the X-API-Key header. Keys are created in the console, shown once, and stored only as a hash.
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. - Job status is polled today. Webhooks are on the roadmap.
