Model Avigilon Alta's Sites and Entries hierarchy and remotely unlock an entry
domain: docs.avigilon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Understand the data model: an organization contains Sites, and each Site contains Entries (the individual doors/access points) — 'entries' is the doorlevel object you act on
Call the 'List Entries' operation after authenticating to confirm connectivity — this is commonly used as an integration health check
Locate the specific entry to unlock by filtering the entries list for the target site
Trigger the unlock action for that entry (in the admin dashboard this is a button; the underlying API call requires the partner-gated docs for exact method/path)
Confirm the unlock event by re-listing entry state or checking the Alta activity log
Known gotchas
'Zones' are not clearly documented as a distinct object separate from Sites/Entries in public sources — don't assume a separate zones endpoint exists without verifying in the gated docs
The exact unlock endpoint path/method was not available outside Avigilon's login-gated developer docs at the time of writing
Custom entry states exist (per an 'add-entry-state' doc reference) and can affect what 'unlocked' means for a given entry
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?