List configured Blue Iris cameras with live health status.

Each entry includes is_no_signal (true when the feed is down and Blue Iris is showing its grey "no video" placeholder -- this is different from is_online, which only means the camera isn't disabled), fps, error, and ptz_capable.

Fetch a JPEG frame from a camera.

Omit pos_ms for the current live frame. Pass pos_ms (Unix epoch milliseconds) to pull a historical frame instead -- use list_clips or list_alerts to find a timestamp of interest first (their date field is epoch seconds; multiply by 1000).

List recorded video segments for a camera, newest first.

Covers Blue Iris's full retention window for that camera (typically a few days, depending on configured storage limits -- there's no separate date-range filter on this endpoint, it returns everything currently on disk). Each entry's date (epoch seconds) and msec (segment duration) can be used with get_snapshot to pull a frame from within that segment.

List motion/AI alerts for a camera, newest first.

This is the fast path for "who/what triggered this camera and when" -- Blue Iris's own memo field carries AI recognition results when available (e.g. "Rahi:74%" for a matched face), so this often answers identity questions directly without a separate face-recognition lookup. date is epoch seconds, same convention as list_clips.

Pan/tilt/zoom a PTZ-capable camera, or jump to a saved preset.

action is one of: left, right, up, down (momentary move, held for duration_s seconds, capped at 3.0), home, zoom_in, zoom_out, stop, or goto_preset (requires preset, 0-99).

Only cameras with PTZ hardware respond -- check list_cameras' ptz_capable field first. If this Blue Iris instance has an automated pipeline that also drives a camera's PTZ (e.g. a monitoring script using a dedicated preset slot), avoid sending competing PTZ commands to that camera at the same time -- Blue Iris does not arbitrate between simultaneous PTZ sources and the result is erratic movement.