Waymark / Routes / apidocs.verkada.com List Classic Alarm devices for a Verkada site through the Alarms API and subscribe to alarm state-change webhooks.
domain: apidocs.verkada.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Authenticate and obtain an access token via the Verkada token endpoint Call GET /alarms/v1/devices with a required site_id and optional device_ids filter to list Classic Alarm devices Confirm whether your devices are Classic Alarm hardware, since a newer-generation Alarms API is documented separately for newer devices Configure a webhook subscription to receive the Classic Alarms Webhook Object payload fired on site state changes Optionally call the notifications/alerts endpoint to retrieve general alert history alongside the alarm state data Known gotchas The Classic Alarms endpoints explicitly do not cover newer-generation Alarm devices, which are documented under a separate current Alarms API site_id is required on the device-listing call, so requests without it will fail Webhook payload shape differs between Classic Alarms and the newer Alarms API, so verify which generation your integration targets
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