Unified Biometric API Integration

Connect biometric hardware directly to your web application via RESTful endpoints. Eliminate middleware and local SDK dependencies for real-time attendance syncing.

Start Free Trial View API Docs

The Advantage of No-SDK Architecture

Modernizing hardware communication by moving logic from local DLLs to secure Cloud APIs.

Cloud API Integration via Web

Universal Compatibility

Integrate with OpenERP, Zoho, SAP, or custom stacks without OS-specific SDK conflicts.

Stateless Real-Time Operations

Stateless Operations

Push and pull data via JSON. No local drivers or background services required on the client side.

Remote User Management

Remote Provisioning

Enroll or delete users across multiple locations instantly via centralized API commands.

How API Communication Works ( On request)

When an event occurs on the device (Fingerprint/Face scan), the hardware initiates a POST request to your configured Callback URL.

Request Payload Preview
{
  "device_id": "MINOP_001",
  "log_time": "2026-01-08 17:11:00",
  "user_id": "EMP102",
  "punch_type": "CheckIn",
  "auth_mode": "Face"
}
Real-Time Biometric Data Callback

Biometric Callback

Real-time tracking of logs. The device acts as a client, pushing data to your endpoint as soon as it's recorded.

Offline Logic and Data Flow

Offline Persistence

Internal memory stores logs during internet outages and automatically flushes them to your server upon reconnection.

Note: Custom APIs can be developed on a chargeable basis. For detailed requirements, feasibility, and pricing, please connect with our sales team for further clarification.

Direct Communication (Without Intermediary Data Server)

Prefer to receive data without passing it through a third-party data server?

Protocol Engine (Lite version)

Install the Protocol Engine (Lite version) directly on your server (Windows/Linux/Unix). With this setup:

  • Your API endpoints are triggered automatically upon each device punch.
  • Activation costs and license fees apply.
  • Suitable for on-premises/LAN environments with no internet access.

Note:

The protocol engine you need depends on your device brand and model. Engine costs range based on device type and order quantity.

Design Considerations for API-Based Attendance Software

To ensure accuracy and reliability, your cloud-based attendance solution must address:

Handling Offline Punches

Offline Punches

Update attendance status for past dates when offline punches sync after reconnection.

Duplicate Punch Prevention

Duplicate Punches

Ignore repeat punch data (same user, device, timestamp).

Handling Multiple Device Logs

Multiple Devices

Sort all punches within a day before assigning IN/OUT times, as data may arrive out of order from different machines.

Supported Biometric Devices

A wide range of biometric devices support modern web APIs-covering fingerprint, palm, face, card (LHF, UHF, QR Code), and password authentication methods.

Fingerprint Biometric Device

Fingerprint

Palm Biometric Device

Palm

Face Recognition Device

Face

RFID Card Attendance Device

Card (LHF, UHF)

QR Code Attendance Device

QR Code

Password Based Attendance Device

Password

View Complete Device List

MinopCloud Enterprise Support

Contact Us