TABLE OF CONTENTS
Introduction
From tracking leave and attendance to managing payroll, Keka's versatile HRMS solutions are enabling thousands of companies across India. As we expand globally, we are cognizant of the evolving challenges our clients face. One of the most challenging aspects of onboarding a new HRMS system is integrating biometric systems for attendance tracking and access control - a critical component for many organizations. Therefore, we've made it our mission to simplify this complex process and provide diverse options for a seamless biometric integration process.
In this article we'll walk you through the different kinds of integrations we currently support and the various data points we need from you in order to get your systems integrated. As of now, support the following 4 types of Integrations within
- SQL-Based
- SDK-Based
- Push-Based
- API-Based
Let's take a look at each of them in some more detail.
Currently Supported Integrations
SQL-Based Biometric Integration
SQL-based integration is akin to the old faithful of integration methods. Here, your biometric devices sync directly with SQL databases, sending the data right into your SQL database, ready to be accessed and processed by Keka. The standout feature of SQL-based integration is its adaptability. It allows you to tailor the data flow to suit your unique needs. Furthermore, SQL databases are universally compatible, making this approach feasible for almost all devices.
Note: As of now, Keka supports only MS-SQL based integration.
What we need from you:
For this method, we need a few details about your SQL database, device, and network. Once we've set it up, Keka will start tracking your attendance logs. For a specific list of prerequisites, please click here.
SDK-Based Biometric Integration
The Software Development Kit (SDK) based integration employs a unique software kit from the biometric device manufacturers. Compared to an SQL-based integration, SDK-based Integration provides a deeper level of customisation and control over the device. This method also facilitates direct communication between Keka and the device, ensuring swift, real-time data updates.
What we need from you:
To employ SDK-based integration, provide us with the device-specific SDK and network details. We'll handle the rest! For a specific list of prerequisites, please click here.
Push-Based Biometric Integration
Push-based integration is as straightforward as it sounds. Your biometric device 'pushes' the attendance data straight to Keka.This approach has a significant benefit - you are freed from the task of regularly extracting data from the device. The data comes to Keka automatically, ensuring Keka always has the most recent data, with minimal effort from your side.
What we need from you:
For this method, we need the network details of your device, as well as its push data configuration. For a specific list of prerequisites, please click here.
API-Based Biometric Integration
API, or Application Programming Interface, based integration is a highly effective method for biometric integration. This approach involves using specific APIs to facilitate seamless communication between your biometric device and Keka. The power of this method lies in its connectivity. It allows Keka to "talk" directly to your biometric device leading to smooth, quick data updates. It's also a very flexible method of integration that's compatible with a variety of biometric devices.
What we need from you:
To get started with API-Integration, you'll need to provide us the manufacturer name for the devices, no. of devices along with their device names, and your network information. For a specific list of prerequisites, please click here.
Conclusion
Selecting the perfect method of integration is based solely on your organisation's distinctive needs. Each of these methods ensures a seamless, fuss-free experience in managing your workforce. At Keka, we believe in more than just providing solutions; we believe in forging partnerships. We are committed to empowering you with the tools and confidence to harness the full potential of our HRMS.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article