Authenticate to the Avigilon Alta (formerly Openpath) access control API and list an organization's users
domain: docs.avigilon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm you are integrating with Avigilon Alta / Openpath access control (api.openpath.com, access.alta.avigilon.com) and not the unrelated 'OpenPath, Inc.' payments company (openpath.io) — the names collide in search results
Authenticate using the organization's Alta account: an Organization ID plus an admin email and password against the Alta Access portal, which returns a session token for subsequent calls
Ensure the admin account used is Alta-native (not federated via SSO) and does not have MFA enforced, since both currently block this login flow
Use the session token to call the users endpoint scoped to the organization to list or manage users and their assigned credential types (mobile, card, etc.)
Consult docs.avigilon.com's API Authentication and Getting Started pages for the current exact request/response shape — full detail requires a partner login
Known gotchas
This is not a static API-key/secret model — it is a session login flow tied to an admin's actual portal credentials
Full endpoint-level reference documentation is gated behind an Avigilon/Motorola partner login; treat any third-party-sourced path names as indicative, not guaranteed exact
SSO-enabled or MFA-enforced admin accounts cannot be used to obtain an API session with this flow
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?