Access the Eagle Eye Video API, made available through Brivo following its merger with Eagle Eye Networks, to list cameras and retrieve footage-related data.
domain: apidocs.brivo.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm your Brivo organization has video/Eagle Eye access enabled following the Brivo-Eagle Eye Networks merger
Review the Video API reference section at apidocs.brivo.com, which is separate from the Access API reference and credentials
Authenticate to the Eagle Eye Video API surface using the credentials and token flow documented for that product
Call the camera listing and camera health endpoints to confirm connectivity to your video devices
Query recordings or live-view endpoints for a specific camera and time range
Known gotchas
The Video API is a distinct product and credential space from the Brivo Access API - an Access API key will not authenticate against it
Exact endpoint paths and payload schemas were still being consolidated into Brivo's docs shortly after the merger, so verify current paths against the live reference before building
Video analytics and event availability depend on the camera model and subscription tier
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?