REST API
A REST API on every product.
Automate the whole chain. Control streams, channels, outputs and layouts over HTTP. No proprietary control protocol, no middleware.
← Back to devicesHow it works
Every device serves a REST API and a live OpenAPI (Swagger) specification at /docs. Your broadcast automation, NOC or provisioning system talks to it directly. The endpoints differ per product, but the shape is the same across the line.
Example endpoints
A selection from the encoder, IPTV server and set-top box APIs.
Streams and encoding
| GET /api/streams | List all streams and their state. |
| POST /api/streams | Create a stream from a source and output profile. |
| PUT /api/streams/{id} | Update bitrate, codec or destination. |
| POST /api/streams/{id}/start | Start or stop a single stream. |
| GET /api/streams/{id}/thumbnail | Fetch a live thumbnail for monitoring. |
System and health
| GET /api/health | Real-time system state for monitoring. |
| GET /api/gpus | GPU load and encoder capacity. |
| GET /api/status | Service and stream status snapshot. |
IPTV and playout
| GET /api/channels | Channel line-up, add, edit and group. |
| GET /api/playlist | M3U playlist for players and set-top boxes. |
| GET /api/stbs | Provisioned set-top boxes. |
| PUT /api/outputs/{id} | Assign streams to an HDMI output. |
| PUT /api/layout | Full-screen or quad-split layout per output. |
Security
LAN-only by design
No internet-facing management ports. Isolate the API on a dedicated management VLAN.
SSH, key-based
Operator access over SSH with key-based authentication only.
Live OpenAPI
The full, current spec is on every device at /docs. It never drifts from the firmware.