Aprionex Bio

Your terminals.
Your systems.
Connected.

Biometric Attendance API & Device Integration

Connect your attendance terminals to your HR and ERP systems. Receive attendance from compatible eSSL and ZKTeco-family terminals using ADMS / PUSH, keep employees in sync across locations, and deliver clean attendance data through a REST API and signed webhooks.

For HR teams, system administrators and integration developers.

Aprionex. BIODEVICE BUSINESS SYSTEM
01
Attendance terminalsCompatible eSSL & ZKTeco-family devices
02
ADMS / PUSH connectionDevice communication & attendance collection
03
Aprionex BioEmployee sync, device visibility & log handling
04
REST API & signed webhooksStructured access & event delivery
05
Your HR or ERP systemUse attendance data in your business workflow

Integration overview · Not live device data

A connection your systems can use

Turn device records
into usable attendance data.

Bring terminal connectivity and employee synchronisation into a central workflow, then connect the output to the systems your teams already use.

01 / CONNECT

Bring devices into view.

Register compatible terminals and follow their heartbeat, last contact and attendance logs.

02 / SYNCHRONISE

Keep employee records aligned.

Manage employees and their location assignments to support synchronisation with the appropriate devices.

03 / INTEGRATE

Deliver data where it matters.

Use REST API access and signed webhook delivery to connect attendance records with your HR or ERP workflow.

Core capabilities

From terminal connectivity
to business integration.

01

ADMS / PUSH connectivity

  • Compatible eSSL terminals
  • Compatible ZKTeco-family terminals
  • Device communication through the push protocol
02

Device monitoring

  • Device registration and heartbeat
  • Online, stale and offline status
  • Last-contact visibility
03

Attendance collection

  • Receive device attendance logs
  • Review collected records
  • Duplicate-safe processing
04

Employee synchronisation

  • Central employee records
  • Location-based assignment
  • Synchronisation across assigned locations
05

Command workflows

  • Queue device operations
  • Track polling and acknowledgements
  • Review command results
06

REST API

  • Structured access for integrations
  • Authorised API access
  • Attendance and device information
07

Signed webhooks

  • Event-based delivery to your endpoint
  • Verify message signatures
  • Connect downstream business workflows
08

Locations & administration

  • Organise devices by location
  • Manage employee location relationships
  • Scope operational access
09

Operational traceability

  • Attendance and device logs
  • Command status records
  • Audit records for administrative actions
Employee & location management

The right people.
On the right devices.

Keep employee synchronisation connected to the places where people work.

Organise devices under locations and maintain employee assignments across their required sites. Use this structure to coordinate the employee records that need to reach each device.

Discuss your site structure
  1. Define locations

    Organise the offices, plants or operational sites in your deployment.

  2. Assign attendance devices

    Associate each terminal with its operational location.

  3. Map employees to locations

    Maintain the employee’s primary and additional location requirements.

  4. Synchronise and monitor

    Coordinate employee records with the relevant devices and review the resulting device activity.

REST API & signed webhooks

Connect attendance
to your next workflow.

Choose how your system receives the data it needs.

Request / REST API

Retrieve data from your application.

Your integration requests attendance or device information through authorised API access. Map employee identifiers and timestamps to the records used in your HR or ERP system.

  • Structured integration access
  • Permission-scoped credentials
  • Controlled request rates
Receive / Signed webhooks

React to incoming events.

Send events to an endpoint in your application. Verify the webhook signature before processing the message and design the receiving workflow to handle repeated delivery safely.

  • Event-driven data delivery
  • Signature verification
  • Business-system hand-off
The integration scope, field mapping, authentication and receiving-system behaviour are agreed for your environment. A REST API does not by itself provide a ready-made connector for every HR or ERP product.
Device operations

Manage the connection.
Follow the result.

Use command workflows and logs to coordinate supported device actions and review their outcomes.

User operations

  • Employee data synchronisation
  • Block or unblock operations
  • Remote enrolment where supported

Attendance operations

  • Attendance log requests
  • Date and time requirements
  • Log and stamp operations where supported

Device administration

  • Device list and last ping
  • Reboot and connection settings
  • Door-control commands where supported

Command availability and behaviour depend on device model, firmware and configuration. A command queued or acknowledged by a terminal is not by itself proof that the intended physical action completed.

Compatibility & implementation

Start with your device.
Validate the full journey.

Designed for compatible eSSL and ZKTeco-family terminals that support the ADMS / PUSH protocol.

Share the terminal model, firmware and connection details so the integration can be assessed against your actual setup.

What we confirm with you

  • Device model, firmware and ADMS / PUSH support
  • Network reachability and server settings
  • Employee identifiers and location assignments
  • Time-zone and attendance timestamp handling
  • Required commands and their device behaviour
  • HR / ERP fields and receiving endpoints
  • End-to-end testing with real attendance records

eSSL and ZKTeco are third-party brands. Compatibility is assessed for the selected devices and does not imply endorsement.

Frequently asked questions

Plan a reliable connection.

What is Aprionex Bio?

Aprionex Bio is a biometric attendance integration platform from Aprilent Software Solutions Private Limited. It connects compatible terminals, supports employee synchronisation and delivers attendance data through REST APIs and signed webhooks.

Which devices can connect?

The product targets compatible eSSL and ZKTeco-family terminals using ADMS / PUSH. Exact support depends on model, firmware, protocol behaviour and configuration.

Can employees be synchronised across locations?

Yes. Employee location assignments support synchronisation with the appropriate devices across the locations where they work.

Can we integrate it with our existing HR or ERP system?

REST API access and signed webhooks support integration with external systems. Field mapping, authentication and a receiving integration must be implemented or configured for your target system.

What is the difference between an API and a webhook?

An API lets your application request information. A webhook delivers an event to your application’s endpoint. Webhook signatures should be verified before accepting the event.

Are all remote device commands supported on every terminal?

No. Device capabilities vary. The required commands should be tested against your model and firmware, including confirmation of the actual result.

Does this page show live device data?

No. The connection graphic is an illustrative overview. A demonstration can be arranged for your device and integration requirements.

Let’s connect your attendance

Bring your terminals
and business systems together.

Share your device models, locations and target HR or ERP system.

Request a Bio demo