Starting point: a plant with KD that does not want to change it
The concept applies to a mid-sized production plant that has used a card-based access control system for years. Readers hang at the gate, in the changing rooms and at the entrances to production halls, and the KD vendor maintains them. Security can see that a card is valid, but cannot see whether its holder has a valid OHS induction training or whether an external company is allowed on site.
InnerWeb is a software maker, not a reader maker. It does not produce or replace access control devices. It integrates with the existing KD system as an independent supplementary system working alongside KD, working time records (RCP), HR and ERP. This assumption shapes the whole project: no hardware is exchanged, no gate goes down, and there is a single integration on the software side.
The point of contact is the card swipe webhook. The KD system sends an HTTP POST to InnerWeb with each swipe, and InnerWeb receives it as an event and links it to the person's account, their trainings, qualifications and company.
Day 1: authentication and the first test message
On the first day the integrator on the KD side gets access to the InnerWeb API. Calling the webhook requires a token, which is obtained from the API login endpoint. The token has a limited validity period and is renewed automatically by the integration. In practice, the service on the KD side has to renew the token regularly, or before each batch of submissions.
A typical mistake on day one is hard-coding the token in the script configuration. The token expires after a set time, so the integration works at first and then submissions start being rejected. A good pattern is a short login routine that runs when the response code rejects authorisation.
The first test message should concern one known person with a card. Security checks in InnerWeb that the swipe appeared on the correct account, and only then switches production traffic on.
Scale and range of events in the swipe integration
Days 2 and 3: person and company data in the submission
According to the specification, the KD system sends in each swipe submission the reader event time, the direction (entry or exit), the event identifier, the swipe location and the person's data: first and last name (required), acronym, company (company name required), active card number, phone, email and language. The active card number is the identifier by which InnerWeb links the swipe to the person's account, and the external company is assigned based on the company name in the submission.
Days two and three are for checking who appears in the system. A swipe by a person InnerWeb does not know creates an account and a company from the submission data. If the same company is recorded in KD once by its full name and once as an abbreviation, the system will end up with two companies. That is why in this window security and HR compare the company list in KD with the company list in InnerWeb and unify the spelling at the source.
- compare company names in KD and in InnerWeb
- check that every person has an active card number
- check that the language field is filled in for foreign workers
Days 4 and 5: swipe locations and the training alert
The swipe location field tells the readers apart. Events from a location that has no template defined in InnerWeb go to the log and do not trigger the training alert. This is the most common surprise on day four: the reader at the main gate works as it should, while the reader at the delivery gate writes to the log and triggers no reaction.
Security therefore reviews the list of all locations that send submissions, and for each one decides whether it should have a template requiring training. Only a complete set of templates gives certainty that a missing training is reported no matter which gate the person came through.
Day 6: load and event bursts check
In a plant with several external companies, card traffic during shift hours comes in spikes. In a plant with many staffing agencies, traffic can exceed 2,000 swipes per working day, so the integration has to withstand bursts of events and repeats. On the sixth day the IT team on the KD side checks whether, after a line outage, the submission queue is sent in order and whether retries do not duplicate events.
The specification requires the KD system to send events in real time, with the event time taken from the reader. This is the condition for a reliable record of entries and working time.
On the InnerWeb side it is worth preparing, in parallel, a control view for security that shows events from new readers as they arrive. In the first days of production traffic it helps catch a reader that sends data in a different format from the rest.
Day 7: what the webhook alone does not give
The card swipe webhook alone does not yet give working time records: a mapping of events to entries and exits is also needed. On the last day of the week the team decides whether the swipes should feed the entry register, and records with the KD vendor's specification the rules for pairing entries and exits and for rejecting duplicates.
The added value of InnerWeb is linking a swipe to the account, trainings and permits. A KD swipe only says that a person passed a point. InnerWeb answers whether that person was allowed to do so under the plant's requirements.
Video
Frequently asked questions
Do we need to replace the card readers for the integration?
No. InnerWeb does not produce or replace card readers. It integrates with the existing KD system, which sends swipes by webhook.
What happens when the token expires?
The call is rejected. The token has a limited validity period, so the service on the KD side should renew it automatically from the login endpoint.
Will a swipe by a person unknown to the system be rejected?
No. The system creates the account and the company from the submission data, so personal data and the company name must be consistent.
Do you have a KD system and want to add OHS?
Book a call about integrating the card swipe webhook with your access control system. We will check what data the vendor sends and what needs to be set up on the InnerWeb side.
Let's talk