Choose a Camera Control Protocol
PTZOptics cameras can be controlled with either the HTTP API or VISCA. Choose the protocol that fits the controller or application you are building, then use the linked guide for the command details.
| Use case | Start here |
|---|---|
| Web requests, browser automations, and integrations that can send camera CGI URLs | HTTP API getting started |
| TCP, UDP, or serial controllers that send VISCA command bytes | VISCA getting started |
| A working Python, Node.js, or C# starting point | Code examples |
| A specific camera setting or command | HTTP API reference or VISCA reference |
HTTP API
The HTTP API uses camera CGI paths and query parameters. It is a good fit when the integration can make HTTP requests and needs commands such as movement, presets, image settings, streaming configuration, or queries. The reference documents the command sent to the camera; it is not a conventional REST API.
Start with HTTP API getting started before using an individual endpoint.
VISCA
VISCA uses command bytes terminated with FF. It is a good fit for serial control and network socket integrations. Network configurations commonly use TCP port 5678 or UDP port 1259; confirm the protocol and port configured on the camera before connecting.
Start with VISCA getting started before sending a command.
Need camera setup information?
Protocol documentation explains how to send commands. For camera networking, controller, or serial-connection setup, use the applicable product documentation first. For example, Move 4K control options describes external-control connections and controller setup.