Acting as Third Party Access Control

When a building is already equipped with a centralized access control system or a parking management system made for ticketing, it will then be possible to integrate this ACS with the Izix API in order to position the API as a secondary validation database. This will allow the customer to keep centralized security and session logs inside the initial system and avoid operational process disruptions.

📘
If you are a Third Party Application looking to trigger the opening of barriers from within your application, please refer to this article instead.

Platform Components

The integration utilizes specific components of the Izix platform, as illustrated in the diagram below.

Overview of the Access Flow

The integration between your ACS and the Izix system involves several key interactions where the ACS communicates with the Izix API in real time to verify and log access rights and capacity management. Here's a simplified step-by-step explanation:

Identification at the gate: A user approaches the parking gate and is identified by a reader (part of the ACS).
Access Request Sent to Izix API: The ACS treats the request and sends it to the Izix API to validate whether the identified user has the right to access and if there is available capacity in the parking.
Izix API Processes Request: The Izix API checks the user’s access rights, schedule, balance and the current parking capacity.
- If access is granted and space is available, the Izix API sends a confirmation back to the ACS.
- If access is denied (due to invalid rights or lack of space), the Izix API sends a denial.
ACS Executes Action:
- If confirmed, the ACS opens the parking barrier or any other necessary local actions.
- If denied, the ACS does not open and ideally communicates the denial to the user via a sign or other notification method.
Logging Entry in Izix API: If the access is granted and the barrier is opened, the ACS logs this confirmation of passage in the Izix API.
Izix Updates Occupancy and Logs: After receiving confirmation of the user's entry, Izix updates its occupancy records and logs the event for future reference and analysis.

Diagram of the Flow

Authorized Flow

Unauthorized Flow

Key Points for the Integrator

Flow Criticality: Understanding where and how the ACS needs to interact with the Izix API is crucial. An approximative integration will immediately result in bad user access experience as well as data inconsistencies leading to occupancy issues.
Network Stability: Izix is a synchroneous system, parking capacity as well as rights and credentials (Licence Plates) are subject to changes at any point in time. We strongly advice to invest in a stable and redundant web connexion to avoid drops or latencies.
Security: This integration does not require to provide Izix with a writing access in your Access Control Database to prevent any security risk. Izix API is only contacted from the ACS servers and not the other way around.