Sigur passage log and badges right in the chat
Connect Sigur access control to the AI agent: pass log, timesheets and late arrivals, denied entries, employees, cards and access rules. Passes need confirmation.
How the agent works with Sigur
The agent works with the Sigur server Public REST API: the connection takes the server address with its port (9500 by default) and an operator login and password. The server usually sits on the local network, so requests go through your computer with the app running. The server answers with that operator's rights.
For timesheets the agent reads the parsed event log: passages with the employee, access point, direction and zone. Time is requested with the server time zone, and the log is read in batches of up to 3000 events, so a period of several months is collected in full.
Writing to Sigur changes people's physical access: issuing a card, an identifier, a guest badge or an access rule opens doors. The agent prepares such changes as a draft, shows the person, the card and the period, and applies them only after confirmation. Opening a door or disarming a zone is not possible through this API.
Integration scenarios
Timesheets and late arrivals
The agent collects passages for a period, finds each employee's first entry and last exit per day and compares them with the start of the shift.
Who is on site now
The agent reads each employee's last zone and shows who is inside, by department and zone.
Denied passages
The agent breaks denials down by reason, such as an expired key, no access to the door or anti-passback, and names the employees and points where they repeat.
A badge for a new hire
The agent creates the employee in a department, issues a free card and assigns an access rule, showing what will change before writing.
Card and access rule audit
The agent finds blocked employees who still hold cards, cards without a holder and employees without an access rule.
Alarms and equipment state
The agent collects controller case openings, lost connections to access points and switches to battery power for a period.
Sigur examples
8 опозданий у 5 сотрудников, в сумме 2 ч 40 мин.
- 3 опоздания у одного сотрудника, по 30 минут в среднем
- В 1 дне нет события входа: сотрудник прошёл с коллегой, это видно по отказу его карты
Считал по событиям прохода с направлением входа на точках доступа проходной.
How to connect
Before you connect
- A REST API licence: Pro, Enterprise or the Web licences: REST API module
- An operator with the REST API access (Integrations) right
- Network access to the Sigur server from the computer running the app
- 1
Enable the REST API on the Sigur server
Server management → Ports → Use REST API, port 9500, then Apply and restart the server module. A REST API licence is required: Pro, Enterprise or the Web module.
- 2
Create an operator for the integration
In the Client program on the Personnel tab give an employee operator rights, check REST API access (Integrations) and set a login and password.
- 3
Check the address and HTTPS
An address like http://192.168.0.10:9500. If Use TLS is enabled, the address starts with https and the server certificate has to validate on the computer running the app.
- 4
Paste the address, login and password
Run the app on a computer on the Sigur server network: requests to a server on the local network go through it.
FAQ
Enable Use REST API on the Ports tab of the Server management program, give an employee operator rights with REST API access (Integrations) checked and set their login and password. In the connection enter the server address with its port, for example http://192.168.0.10:9500, and that login and password.
Departments, positions, employees, cards and virtual identifiers, official vehicles, guests and guest cards, access rules, access points and zones, operators and roles, plus the event log in short and parsed form.
Only with your confirmation: it creates employees, issues and withdraws cards and identifiers and assigns access rules. Before each such write the agent shows what will change. The API has no door opening commands.
If TLS is enabled on the server, use an https address. The server certificate has to validate on the computer the requests go through; with mutual authentication the external system also needs its own certificate.