FOR BUILDERS, DEVELOPERS & INTEGRATORS

Integrate your access system with EntryLuma

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

  1. Device event
  2. API request
  3. Portal record
ONE SHARED WORKFLOW

Keep your hardware.
Build the connection.

Your adapter speaks to the reader or vendor platform. EntryLuma handles the branch context, mapped access users, recipient settings and notification workflow.

Reader or vendor platformYour adapter or connectorEntryLuma cloudConfigured notifications & recipients

BUILT FOR DIFFERENT SYSTEMS

A documented route
from device to notification.

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.

01

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.

02

Submit it securely

Send a normalised event over HTTPS with a device credential. Keep a durable outbox, retry the same event safely and report connector health.

03

Let EntryLuma connect it

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.

A clear division
of responsibilities.

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 →

Your integration handles

Reader/vendor authentication, confirmed-event mapping, clock handling, reader identity checks, durable retries and optional event-photo correlation.

EntryLuma handles

Organisations and branches, access-user mapping, configured recipients and channels, notification layouts, attendance records and downstream queues.

A PRACTICAL STARTING POINT

Developer guide, API schema and examples

API reference

Authentication, attendance events, response meanings, connector heartbeats and optional authentication-photo workflows.

Read the guide →

Machine-readable resources

Download the OpenAPI definition and a Postman collection with blank secret variables and fictional sample events.

Get the resources →

Reference examples

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 →

Start with a test branch.

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.

Entry Device and CCTV APIs

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.

CCTV SETUP

Connect a compatible camera

CCTV uses the local Windows connector for snapshot-based detection and zone rules. Share your camera model to check compatibility.

Explore CCTV alerts

LET’S CONNECT YOUR SYSTEM

Build with EntryLuma.

Tell us the device brand, model, firmware and available API or SDK. We’ll help identify the integration route.

Talk to our team →

Read the CCTV API guide →

WHATSAPP DELIVERY

Connected through WebWMS2U.

See how reader events and camera alerts pass through EntryLuma processing to the configured WhatsApp delivery route.

Explore the delivery workflow →