Motorola Solutions and Avigilon integration interfaces
Identify the exact Avigilon platform and release. Check its interfaces, access requirements and supported media or event functions.
Sources and scopeSource record 25 August 2026
Technical source record: 25 August 2026. Check the linked documentation for current product requirements.
Public Motorola Solutions and Avigilon programme, product, release, and help material; detailed SDK/API contracts, endpoints, credentials, licences, compatibility, and partner entitlements are fragmented or gated and are not inferred.
On this page
Overview#
Vendor APIs / VMS and cloud video / Motorola Solutions and Avigilon
The current portfolio spans multiple independently versioned platforms. Unity Video, Unity Access, Alta Video, Alta Access, and other Motorola Solutions command center products don't share one universal “Avigilon API.” The official developer program page and Avigilon documentation portal are the correct starting points, but much of the detailed developer contract is programme, product or licence controlled.
Verified product separation#
| Product family | Publicly evidenced integration route | Evidence limit |
|---|---|---|
| Avigilon Unity Video | Web Endpoint API and interoperability/developer programme references | Detailed current API/SDK contract and licences were not verified publicly as one catalogue |
| Avigilon Unity Access | Product specific REST/integration and licensed partner surfaces | Public product/release docs exist; older official integration blueprints prove a REST API licence for that exact workflow only |
| Avigilon Alta Video | Cloud video integrations documented in the Avigilon help portal | Tenant/region API contract and developer entitlement must be obtained for the intended integration |
| Avigilon Alta Access | Cloud access, identity and app integrations; formerly Openpath | Public administration/integration guides exist; a general current public developer API reference was not established in this review |
| Motorola Solutions developer programmes | Avigilon and command center developer/interoperability routes | Programme acceptance, agreements, documentation and support are distinct by product |
Current documentation observations#
The Avigilon portal contained Unity Video 8.8 documentation and Unity Access 7.20 release material during the 25 August 2026 review. These observations don't establish that either is universally latest, licensed, or compatible with a given integration. The portal also retains older product documentation; always select the exact version label.
Alta Access documentation reflects the Openpath to Avigilon product transition. Record both legacy and current names only for traceability; use current product identifiers in new contracts. Alta cloud sign in and feature availability can be region and subscription specific.
Required evidence before design#
Obtain a vendor/partner statement that identifies:
- exact Unity/Alta/Motorola product and edition;
- server/cloud release, region and tenant type;
- API/SDK/package name and version;
- development, test and production licence/entitlement;
- supported operations and event/media semantics;
- identity, token/certificate and permission model;
- rate, pagination, session and retention limits;
- compatibility, deprecation, support and security advisory route.
Don't use a PDF for a named third party integration as proof of a general purpose endpoint. For example, an official 2023 integration blueprint referenced a Unity Access REST API licence and minimum product version for that blueprint; it doesn't authorise or define other workflows.
Security and physical safety boundary#
Unity and Alta surfaces can span live/recorded video, evidence, alarms, identities, credentials, doors and physical commands. Create separate principals and authorisation policies for each capability. Cloud credentials must be bound to the correct organization/region; on premises credentials must remain inside the management conduit.
For Alta identity provider integrations, current official guides document subscription dependent sync intervals and read permissions for named providers. Those application specific settings aren't a general Alta developer authentication contract. Pin the exact integration guide and permissions.
Never retry door, lockdown, alarm acknowledgement, relay, PTZ or other command blindly after timeout. Query product state and audit records or require operator reconciliation. Preserve local life safety authority and egress behaviour independently of cloud/API availability.
Events and media#
Before relying on an event integration, establish subscription durability, resume cursor, ordering, duplicate/gap behaviour, initial snapshot and retention. Before using media, establish live/playback/export distinctions, session lifetime, codec, authorisation, watermark/integrity and redistribution rights. Product UI deep links aren't media APIs or evidence exports.
Lifecycle and product identity#
technology_status: mixed reflects multiple current cloud/on premises product lines, retained older documentation, renaming and separately versioned interfaces. Recheck branding, product ownership, support and replacement paths at every review.
Primary sources#
- Motorola Solutions developer programmes, official programme entry point, including Avigilon.
- Motorola Solutions interoperability programmes, official partner/resource route.
- Avigilon documentation portal, current versioned product documentation.
- Unity Video 8.8 support and Web Endpoint API links, product specific evidence.
- Unity Access 7.20 documentation results, versioned release/product evidence.
- Alta Access Microsoft Entra integration, example of product, subscription and permission specific integration documentation.