The role of InnerWeb: what we do not do
InnerWeb is a software manufacturer. It does not produce or replace access control readers, does not sell access control cards and does not change controller configuration. Readers, cards and controllers remain within the scope of the access control supplier, and their contract and warranty do not change because of the integration.
This keeps purchasing clearly separated: the access control supplier is responsible for the doors, and InnerWeb is responsible for what happens to the swipe next. The purchasing department does not have to coordinate two hardware suppliers on the same doors.
How a swipe event reaches InnerWeb
InnerWeb receives card swipe events from the access control system through an HTTPS webhook and links them with qualifications, permits, attendance and working time recording. The message contains the swipe time from the controller, the reader identifier, the person, the card number in the form object_code-number and, optionally, the direction and an event identifier, which is used for idempotency, meaning protection against processing the same event twice.
Integration authentication uses a technical account and a JWT token valid for 12 hours. The access control supplier therefore receives a clear specification: the account, the token and the message format.
Parameters of the access control swipe integration
Network and security: ports
In the integration with the access control system, the connection is initiated by the plant side as outbound traffic on port 443. There is no need to open inbound ports in the plant network, which simplifies the conversation with the IT department and usually shortens agreements with the firewall administrator.
From the IT perspective, three things are worth recording in the documentation: the destination address, the technical account and the owner of the token on the access control supplier's side.
Entry and exit: what if the access control system does not distinguish direction
It happens that a working access control system uses proximity cards in the 26-bit Wiegand format and does not distinguish entry from exit. In such a plant InnerWeb records working time without replacing cards or readers.
When a message carries no direction, pairing of entry and exit is done in InnerWeb software: a window of up to 13 hours, and a swipe repeated within less than 180 s is treated as a duplicate. These rules are described in the agreements, so that HR knows how the working day is counted.
Scale and working time
In a similar integration running since 2024, about 2,100 swipes a day are processed on working days. This is an order of magnitude for a medium-sized plant and a reference point when planning throughput.
The working time module in InnerWeb is delivered switched off by default and is enabled by an administrator setting, so the swipe integration does not change working rules without a decision by the plant.
Changing readers in the future
If the plant changes the reader-to-controller protocol, for example from Wiegand to OSDP, no changes are required on the InnerWeb side, as long as the access control system keeps sending events. The integration depends on the system events, not on the reader type.
Video
Frequently asked questions
Does InnerWeb supply readers and cards?
No. Readers, cards and controllers are supplied by the access control supplier. InnerWeb integrates with the client's access control system and receives swipe events.
What must the access control supplier send?
The swipe time from the controller, the reader identifier, the person, the card number in the form object_code-number, and optionally the direction and an event identifier.
Do inbound ports have to be opened?
No. The connection is initiated by the plant side as outbound traffic on port 443.
What if the access control system does not provide the direction?
Entry and exit are paired in InnerWeb: a window of up to 13 hours, and duplicate swipes within less than 180 s.
How many swipes a day can be processed?
In a similar integration since 2024, about 2,100 swipes a day are processed on working days.
Sources
Let's talk about integrating with your access control system
We will describe which events from the InnerWeb access control system can be received and how to connect them with permits, attendance and working time recording. We will propose a demonstration on your data.
Let's talk