EXTERNAL PROTOCOL
WATCHOUT offers two distinct protocols that allow external applications to control and monitor your WATCHOUT shows:
- HTTP Protocol - Modern REST-based API (recommended)For detailed documentation and examples of the HTTP protocol.
- TCP/UDP Protocol - Deprecated legacy protocol for backward compatibility Both protocols enable integration with other systems, custom control interfaces, and show automation.
HTTP Protocol Overview
The modern HTTP protocol provides RESTful endpoints to:
- Control playback (play, pause, stop)
- Navigate timelines (jump to specific times or cues)
- Load shows
- Get status information
- Manipulate cue sets
- Send inputs to variables
- Receive event streams for real-time monitoring
All requests use standard HTTP methods (GET, POST) with either JSON or plain text payloads.
Legacy TCP/UDP Protocol
The older protocol uses plain text commands sent over TCP or UDP connections. While still supported for backward compatibility, we recommend using the HTTP protocol for new integrations.
Security Considerations
Neither protocol includes authentication by default. When exposing WATCHOUT control to external networks, consider:
- Using a firewall to restrict access
- Implementing a proxy with authentication
- Keeping your WATCHOUT system on a protected network