Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration guide

How to Connect eSSL Biometric to Apragya: Devices, Bindings and the Runner

For HR and IT at plants, hospitals and offices with eSSL devices: the setup order that gets punches into attendance without opening your network.

A nurse using a biometric reader while a technician holds a small device

To connect eSSL biometric devices to Apragya, work in this order: register the device in HR, bind biometric IDs to employees, then run the eSSL connector where it can reach your eSSL server. For most sites that is a Tenant Runner on your own network.

Getting the order right matters. Punches that arrive before bindings exist cannot be matched, and a device without its key cannot send anything.

Below are the steps, an illustrative example from Nagpur and the checks for the first fortnight.

How to connect eSSL biometric to Apragya

Register each eSSL device in Apragya HR with its serial number and save the device key it returns. Then map biometric IDs to employees, starting from the device's enrolled users.

Configure the eSSL connector with your eSSL server address, the device serial, the poll interval and the device key, and run it in a Tenant Runner on your network. Watch the first punches arrive and bind any unknown IDs.

  1. Register the device in HR and save its key.
  2. Map biometric IDs to employees.
  3. Install a Tenant Runner on your network.
  4. Configure the eSSL connector with server and device details.
  5. Check the first punches and bind unknown IDs.

Where eSSL setups usually trip

Missing bindings

Punches arrive for IDs nobody has mapped.

Lost device key

The key shown at registration was not saved.

Wrong server address

The runner cannot reach the eSSL server.

Field differences

The eSSL setup uses different field names.

An example: a Nagpur hospital with two gates

Take an illustrative 250-bed hospital with eSSL devices at the staff entrance and the emergency wing, and an eSSL server in its own server room.

What the runner connects

Tenant Runner

Inside the hospital network, outbound only.

  • eSSL server

    Polled for new punches.

  • Staff gate device

    Registered with its own key.

  • Emergency wing device

    Registered with its own key.

  • Bindings

    Seeded from the enrolled user list.

  • HR attendance

    Receives matched punches.

Nothing inside the hospital had to accept a connection from outside.

Bindings were seeded from the device's enrolled list, so night-shift nurses were matched from the first poll. Three agency staff showed up as unknown IDs and were bound the next morning. By the end of the month, the nursing superintendent was planning rosters from attendance she trusted, instead of from the register at the gate.

A small box linked by threads to two readers and a stack of cards
Three agency staff were the only unknown IDs, bound the next morning.

How eSSL device setup works in Apragya

Step 1 of 5

Register

Add the device with its serial; save the key it returns.

  1. Register: Add the device with its serial; save the key it returns.
  2. Seed bindings: List the device's enrolled users and map each biometric ID.
  3. Configure the connector: Enter the eSSL server address, device serial and poll interval.
  4. Run it: Load the connector in a Tenant Runner that can reach the server.
  5. Rotate keys: Rotate a device key if it may have been exposed.

Biometric ID mapping, done right

The mapping is the heart of the setup. A biometric ID can belong to only one employee on a device, and Apragya refuses a clash instead of guessing. Unknown IDs are counted in each batch so gaps are found quickly.

Mapping approaches, compared

FeatureSpreadsheet mappingApragya bindings
SourceTyped by HRSeeded from the enrolled list
ClashesFound at payrollRefused when entered
Unknown IDsDropped silentlyCounted in each batch
New joinersAdded when noticedBound at enrolment

Checked against public information on 16 September 2026.

Why this eSSL server integration is dependable

Outbound only

The runner connects out, so the network stays closed.

Reconnect batches

Punches held during an outage arrive together, without duplicates.

Key per device

Each device authenticates separately.

One employee record

Attendance feeds shifts, overtime and payroll.

Employee view

Staff see their attendance on the phone-friendly app.

Adjustable adapter

Server address and field names set for your install.

Read the eSSL biometric integration overview and attendance.

First fortnight checks

  1. Compare a day's punches with the eSSL software.
  2. Clear the unknown IDs each morning.
  3. Check night shifts that cross midnight.
  4. Confirm payroll reads the same attendance.

eSSL installations vary, so the connector is set up and tested against your own server.

What it costs to start

Free
Up to 3 users
HR included, with CRM and Vendor Onboarding
1,000
AI Credits a month
On the free plan
INR 3,999
Starter, a month
Up to 10 users and 2,000 AI Credits

Connecting eSSL biometric, answered

What poll interval should we use?
Between 30 and 300 seconds is typical; a minute suits most sites.
Can the connector run without a runner?
Only if the eSSL server is reachable from the internet, which is rare.
What if we lose a device key?
Rotate the key for that device and update the connector.
Does the eSSL server need a login?
If it uses basic authentication, add its username and password to the connection.
What does it cost to start?
HR is part of the free plan, which covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter, at INR 3,999 a month, covers up to 10 users, adds a choice of enterprise apps, and is where ready-made AI agents start to run.

Connect one gate this week

Register one device, seed its bindings and let the runner bring in a shift.