Access control × HR software · Dubai, UAE

Hikvision & Uniview Attendance to HR Software Integration

Every face scan and card tap, in your HR system automatically. No exports, no uploads.

Hikvision terminals, Hik-Connect for Teams, HikCentral Professional and Uniview access control already record who arrived and when. A secure middleware on AWS collects those punches, matches each one to the right employee and posts it to Zoho People, Odoo, SAP SuccessFactors, Oracle HCM, Workday, BambooHR or the HR system you already use.

Get a free integration review Supported HR software

Hosted on AWS
Encrypted
Private
Monitored 24/7

Attendance
middleware

Also works with

Oracle Fusion Cloud HCM
Workday
Keka
greytHR

Where attendance comes from

Hikvision, Hik-Connect, HikCentral and Uniview

Each source has its own documented way to get attendance out. The right one depends on what is already installed, so nothing needs replacing.

Hikvision access control & face recognition terminals

MinMoe face recognition terminals, card and fingerprint readers and access controllers record every verified entry with the employee number, time and verify method.

How the data gets out

ISAPI over HTTP(S) on the device: search the access-event log, or have the terminal push events to a listening server as they happen.
Hikvision's own integration notes point out that direct ISAPI integration needs the terminal reachable on a static address.

Best for: Single sites, or where each terminal can reach the middleware directly.

Hik-Connect for Teams (cloud)

Hikvision's cloud platform for businesses (Team mode) manages people, devices and access across sites, with attendance features designed for payroll.

How the data gets out

Hik-Connect for Teams OpenAPI over HTTPS, using an AppKey and SecretKey issued by Hikvision: read card/face swipe records, attendance timecards, and add or remove persons.
CSV, TXT or PDF attendance exports as a fallback.

Best for: Multi-site businesses that want devices managed in the cloud with no on-premise server.

HikCentral Professional (on-premise)

Hikvision's central management software calculates attendance from its own shift rules and keeps the person and access-level master for every device.

How the data gets out

HikCentral Professional OpenAPI (REST): door events, attendance reports and real-time event subscriptions, plus person and access-group management.
Database or CSV/TXT attendance export where an API is not an option.

Best for: Larger estates already running HikCentral on a Windows server in the LAN.

Uniview access control & face terminals

Uniview (UNV) face recognition terminals and access controllers log recognition and access records with the person ID and time.

How the data gets out

Uniview LAPI (HTTP with Digest authentication): subscribe to real-time recognition records, pull historical records and add or update people on the terminal.
Terminals can open a persistent connection out to a server, which avoids port forwarding at remote sites.
EZAccess desktop software can export attendance reports to Excel as a fallback.

Best for: Uniview estates of any size, including sites behind a normal office router.

The middleware

What happens between the door and the payslip

One always-on service, hosted on AWS, does the work people usually do by hand at the end of every month.

Collect

Receives pushed events in real time, or pulls the event log on a schedule, from every terminal and platform.

Normalise

Turns Hikvision, Uniview and cloud records into one clean format: who, when, which door or device, in or out.

Map employee IDs

Matches the device's employee number to the right person in HR, such as the Zoho People biometric mapper ID or the Odoo employee.

Remove duplicates

Drops double taps and repeated swipes inside a set window, and keeps the serial number of each event so nothing is counted twice.

Buffer offline

Terminals keep their own log when the internet drops; the middleware back-fills from the last confirmed event once the link returns.

Time zone aware

Stores every punch with its offset and sends it to HR in Asia/Dubai time, or each site's own zone across the GCC.

Push to HR

Posts check-ins and check-outs through the HR system's API, in batches that respect its rate limits.

Two-way employee sync

Where the device API allows, new joiners and leavers in HR are added to or removed from terminals automatically. Face photos only with consent.

HR & payroll software

HR software with a documented attendance API

These systems publish an API for clock-ins, time events or attendance records. Each card links to the vendor's own documentation.

In detail below

Zoho People

REST · OAuth 2.0

Check-in/check-out and bulk attendance entries APIs, keyed by employee ID, email or biometric mapper ID.

Vendor API docs

In detail below

Odoo Attendances

JSON-2 API · API key

Creates check-in and check-out records on the hr.attendance model for each employee.

Vendor API docs

SAP SuccessFactors

OData v4 · bearer token

Clock In Clock Out time events API for terminal punches, with an optional terminal ID.

Vendor API docs

Oracle Fusion Cloud HCM

REST

Time event requests endpoint for time collection devices, with supplier event codes such as punch in and out.

Vendor API docs

Workday

SOAP web services

Put Time Clock Events for near real-time punches; Import Time Clock Events for large batches.

Vendor API docs

BambooHR

REST

Time Tracking API: clock-in and clock-out entries straight into employee timesheets.

Vendor API docs

Keka

REST · attendance API key

Attendance log ingestion API built for biometric devices: up to 1,000 logs per request, back-dated up to 30 days (needs Keka's API add-on).

Vendor API docs

greytHR

REST API v2 · OAuth 2.0

Attendance swipe endpoints per employee; write access to be confirmed with greytHR for your plan.

Vendor API docs

Using something else, such as Bayzat, Darwinbox, Microsoft Dynamics 365 or a payroll bureau? If it offers an attendance API or a reliable import file, it can usually be connected. That is confirmed during the free review, before anything is built.

Two integrations in detail

Zoho People and Odoo, step by step

Two of the HR systems most used by UAE businesses, and how attendance from Hikvision or Uniview lands in each.

Zoho People

Popular with UAE SMEs, and already built for biometric devices.

Zoho People gives each employee a biometric mapper ID, which is exactly the number stored on a Hikvision or Uniview terminal. That makes matching people reliable without renaming anyone.

Terminal or Hik-Connect for Teams
Middleware on AWS
Zoho People Attendance

Endpoint: Attendance check-in/check-out API, plus a bulk attendance entries API (v3)
Auth: OAuth 2.0 (Zoho-oauthtoken), scoped to attendance only
Employee match: Employee ID, email or biometric mapper ID
Time zone: The bulk API accepts the entries' time zone, so Dubai punches stay Dubai punches
Limits: Documented per-minute and daily limits; the middleware batches to stay inside them

How it is set up

1Set each employee's biometric mapper ID to their terminal employee number.
2Create an OAuth client with attendance scopes only.
3Middleware posts punches in batches; shifts, overtime and leave stay in Zoho People.
4Payroll reads the attendance summary as it already does.

Check-in/check-out API Bulk attendance entries API

Odoo Attendances

For businesses that run HR, payroll and ERP in one Odoo.

In Odoo an attendance is a simple record: an employee, a check-in and a check-out. The middleware writes those records directly, so attendance flows on into Odoo Payroll and timesheets the way Odoo intends.

Hikvision or Uniview terminal
Middleware on AWS
Odoo hr.attendance

Endpoint: External JSON-2 API (/json/2/…), creating and updating hr.attendance records
Auth: API key of a dedicated integration user, sent as a bearer token
Employee match: Terminal employee number mapped to the Odoo employee (badge ID or a mapping table)
Hosting: Self-hosted and Odoo.sh support the external API; on Odoo Online it requires a Custom plan
Housekeeping: API keys can last up to three months, so rotation is planned in

How it is set up

1Create a dedicated integration user with attendance rights and an API key.
2Map each terminal employee number to its Odoo employee.
3Middleware opens a record on check-in and closes it on check-out.
4Missing check-outs are flagged for HR rather than guessed.

Odoo 19 external JSON-2 API

What gets synced

Exactly what moves, and in which direction

Data synced between access control and HR software
Data	From	To	When
Clock-in / clock-out punches	Terminal or platform	HR attendance	Real time, or every few minutes
Device, door and site	Terminal or platform	Attendance location / notes	With each punch
Verify method (face, card, fingerprint)	Terminal	Audit log	With each punch
Processed timecards (first in, last out)	Hik-Connect for Teams / HikCentral	HR or payroll	Daily or per pay period
New joiners and leavers	HR	Terminals or platform	On change, where the device API allows
Face photos	Enrolment at the terminal	Stays on the device / platform	Never sent to HR unless you decide otherwise

Clock-in / clock-out punches
From
Terminal or platform
To
HR attendance
When
Real time, or every few minutes
Device, door and site
From
Terminal or platform
To
Attendance location / notes
When
With each punch
Verify method (face, card, fingerprint)
From
Terminal
To
Audit log
When
With each punch
Processed timecards (first in, last out)
From
Hik-Connect for Teams / HikCentral
To
HR or payroll
When
Daily or per pay period
New joiners and leavers
From
HR
To
Terminals or platform
When
On change, where the device API allows
Face photos
From
Enrolment at the terminal
To
Stays on the device / platform
When
Never sent to HR unless you decide otherwise

How a project runs

From first call to automatic attendance

Free review

List your terminals, models, firmware, sites and HR or payroll system, and how attendance is handled today.

Choose the route

Device API, Hik-Connect for Teams, HikCentral or Uniview LAPI, based on what you already own. No rip-and-replace.

Map people and rules

Agree the employee ID mapping, duplicate window, in/out logic and which system owns shifts and overtime.

Pilot one site

Run alongside your current process for a pay period and compare the numbers line by line.

Go live and monitor

Roll out to every site, with alerts for offline terminals, failed pushes and unmatched employees.

Use cases

Built for how UAE teams actually clock in

Shift attendance

Morning, evening and split shifts recorded from the terminal, with the shift rules kept in your HR system.

Multi-site and branches

Every branch's terminals report into one middleware, tagged by site, so HR sees one clean list.

Construction sites and labour camps

Face terminals at site gates and camp entrances, with offline buffering for patchy connectivity and back-fill when it returns.

Warehouses and logistics

Shift changeovers at high volume, with duplicate taps filtered before they reach payroll.

Retail and F&B outlets

Small teams spread across malls, each outlet's punches landing in HR without anyone emailing a spreadsheet.

Visitors and contractors

Visitor and contractor entries kept separate from employee attendance, so they never touch payroll.

UAE notes

Payroll, overtime and face data in the UAE

Practical points that come up in almost every UAE project. They are general guidance, not legal advice.

WPS payroll exports

Attendance feeds the payroll system, and the payroll system produces the WPS salary file (SIF) as it does today. The integration does not replace your WPS agent, bank or exchange house.

Overtime and shift rules

Overtime, Ramadan hours, rest days and shift patterns are configured in your HR or payroll system. The middleware delivers accurate punches; it does not decide entitlements.

Face data and consent

Face templates stay on the terminal or the access platform. Employees should know how biometric data is used; consent and retention policies are your HR and legal team's call.

Data handling

Only the fields HR needs are moved, over encrypted connections, with access restricted and every sync logged.

FAQ

Questions about attendance and HR integration

Can Hikvision attendance data be sent to HR software automatically?

Yes. Hikvision terminals and platforms expose attendance through ISAPI on the device, Hik-Connect for Teams OpenAPI, or HikCentral Professional OpenAPI. A middleware collects those events, matches each employee and posts the check-ins and check-outs to your HR system's API, so nobody exports or uploads files.

Does the Hik-Connect app have an API for attendance?

The Hik-Connect mobile app does not document a public attendance API. For businesses, Hikvision offers Hik-Connect for Teams, which has an OpenAPI for swipe records, attendance timecards and people. The integration uses that, or the terminal's own API.

Can UNV-Link attendance be integrated with HR software?

UNV-Link is Uniview's mobile app for viewing and managing devices, and it does not document a public attendance API. The integration connects to the Uniview face terminals or access controllers directly through Uniview's LAPI, which supports real-time and historical recognition records.

Which HR software works with Hikvision or Uniview attendance?

Any HR system with an attendance API. Zoho People, Odoo, SAP SuccessFactors, Oracle Fusion Cloud HCM, Workday, BambooHR, Keka and greytHR all document one. Others can usually be connected through their API or a reliable import format.

How are employees matched between the terminal and HR?

Each person's employee number on the terminal is mapped to their record in HR, for example the biometric mapper ID in Zoho People or the employee in Odoo. Unmatched punches are held and flagged, never dropped silently.

What happens when a site loses internet?

The terminals keep recording locally. When the connection returns, the middleware back-fills from the last confirmed event and skips anything already delivered, so the day's attendance is complete without duplicates.

Do I need to replace my access control or HR system?

No. The integration works with the Hikvision or Uniview devices and the HR software you already have. Door access, alarms and the mobile apps keep working exactly as they do now.

Is face recognition data sent to the HR system?

No. Only attendance events such as employee number, time, device and direction are moved. Face templates stay on the terminal or access platform, and how biometric data is handled remains your company's policy.

See every API integration service

Tell me which terminals and HR system you use

Share the device models, how many sites, and your HR or payroll software. You will get a clear plan for the integration route before anything is built.