Scope of the integration and division of responsibilities
InnerWeb does not produce or replace access control readers. It integrates with the client's existing access control (KD) system and receives card punch events through a webhook, according to the specification for the access control vendor. Readers, cards and controllers stay with the client and its integrator.
InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. In this integration the access control system is the source of events and the working time module is the recipient. That is why the points below divide the work into what the integrator does and what InnerWeb does.
Event fields in the integration specification
The integration specification assumes that the access control system sends events in real time, each event with seven pieces of information. InnerWeb receives them through an authenticated webhook.
- Event time: the moment of the punch according to the access control reader clock.
- Place: the gate or reader where the punch was made.
- Person data: an unambiguous link between the card and the employee.
- Company: the employer of the person, which distinguishes own employees from external companies.
- Number of the active card at the moment of the punch.
- Direction: entry or exit, resulting from the reader configuration.
- Event identifier: stable and unique, unchanged when the event is sent again.
Event fields: punch identification and a full set for the records
Direction and event identifier: why they are required
For the records every entry must be either an entry or an exit, and the direction from the reader allows presence to be opened or closed. The event identifier prevents the same punch from being counted twice, for example when it is sent again after a break in the link.
The rules for pairing entries and exits and rejecting duplicates are set in the specification with the access control vendor, together with the scope of work on both sides of the integration. We do not treat them as a ready feature to switch on, but as an element of the implementation project.
What the access control integrator does
Configures the direction resulting from the reader setting, for example an entry reader and an exit reader on the same gate, and assigns stable, unique event identifiers that do not change when the event is sent again.
What is set in the specification
On the InnerWeb side the specification sets the reception of direction and identifier, the rejection of duplicates and the mapping of an event to an entry or exit in the records. Scope and schedule are planned with the client and the access control vendor.
Authentication and continuity of delivery
The webhook is authenticated with a token that has a limited validity period and is renewed automatically by the integration. The integrator handles a refusal response without losing events. We recommend a queue on the access control system side, with resending in the original order and with the original punch time from the reader.
When the link is down for one hour, events are sent with the time of the punch, not the time of sending. The records count minutes, so the event time from the reader is the basis of the entry.
Order of rollout and testing
We recommend three steps, each with a separate completion criterion.
- Step 1: test sending of events from one gate, checking that all seven fields are complete.
- Step 2: duplicate test and link interruption test, with direction and identifier in every event.
- Step 3: switching on for a test group in the working time pilot and comparison with records from QR scans.
What the plant gains from complete events
A plant with an access control system has two sources of attendance: cards and QR scans. Complete punch events can feed the records, and InnerWeb links them with qualifications, permits and attendance. The employer keeps working time records as the basis for calculating pay and other benefits (Kodeks pracy, art. 149 § 1), so one consistent source of records reduces manual reconciliation.
Before the start, ask the integrator three things: whether entry and exit readers are distinguished in the controller configuration, whether the access control system assigns persistent event identifiers, and how long it keeps unsent events in its queue. Record the answers in the pre-implementation protocol, because the scope of work on both sides of the integration depends on them.
Video
Frequently asked questions
Does InnerWeb supply card readers?
No. InnerWeb integrates with the client's existing access control system, and the readers stay with the client and its integrator.
Which fields must a punch event carry?
Reader event time, place, person data, company, active card number, direction (entry or exit) and event identifier. The rules for pairing and rejecting duplicates are set in the specification with the access control vendor.
How is the webhook authenticated?
The token has a limited validity period and is renewed automatically by the integration. Events wait in the access control system's queue if sending fails.
Sources
Pass the specification to your integrator
We will prepare for your integrator a description of the event and an implementation plan for the integration. Book a meeting with the InnerWeb team.
Let's talk