Local HTTP control API (advanced)

For integrators, each screen can expose a local HTTP API so other systems on the same network can control it and read its status directly — without going through the cloud. This is optional and off by default.

Enabling it

Turn on the HTTP service in device settings and set its port (and credentials). It becomes reachable on the local network at that port. See All settings reference → On-device services. It can also optionally serve downloads (used by peer-to-peer downloads) and serve firmware files.

What it offers

• Read endpoints (GET): /status, /state, /info, /schedule, /system_usage, /timers, /server_config — for monitoring and dashboards.

• Action endpoints (POST /action/<name>): the same commands listed in All remote commands (reference) (playlist, download, stop, next, volume, display on/off, reboot, backlight, rotation, firmware, etc.).

Requests are authenticated with the service's username/password — change the defaults if you enable it.

Health endpoint (no auth, localhost only)

There's also a lightweight health service (default port 3050) that returns /status without authentication, but only from localhost (127.0.0.1) — for on-device monitoring scripts. It can't be reached from other machines.

When to use it

• Tie a screen into building automation, show control, or a custom dashboard on the LAN.

• Local, internet-independent control and monitoring.

Most users never need this — the manage app and the assistant cover normal control. Use the local API for bespoke on-site integrations, set up with impressBox. Don't expose it beyond your trusted network, and always change the default credentials.