API reference
The app serves a plain HTTP API on the port chosen at launch. Paths below are
extracted from the server's own route definitions, so they cannot drift from
what the app actually serves.
Driving a tally from another tool
This is the one most people want. Every input answers three URLs, with no
request body, so anything that can fire an HTTP request can drive a tally
light — Stream Deck, Companion, QLab, a cron job:
GET or POST http://<this-machine>:<port>/api/inputs/<id>/state/on
GET or POST http://<this-machine>:<port>/api/inputs/<id>/state/off
GET or POST http://<this-machine>:<port>/api/inputs/<id>/state/toggle
The dashboard shows the exact URLs, ready to copy, in a virtual input's
editor. These keep working from another machine even when the sign-in gate
is on, because external tools generally cannot hold a session — see
Webhooks below.
Health no sign-in required
Liveness, radio-mesh state, database status and the machine's LAN addresses.
Authentication no sign-in required
The optional sign-in gate. Off by default; the machine running the app is always trusted.
Webhooks no sign-in required
Drive any input from an external tool. No body needed, so anything that can fire an HTTP request works.
Devices sign-in required when the gate is on
Inputs, outputs and wiring sign-in required when the gate is on
Coordinator and radio network sign-in required when the gate is on
Firmware this machine only
Guided USB flashing. Refused outright for non-loopback callers -- flashing a board plugged into someone else's machine is never wanted.
System, backup and metrics sign-in required when the gate is on