Retrieve Verkada camera-based occupancy trend analytics for a location over a specified time interval.
domain: apidocs.verkada.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm Occupancy Trends is enabled for the target camera in Verkada Command
Authenticate and obtain an access token via the Verkada token endpoint
Call GET /cameras/v1/analytics/occupancy_trends with camera_id, start_time and end_time in unix seconds, and an interval such as 15_minutes, 1_hour, or 1_day
Set the type parameter to person or vehicle, or supply a preset_id to use a predefined detection zone
Aggregate the returned counts to build a utilization or occupancy report
Known gotchas
The endpoint returns no data if Occupancy Trends has not been explicitly enabled on that camera beforehand
Supplying a preset_id overrides the type parameter, so the two should not be treated as independent filters
Large time ranges at fine intervals can return sizeable payloads, so request long historical pulls in chunks
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?