Create a Verkada Helix event tied to a specific camera and timestamp to enrich video footage with custom business data.
domain: apidocs.verkada.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate a Verkada Public API key with Helix permissions enabled
Exchange the API key for a short-lived access token at the Verkada token endpoint
Call POST /cameras/v1/video_tagging/event with camera_id, event_type_uid, and time_ms (epoch milliseconds) to create the event
Optionally include an attributes object and a flagged boolean to mark the event for review
Check Verkada Command to confirm the event now appears tagged on the corresponding camera's timeline
Known gotchas
time_ms must be a valid epoch-millisecond timestamp within the camera's retention window or the event will not attach to footage
event_type_uid values must be pre-registered for your Helix integration before they can be used
Helix permissions are a separate grant from general camera-read permissions on the API key
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?