Hikvision attendance integration
Hikvision access-control terminals post events straight to SignHR — no PC software in between, and nothing to keep running at the site.
SignHR accepts access events directly from Hikvision terminals. Unlike most attendance integrations, there is no PC software in the middle: the terminal itself posts each event to a SignHR endpoint over HTTP, and SignHR turns it into an attendance punch. That means one less machine at each site that has to be switched on for attendance to work.
How it works
- 1
Point the terminal at SignHR
Hikvision terminals support posting event notifications to an HTTP listener. You configure that listener URL in the device, including the access token issued for your workspace.
- 2
The device posts events as they happen
Each access event arrives as a document the terminal composes itself. SignHR parses it, extracts the employee identifier and the timestamp, and normalises it into a punch.
- 3
Events become attendance
Punches are deduplicated, localised to the device's timezone, paired into sessions and attributed to the right business date — including night shifts that cross midnight.
- 4
Delivery is always acknowledged
SignHR answers every delivered request successfully, even for an event it could not interpret. A Hikvision terminal treats a failure response as the server being down and will change its behaviour; one unreadable event is a much smaller problem than a device that stops trying.
Where it stops
Every integration has edges. These are ours, stated here rather than discovered during implementation.
- Because the terminal cannot set custom request headers, the access token travels in the URL. Treat that URL as a credential — anyone with it can post events for your workspace.
- One-way only. SignHR does not push users, cards or face templates to the terminal; enrolment stays on the device.
- An event SignHR cannot interpret is acknowledged and dropped rather than retried, because the alternative is a device that decides the server is unavailable. Unusual firmware should be piloted on one terminal first.
Questions
No, and that is the main advantage over most attendance integrations. The terminal posts directly to SignHR, so there is no PC running a service that has to stay switched on. Fewer moving parts at each site means fewer ways for attendance to quietly stop arriving.
It consumes access-control events, which is what these terminals emit when someone is granted entry. If the terminal is on a door rather than a dedicated attendance panel, those entries become punches — which is usually what a site wants, but worth deciding deliberately.
The most common causes are the configured URL missing its token, or the device being unable to reach the internet. Because SignHR acknowledges every delivered request, the device's own logs will show delivery succeeding even where an event could not be interpreted — so check the SignHR punch log rather than the terminal when reconciling.
Yes. Devices from different vendors register separately by serial and write into the same attendance record, so a company that inherited mixed hardware across sites does not have to standardise before it can consolidate reporting.
This integration feeds Time & Attendance.
Other integrations
Technical detail last checked against the product on 2026-08-07.