Reference · built on requestConnectorAccess control & video

Avigilon Alta

Entries, zones, users, credentials, activity, and alarm events from Avigilon Alta Access, formerly Openpath.

Request accessPricing ↗

About

Avigilon Alta Access, formerly Openpath, is a cloud access control system from Motorola Solutions. An org holds sites, zones, and entries; an ACU hub drives each entry's readers, relays, contact sensors, and request-to-exit inputs. The API at api.openpath.com exposes all of it under /orgs/{orgId}, alongside REST Hook subscriptions and Event Forwarder rules.

Through Fibric, an operator follows access activity and alarm events, checks who holds which credential, and proposes a temporary entry state, a user change, or a lockdown. Nothing changes until you approve it, and each change is recorded.

This is a reference listing. It documents what Fibric would read from Avigilon Alta and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Access activity through GET /orgs/{orgId}/reports/activity/events, filtered on uiData.time with user, entry, credential, and result
  • Alarm events through GET /orgs/{orgId}/reports/alarm/events with status, assignee, linked cameras, and notes
  • Users, groups, roles, and credentials, including credential types via GET /orgs/{orgId}/credentialTypes
  • Entries with their readers, relays, contact sensors, and REX inputs, plus ACU hardware state
  • Sites, zones, schedules, entry states, and lockdown plans
  • REST Hook events such as user.created, listed by the listHookEvents endpoint, delivered to your target URL
  • Presence bucket reports and identity provider group relations

Proposed actions

  • Target capability: propose a timed entry override through POST /orgs/{orgId}/entries/{entryId}/setTempState with an entryStateId and durationSeconds, and revert it
  • Target capability: propose creating or updating a user, group membership, or credential through the users and credentials endpoints
  • Target capability: propose triggering or reverting a lockdown plan through the cloudKey lockdown plan endpoints
  • Target capability: propose a REST Hook subscription through POST /orgs/{orgId}/subscriptions for the events you want forwarded

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Review a denied entry with context

    A denied result on the activity feed carries the user, credential type, reader, and reason. The operator gathers the last hour at that entry and proposes a note for the site lead.

    With Access Anomaly, Tailgate Review

  • Let a contractor in for one afternoon

    Given an approved work window, the operator proposes setTempState on the loading dock entry with a durationSeconds that ends at the window's close, and the revert if it is cancelled.

    With Contractor Credentials

  • Close credentials when a person leaves

    On an offboarding signal, the operator lists the person's credentials and group memberships and proposes their removal in one approval.

    With Access Offboarding

  • Triage open alarms each morning

    Unassigned alarms from the alarm events report are grouped by site and entry. The operator proposes an assignee and a note on each.

    With Alarm Triage

Requirements

  • An Avigilon Alta org and an Alta-native user account; identities synced from an identity provider cannot log in to the API
  • A role whose scopes cover what the operator touches, for example o{orgId}-site:w for entry overrides and o{orgId}-outboundWebhooks:w for hooks
  • The orgId for every request path
  • A public HTTPS endpoint to receive REST Hook or Event Forwarder posts
Authentication
A JWT from POST /auth/login with email, password, and an optional TOTP code, sent as the Authorization header value; Basic auth or a certificate-signed JWT (RS256 or ES256) are also documented.

Limits

  • Activity and alarm report calls treat limit as a suggestion and often return more rows than asked; iterate until cursors.hasNextPage is false
  • Login tokens expire at data.expiresAt and must be cached and renewed by calling /auth/login again
  • The developer docs publish no request rate limits; REST Hooks carry per-subscription rateLimitCount and rateLimitWindowSecs fields
  • Bulk permission changes should send x-op-triggers: bypass and then POST /orgs/{orgId}/triggerPermissionsChange once

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Avigilon Alta ↗

Questions and answers

How do I get events without polling?
Create a REST Hook with POST /orgs/{orgId}/subscriptions naming a hook event such as user.created and a targetUrl. Alta sends an HTTP POST when the event fires. The Rules Engine also offers an Event Forwarder that posts JSON for selected events to any HTTP listener.
Can an API call open an entry?
POST /orgs/{orgId}/entries/{entryId}/setTempState applies an entry state for durationSeconds, from 1 second to 315,360,000 seconds, and returns 204. A cloudKey token can also be generated for a specific entry and used to open it remotely.
Which accounts can authenticate?
Only Avigilon Alta-native accounts. Users synchronized from a third-party identity provider cannot log in through the API. If MFA is enabled, the login body must include an mfa object with a six-digit totpCode.
Ask about Avigilon Alta

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Avigilon Alta through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy