Nixstasis Device API
The routes devices use to register, send heartbeats, report command results, and fetch large command payloads, plus the device list for operators and the check Caddy makes before issuing a device certificate. Heartbeats, command results, and payload fetches send the device's token as a bearer token (the deviceBearer scheme), never in the URL. Registration needs no token, because it is how a device gets one. The device list needs a signed-in operator and only shows devices they can access. The same device actions are also available as generated routes under /api/json/device_runtime/devices.
Authentication
- HTTP: Bearer Auth
- HTTP: Bearer Auth
Trusted operator bearer claims admitted by the Caddy/AuthCrunch edge.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Registration-issued device token used in the Authorization header by runtime heartbeat and command operations. Query-string credentials are rejected.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | Device token |