Biometric attendance machine integration with Keka

Keka runs attendance and payroll for many growing Indian companies, and its attendance is only as good as the punches it receives. This page explains how every punch from your fingerprint or face machines reaches Keka on its own.

Keka

Where the punches have to go

Keka is an HR and payroll platform popular with Indian businesses. Attendance can come from its app, the web and biometric machines. With machines, the hard part is getting punches out of every terminal reliably, across offices, without a PC that someone forgets to switch on.

An integration removes the file in the middle: every punch travels from the terminal to the Cams cloud and on to Keka by itself, from every site, whatever the terminal brand.

What reaches Keka

Punch by punch

Every punch is sent to Keka as it happens, in the Cams 3.0 format that Keka accepts, so Keka's attendance policies (shifts, late marks, overtime) work on live data.

  • The user ID of the person who punched
  • Punch date, time and type
  • The terminal it came from

Setup

How to connect Keka

Connect the terminals to the Cams cloud

Cams terminals connect out of the box. For terminals you already own, check the model for free at developer.camsbiometrics.com: supported models connect directly over the internet, older ones as a Cams Open Terminal.

Line up the employee IDs

Keka links each punch to an employee through the attendance ID it holds for that person, so keep the user ID on the terminal the same as that ID in Keka. Keka can confirm which field it uses for your account.

Add Keka in the Cams console

Open Configurations, then Connectors, add Keka and enter what it asks for (list on the right). Choose which terminals send to it.

Punches flow

From then on every punch reaches Keka, usually within a minute. Failed deliveries are retried and listed in the console, so problems are visible instead of silent.

What you need

  • The callback address Keka gives you
  • An authentication token and a security key, also from Keka

Good to know

  • Ask Keka to set up the biometric integration on their side first: they issue the address and keys.
  • Terminals in every branch can send to the same Keka account.

Hardware

Which attendance machines work with Keka

Every Cams terminal, and terminals from ZKTeco, eSSL, Hikvision, Suprema, Anviz and many of the 90+ other brands that connect to the Cams cloud. Fingerprint, face, palm and card punches all reach Keka in the same form, so you can mix technologies and brands across sites.

Choosing new terminals? Start with the types of attendance machine. Keeping the ones you have? See connecting existing machines to the cloud.

Set it up with Cams

The Keka integration is one of 70+ ready-made integrations on the Cams Biometric Gateway. The page on camsbiometrics.com lists every field, the licence that applies and the price.

FAQ

Keka attendance integration: questions

Where do I get the Keka address and keys?

From Keka. Once Keka sets up the biometric integration for your account, they give you the callback address, an authentication token and a security key. You enter them once in your Cams console.

Will my existing eSSL machines work with Keka?

In most cases, yes. Check the model for free at developer.camsbiometrics.com. Supported models connect straight to the Cams cloud; older or LAN-only models connect through the Hybrid Connector, a small program on a PC on site. Either way the Keka integration takes the punches from there. See keeping the machines you have.

Do punches from several offices go to the same Keka account?

Yes. Every terminal on your Cams account can send to the same Keka integration, whichever city it is in, and you choose which terminals take part.

What does it cost?

Each terminal needs a Cams API licence: a one-time activation plus a yearly fee, with no per-employee or per-punch charge. Some integrations are included with that licence and some are paid; the Keka page on camsbiometrics.com shows which applies and the price.