Kapri 2-K is an access control and time and attendance control terminal designed to integrate directly and seamlessly with your cloud-based application. It communicates via HTTP (POST) in JSON format, eliminating the need for complex network configurations: you don’t need to open ports, set up VPNs, or install software within the client’s LAN. This way:
In addition, you can customize the terminal’s behavior for each use case from your own backend, with quick and easy configuration thanks to its built-in web server.
We have designed Kapri 2-K for the following applications:
This option is best suited for extranet web applications, since in these environments—for security reasons—the cloud application is not typically allowed to initiate communications with devices; instead, only the terminals can do so. Kapri 2-K initiates communication, and when an event occurs—such as a card being read—it sends a POST command to the cloud application or API server. In response, the application sends a set of commands for the terminal to execute, such as displaying messages on the screen and activating relays to grant access.
The Cloud protocol is characterized by:
– The Kapri terminal initiates all communications.
– Communications are secure when the cloud uses the HTTPS protocol.
– No drivers, .DLLs, or services need to be installed.
– The application does not need to know the terminal’s IP address.
– Easy installation. No local installation is required.
The Kapri 2-K terminal supports the following communication protocols:
*For more information, see the Communication Protocols tab.
The Kimaldi Kapri 2-K is available as an integration module for installation in turnstiles, barriers, and doors.
Kapri 2-K uses RFID technology with MIFARE/DESFire cards, wristbands, or key fobs.
Integration is done by exchanging JSON objects. No SDK is required; you can integrate directly from your backend using HTTP/JSON.
POST via HTTP/HTTPS and sends the data in JSON format (JSON objects).
The terminal initiates communication: when an event occurs (RFID/QR scan, key press, etc.), it sends a POST request to an endpoint in your application. Your system can then respond with instructions for the terminal to execute.
There is no need to open ports, configure VPNs, or install software on the customer’s network/LAN.
Yes: Since it uses HTTP + JSON, the integration is independent of the programming language and operating system.
Yes, setup is easy using an intuitive internal web server.
Yes. It features an offline mode and can operate autonomously, including local whitelists to continue operating during connection outages.
Kapri 2-K features a 16-key keyboard for user interaction. The terminal can generate events in response to keystrokes.
Setup is usually quick because it doesn’t require opening ports or setting up a VPN, nor does it require installing software on the LAN, and integration is done via HTTP/JSON. If you’d like to run a pilot test, please contact us.
Kimaldi offers technical support from Terrassa (Barcelona) and a 2-year warranty. Support is available by phone and email, Monday through Thursday from 9:00 a.m. to 2:00 p.m. and from 4:00 p.m. to 6:00 p.m., and Friday from 9:00 a.m. to 2:00 p.m.
| Display | 2.4'', IPS, 320 x 240 |
|---|---|
| Keyboard | 16-key capacitive touchscreen |
| Ethernet | 10/100 Base-T |
| PoE | Full compatibility with IEEE 802.3bt, IEEE 802.3at, and IEEE 802.3af |
| Feeding | 5 VDC +/-10%. |
| Maximum consumption | 1,000 mA |
| Wi-Fi | 802.11 b/g/n Wi-Fi, 2.4 GHz band |
| TTL | 2 internal ports: |
| RS-232 | 2 internal ports: |
| Relays | 3 relays, power-free, 24V/1A (24/1A: 500,000 operations) |
| Buzzer | 1 integrated circuit |
| Digital Tickets | 4 digital inputs active to ground, inactive in open-circuit mode. |
| AntiTamper | 1 anti-tamper input |
| RTC | 1 integrated circuit |
| Operating temperature | -20°C to 50°C |
| RFID Technology | |
| RFID Solutions | |
| Certificate | EC |
The Kapri terminal communicates via TCP/IP (Ethernet cable or Wi-Fi). Communication with the application always takes place through the exchange of JSON objects.
To simplify terminal configuration , you can use a web browser to connect to the Kapri’s built-in web server and select the communication protocol from there.
The device supports the following protocols:
JSON-TCP/IP
The terminal provides a TCP/IP communication port through which it will send and receive JSON objects. This port can function as either a server or a client, depending on how it is configured.
This option is best suited for applications developed in languages that do not support web protocols but can handle standard TCP/IP sockets.
KTP
It is a proprietary protocol developed by Kimaldi that uses a KTP network controller and performs the following functions:
– Automatically detects devices on the LAN.
– Provides an API interface with the software
– Offers a Socket.IO channel for event management.
– Encrypts communications using AES-256.
This option is best suited for intranet applications that need to manage multiple devices whose IP addresses are unknown. The application interacts exclusively with the KTP network driver/controller. It also allows terminals on the same LAN to be grouped so they can be controlled by different applications.
HTTP
The terminal provides an API Server interface that supports POST and GET commands. The terminal can optionally send events via Socket.IO to avoid polling by the application. No drivers need to be installed. The application needs to know the terminal’s IP address.
This option is best suited for intranet web applications, since in these environments applications can freely access devices.
Cloud
The terminal always initiates communication. When an event occurs—such as a card being read—it sends a POST command to the cloud-based application or API server. In response, the application sends a batch of commands for the terminal to execute, such as displaying messages on the screen and activating relays to grant access.
The Cloud protocol is characterized by:
– The Kapri terminal initiates all communications.
– Communications are secure when the cloud uses the HTTPS protocol.
– No drivers are required.
– The app does not need to know the device’s IP address.
This option is best suited for extranet web applications, since in these environments—for security reasons—the cloud-based application is not typically allowed to initiate communications with devices; instead, only the end devices can do so.
