API reference

Rackrew's public API is a first-class part of the product, not an afterthought — the same decorators that build the dashboard's own screens generate the OpenAPI spec, so the docs can never drift from what the API actually does.

Full interactive reference: api.rackrew.com/docs

Authentication

Create a key under Developers → API keys. Keys are shown once at creation (rk_live_...) and carry explicit scopes (read, write) — only the hash is stored server-side.

Use a separate key per system that calls Rackrew, so revoking one never breaks the others. How many you can hold at once depends on your plan — one on Free, three on Farm, unlimited on Workshop — and revoking a key frees its slot straight away. See pricing.

curl https://api.rackrew.com/v1/printers \
  -H "Authorization: Bearer rk_live_..."

Webhooks

Subscribe to job and printer events under Developers → Webhooks. Deliveries are HMAC-signed and retried on failure — verify the signature the same way you'd verify a Stripe webhook.

Endpoints have their own per-plan allowance, separate from API keys: one on Free, three on Farm, unlimited on Workshop. Deleting an endpoint frees its slot.

Common uses

• Push jobs into the queue from your own ERP or order system
• React to job.completed to update inventory or notify a customer
• Pull fleet status into an external dashboard