A Simple Guide to Supported Integration Methods

Introduction

Keka HRMS supports multiple ways to integrate biometric systems, making it easier for your organization to track attendance and access control. Whether you're a growing startup or a large enterprise, integrating your biometric devices can streamline data flow and reduce manual effort.

This guide walks you through all the integration options currently available in Keka, along with what information you'll need to get started.

Note: These integration methods apply to biometric attendance devices only.

Currently Supported Integrations

1. SQL-Based Biometric Integration

This method connects your biometric device directly to an MS-SQL database. The device sends attendance data to your SQL server, which Keka then accesses to process logs.

• Best suited for organizations with existing SQL infrastructure

• Offers flexibility in how data is retrieved and managed

• Works with most biometric devices that support SQL logging

Important: Keka currently supports only MS-SQL for this type of integration.

What you need to provide:

• SQL database details

• Biometric device specifications

• Network configuration
  

2. SDK-Based Biometric Integration

SDK-based integration uses a Software Development Kit provided by the biometric device manufacturer. This setup allows deeper control and direct interaction between the device and Keka.

• Enables real-time data syncing

• Supports more customization than SQL-based setups

• Requires manufacturer’s SDK

What you need to provide:

• Device-specific SDK

• Network details

3. Push-Based Biometric Integration

In this setup, the biometric device automatically pushes attendance data to Keka without manual intervention. It's one of the most hands-off options available.

• Simplifies data management

• Automatically syncs latest logs

• Ideal for real-time attendance tracking

What you need to provide:

• Network details of the device

• Device push data configuration

4. API-Based Biometric Integration

API integration allows your biometric devices to communicate with Keka via predefined APIs. This is a flexible and scalable method suitable for modern infrastructure.

• Seamless data exchange

• Compatible with a wide range of devices

• Ideal for custom or cloud-based setups

What you need to provide:

• Device manufacturer name

• Number of devices and their names

• Network information

Options & Variants

• SQL-Based: MS-SQL only

• SDK-Based: Requires manufacturer SDK

• Push-Based: Best for hands-free syncing

• API-Based: Most scalable and device-agnostic

Choose the method that best fits your infrastructure and operational preferences.

Notes, Tips, Important, Warnings

Note: Only MS-SQL is supported for SQL-based integrations.

Tip: API and Push-based methods require less ongoing maintenance compared to SQL or SDK-based setups.

Important: Ensure your network firewall and access permissions are configured correctly to avoid data sync failures.

 Click here to view the full list of prerequisites