Capture a successful event
Use the vendor’s supported interface to identify a confirmed authentication. Map the person ID, reader identity, original timestamp, method and event type.
FOR BUILDERS, DEVELOPERS & INTEGRATORS
Bring events from your biometric or card access system into EntryLuma. Connect verified arrivals to cloud records and notifications for the people your customer selects.
Integration workflow
BUILT FOR DIFFERENT SYSTEMS
We currently support selected Hikvision devices. Other brands can connect through a manufacturer-specific adapter when their APIs, SDKs or event interfaces provide the required information.
Use the vendor’s supported interface to identify a confirmed authentication. Map the person ID, reader identity, original timestamp, method and event type.
Send a normalised event over HTTPS with a device credential. Keep a durable outbox, retry the same event safely and report connector health.
EntryLuma matches configured access users and branch settings, records attendance and creates eligible notification jobs for its delivery workers.
Compatibility is assessed per device, firmware and vendor interface. The cloud API does not supply a universal driver or automatically certify another manufacturer’s hardware.
YOUR ADAPTER. OUR CLOUD WORKFLOW.
Build in the language and environment that fit your system. An adapter can run on site or in a vendor cloud service when the vendor’s interface permits it.
Explore the architecture →Reader/vendor authentication, confirmed-event mapping, clock handling, reader identity checks, durable retries and optional event-photo correlation.
Organisations and branches, access-user mapping, configured recipients and channels, notification layouts, attendance records and downstream queues.
A PRACTICAL STARTING POINT
Authentication, attendance events, response meanings, connector heartbeats and optional authentication-photo workflows.
Read the guide →Download the OpenAPI definition and a Postman collection with blank secret variables and fictional sample events.
Get the resources →Start with JSON event examples and a Python transport example that defaults to a dry run, then commission against an authorised test branch.
See the examples →Create the organisation, branch, device and mapped access users in the portal, obtain the authorised device credential, and confirm recipient settings. Test real successful events, duplicate handling, offline recovery and final notification receipt before rollout.
Event acceptance is not proof of notification delivery. Photos are optional and must belong to the same authentication event. Recipient management stays in authorised portal workflows.
Attendance integrations use the versioned event, heartbeat and photo-policy endpoints. CCTV integrations use a separate camera credential to submit alerts and resolutions. Detection runs locally, and the portal can queue configured notifications.
LET’S CONNECT YOUR SYSTEM
Tell us the device brand, model, firmware and available API or SDK. We’ll help identify the integration route.
WHATSAPP DELIVERY
See how reader events and camera alerts pass through EntryLuma processing to the configured WhatsApp delivery route.