LenelS2 OnGuard, OpenAccess, and Elements
Identify the exact OnGuard or Elements platform and supported interface. Check where OpenAccess applies before planning identity, event or control integration.
Sources and scopeSource record 25 August 2026
Technical source record: 25 August 2026. Check the linked documentation for current product requirements.
Public LenelS2 product, data sheet, partner certification, cloud, and portal material; current OpenAccess contract, API packages, auth, endpoint schemas, licences, DataConduIT status, and any Elements developer API are not publicly verified here.
On this page
Overview#
Vendor APIs / Access and identity / LenelS2
LenelS2’s integration story spans the on premises OnGuard platform, OnGuard Cloud, the OpenAccess Web Services API family, legacy/other data interfaces, and the distinct Elements SaaS platform. Don't infer that an OnGuard OpenAccess integration can call Elements or that the Elements OnGuard Connector is a general public API.
Documented interface map#
| Surface | Public evidence | Boundary |
|---|---|---|
| OnGuard OpenAccess Web Services | OnGuard product and data sheets identify RESTful/web service integration; OnGuard 7.5 material described parity work with DataConduIT | Full current contract and samples are delivered through LenelS2 Connect/installed product and licences |
| OpenAccess event bridge | Official partner pages show REST plus SignalR event bridge use for named certified integrations | Delivery behaviour on one partner page is not universal; use the target OpenAccess guide |
| OAAP/technology partner interfaces | Certified integrations list exact OnGuard releases, partner versions and API licence part numbers | Certification applies only to the listed combination and does not certify partner cybersecurity |
| OnGuard Cloud | Single tenant cloud deployment with web/OpenAccess integration options in official brochure | Cloud network, region, edition, licence and support contract apply |
| Elements | Cloud access/video platform with continuous delivery and an Elements to OnGuard Connector | No general current public Elements developer API contract was established in this review |
OnGuard contract#
The OnGuard 8.3 data sheet observed during review lists continuing OpenAccess Web Services API updates. This is an inherited release record. The previously cited PDF returned 404 on 29 September 2026, so obtain the release document from LenelS2 before relying on that detail. Record OnGuard server/enterprise version, OpenAccess component build, database/topology, API licence, service identity, event bridge version and every target entity class.
Public OAAP partner pages demonstrate that LenelS2 issues integration specific API licence part numbers and certifies named product/version combinations. Use that matrix for the selected partner interface. Don't treat “factory certified” as a blanket security, functionality or future compatibility warranty; LenelS2 explicitly limits the certification statement on those pages.
DataConduIT appears in older OnGuard material as a comparison/legacy integration interface. Obtain the current lifecycle and migration guidance before maintaining or replacing it. Don't start new database or COM based integration based on historical familiarity when OpenAccess is the supported route.
Elements boundary#
Official Elements material establishes a cloud access/video product, continuous delivery and the Elements OnGuard Connector for hybrid deployments. Public material doesn't establish a customer general Elements API reference with authentication, schemas, limits and lifecycle. Therefore this catalogue makes no endpoint, SDK or access claim for Elements. Obtain written LenelS2 evidence for any proposed Elements integration.
Continuous delivery means capability and behaviour can change without an on premises upgrade event. Record tenant, release/change notice channel, region, subscription and connector version, and maintain contract tests within the integration owner's release process.
Authentication, events, and commands#
Use the exact versioned OpenAccess guide for identity/authentication, TLS, operator permissions, token/session lifetime and event subscription. Don't copy ports, file paths or auth from old knowledge base articles into a new design.
Separate cardholder/credential management, configuration reads, event monitoring, alarm acknowledgement and command/control. OnGuard APIs can expose doors, readers, panels, alarms, photos and credentials through authorised integrations. Apply least privilege, data minimisation and immutable audit.
For event bridges, establish whether subscriptions are transient or durable, initial state behaviour, filters, gap recovery and backpressure. One official partner page says its integration supports transient hardware event subscriptions only; that statement belongs to that integration, not every OpenAccess consumer.
For door/output commands, never blind retry. Query authoritative state/journal and preserve local egress and life safety authority.
Primary sources#
- OnGuard product page, current public platform/open integration positioning.
- Historical OnGuard 8.3 data sheet: the former public download is unavailable. Obtain the exact release document through the LenelS2 portal.
- Historical OnGuard Cloud brochure: the former public download is unavailable. Confirm deployment architecture with the current product documentation.
- LenelS2 login and portal routes, gated technical documentation/support boundary.
- OAAP partner example with version/licence matrix, certification and integration specific licence evidence.
- OpenAccess REST/event bridge partner example, transient subscription evidence limited to that product.
- Cloud solutions page, current product entry point. The former Elements data sheet download returned 404; this page is not a substitute for its versioned technical contract.