How the integration works and what InnerWeb does not do
The integration point with the existing access control system is the card swipe webhook: the access control system sends an HTTP POST request at every swipe. InnerWeb does not produce or replace readers. It is an independent system that complements the access control, time and attendance, HR and ERP systems. For IT this means that the point of testing is the access control vendor and its sending queue, not the equipment at the gate.
The notification contains the time of the event, the swipe location and the person's data: first name and surname (required), an acronym, the company (name required), the number of the active card, phone, e-mail and language.
Step 1: authentication and token renewal
Calling the webhook requires a JWT token obtained from the API login endpoint. It is a token with a limited validity time, renewed automatically by the integration. With several shifts a day, renewal must work without human involvement, also in the middle of a shift. The IT team should check whether the access control system renews the token before it expires and what it does after a rejecting response.
Suggested test: force a token renewal in the test environment and observe whether swipes from the access control queue are not lost. Record how many swipes are repeated after the renewal.
Average swipe rate depending on the shift start time, example
Step 2: requirements of the specification for access control events
The access control system sends events in real time, with the event time read from the reader, the direction (entry or exit) and an event identifier, and InnerWeb receives them through an authenticated webhook. The rules for pairing entries with exits and for rejecting duplicates are set in the specification agreed with the vendor. This matters at peak: if the access control system collects swipes in a queue and sends them with a delay, InnerWeb counts the time of the swipe from the reader, not the time of sending.
The event identifier allows a repeated request to be told apart from a new swipe. The IT team should therefore agree with the vendor the retry rules, limit them to cases without an acknowledgement of receipt, and describe how the access control system behaves. Statuses such as start and end of work are outside the scope of this integration.
Step 3: distinguishing gates and swipe locations
A vendor that handles swipes at several locations tells them apart with the swipe location field. In a warehouse with several gates, airlocks and entrances to zones, a dictionary of location names must be agreed and kept stable. Renaming a gate in the access control system without agreement breaks the reports.
- List all swipe locations in the access control system and their names.
- Agree with the InnerWeb administrator the scope of locations covered by training control.
- Test a swipe at every gate before the peak.
Step 4: load test before the season
Assuming 400 people within 15 minutes, swipes arrive on average at 400 / 900 seconds, which is about 0.44 swipes per second, and in short bursts at the peak it is many times more. This is an example calculation. The test should reproduce this pattern: a series of requests from the access control system with data of several hundred people, including new people unknown to the system. Watch the response delay, the rejections and the number of accounts and companies created.
A swipe by a person unknown to the system creates an account and a company, so the test with new people also checks the uniformity of agency name spelling.
What the IT team should have ready before the first peak
Three things matter most: the token renewal procedure, a description of the access control system's behaviour when there is no response, and a contact to the InnerWeb administrator for the peak period. It is also worth deciding who in IT watches the gate during the first 30 minutes of the shift.
Video
Frequently asked questions
How does the webhook token work?
It is a token with a limited validity time, renewed automatically by the integration, so the access control system should renew it during the shift.
What data should the access control system send?
Real-time events with the reader time, the direction (entry or exit) and the event identifier. The pairing and duplicate rules are set in the specification with the vendor.
How does InnerWeb know which gate it is?
From the swipe location field in the notification. The names must be kept stable.
Can the load test run in production?
We recommend a test environment, because a test with new people creates accounts and companies.
Test the integration before the season
Book a call with the IT team. We will go through the token, the swipe queue and the location dictionary before the shift starts with several hundred cards.
Let's talk