Now Live — Works with Claude, ChatGPT, Gemini

The Secure Biometric Gateway

One secure API that streams real-time biometric events from any device brand to any AI workflow, ERP, or application. Encrypted in transit and at rest. No SDK. No vendor lock-in.

Explore the API Email Sales See 100+ partners
Rated 4.5 out of 5 stars Excellent · 29 reviews on

ISO 9001:2015 certified · Verify

80000+
Machines
100+
Partners
11000+
Clients
104+
Countries

Live active customer base · refreshed monthly

ISO 9001:2015 certified GDPR-aligned No raw biometric data on Cams servers TLS in transit · AES-256 at rest Full policy →
★★★★★ Rated Excellent on Trustpilot →

100% Global Device Compatibility — Works with every major brand

Why Biometric Gateway

One gateway ends the integration chaos

Every biometric vendor ships a different SDK, protocol, and data format. Integrating even two brands is months of work. Cams Biometric Gateway solves this at the infrastructure layer.

Without a Gateway

  • A different SDK per vendor — ZKTeco, Suprema, Hikvision each require separate integration code
  • Proprietary binary protocols — impossible to standardize without deep reverse-engineering
  • Vendor lock-in — switching hardware means rewriting your entire attendance stack
  • No AI access — biometric data stays trapped inside legacy middleware
  • On-premise only — no cloud streaming, no real-time webhooks, no REST API

With Cams Biometric Gateway

  • One REST API for all devices — ZKTeco, Suprema, Hikvision, and 90+ brands unified
  • Standardised JSON payloads — every punch, enrollment, and command in the same schema
  • Hardware-agnostic architecture — swap devices without touching your application code
  • MCP-ready — connect Claude, ChatGPT, Gemini directly to your biometric infrastructure
  • Cloud-native real-time streaming — sub-second push events, no polling required
Now Available — AI & MCP

Your AI agents can now control biometric machines

Connect Claude, ChatGPT, Gemini, Copilot, or any MCP-compatible AI agent to the Biometric Gateway. Manage thousands of devices, enroll users, and stream attendance — all through natural language.

MCP Endpoint

https://agent.camsbiometrics.com

n8n / Make / Zapier workflows

Trigger biometric operations from any automation platform

50 devices in 10 seconds

Mass enroll, block, or sync users across your entire fleet instantly

Claude (MCP) ChatGPT Gemini CLI Copilot Studio Perplexity n8n Make Zapier Power Automate Claude Code Cursor VS Code / GitHub Copilot
agent.camsbiometrics.com
$ Connector URL: https://agent.camsbiometrics.com
✓ Connected to Biometric Gateway
✓ 847 devices online · 104 countries · 1M attendance records a day
AI> "Show all offline devices in Dubai"
Found 3 offline devices in Dubai, UAE:
· Device #DXB-0412 — Al Barsha Hub (offline 2h 14m)
· Device #DXB-0891 — Downtown Office (offline 14m)
· Device #DXB-1203 — JBR Marina (offline 6m)
AI> "Enroll John Smith on all 3 Dubai devices"
✓ Enrollment queued for DXB-0412, DXB-0891, DXB-1203
✓ Biometric templates syncing... completed in 38 seconds
✓ Access granted on 3 devices
# 50+ devices managed in < 10 seconds via natural language

Read the Claude AI integration guide →

Quick Start

Live in three steps · under 30 minutes

No SDK. No vendor calls. Pure HTTP — works with any language, any environment, any biometric device brand.

01

Plug in your device ~8 min

Check your device for free at developer.camsbiometrics.com. Cams machines and verified devices (ZKTeco, eSSL, Suprema, Hikvision, Anviz, Morpho and more) connect by Native Push: real-time, no local connector. Any other device connects by Hybrid Push.

02

See your first event ~min 12

First punch hits your callback URL within minutes. Standardised JSON across every device brand — attendance, punch photos, user changes — same schema. Wire it to your webhook, log it, sync your DB, fire a Slack message. Done.

03

Ship the workflow ~min 30

Use 27 RESTful commands to enroll users, block access, sync templates, retrieve logs. Or hand it to Claude / ChatGPT / Gemini via MCP and manage the whole fleet through natural language. From zero to production workflow in your first half-hour.

API Reference

38 operations.
Zero SDK.

All payloads are raw JSON over HTTPS. Works with PHP, Node.js, Python, Go, Java, Ruby — any language that can make an HTTP request.

Callback APIs (11) — Device → Server
  • Real-time attendance punch
  • Photo capture on punch
  • User deleted on the device
  • Date/time modification
  • User updated (no template)
  • Card updated
  • Password updated
  • Fingerprint updated
  • Face updated
  • Palm updated
  • User photo updated
RESTful APIs (27) — Server → Device
  • Add user (single / batch)
  • Delete user / all users
  • Enable / disable access
  • Fingerprint enrollment
  • Add user with face template
  • Add user with palm template
  • Update access time window
  • Load attendance logs
  • Device info & capacity
  • Clear logs / photos
  • Resend missed data
  • + 16 more operations
Fingerprint Face Recognition Palm Vein Iris RFID / NFC QR Code GPS Tracking Temperature
Sample — Attendance Callback (Device → Your Server) ● LIVE 
{
  "RealTime": {
    "OperationID": "9nu1wak5616p",
    "LabelName": "Burj Khalifa",
    "SerialNumber": "ZHM11xxxxxxxx",
    "PunchLog": {
      "Type": "CheckOut",
      "Temperature": "36.8",
      "FaceMask": false,
      "InputType": "Fingerprint",
      "UserId": "2",
      "LogTime": "2026-10-28 09:14:07 GMT +0530"
    },
    "AuthToken": "COJJ7eiiPBGUfmIQPvh2PJWWDLX7OuKs",
    "Time": "2026-10-28 03:44:08 GMT +0000"
  }
}
Full API Docs Device Compatibility
99.95%
Uptime SLA
≤250ms
Webhook latency
30-day
Retry queue · zero loss
24×7
Security monitoring
90+
Device brands · one API
In Production

What partners are running on Cams

Anonymized snapshots from across the network — magnitudes drawn from live partner deployments.

4,000+

An HRMS partner running biometric attendance across SMBs in 3 regions

India, MENA, and Africa — one Cams integration, customers buying whatever device brand is locally cheapest. Zero device-driver work on the partner side.

HRMS · multi-region
1,200+

A school-management platform deployed biometric check-in in 8 months

Campuses live across primary, secondary, and tertiary education. Push events to the partner's webhook directly — no polling, no per-vendor SDK juggling.

School · push webhooks
850+

A regional payroll vendor onboarded enterprise customers with zero device-side code

User-management + attendance log retrieval over REST. Customer keeps their existing hardware. Partner shipped the integration in 2 weeks of engineering time.

Payroll · REST-only
Integration Ecosystem

Connects to your entire stack

Integration modules for leading ERP, HRMS, payroll, and AI workflow platforms.

ERP / HRMS / Payroll

Zoho People ERPNext SAP Odoo MS Dynamics BayZat OrangeHRM PalmHR RazorPay Payroll

AI Workflow Platforms

n8n Make Zapier Claude (MCP) ChatGPT Gemini Copilot Studio Perplexity Power Automate Cursor VS Code / GitHub Copilot

Use Cases

Attendance & Payroll
Access Control
Fleet & Vehicle Auth
Asset Tracking
School Management
Healthcare & Labs
Our Partner Network

Trusted by 100+ integration partners worldwide

ERP vendors, HR platforms, system integrators and consultants — across 104+ countries.

Transparent Pricing

Simple, device-based pricing

Price ranges per device. One-time activation + low annual renewal. No per-transaction fees. No user-count limits.

Most Popular
Cams & Verified Devices

Native Push

Cams Biometrics machines and any device verified at developer.camsbiometrics.com — ZKTeco, eSSL, Suprema and more. Full REST API + real-time callbacks, no local connector.

$120–144 one-time
activation · then $60–$72 /yr per device
  • All 38 API operations
  • Sub-second real-time push
  • Full user & biometric management
  • MCP / AI agent access
  • Protocol Update, if your device needs it: $120–$300
Get Started

Check your device free →

Any Other Device

Hybrid Push

Devices that are not verified, including legacy and LAN-only machines, connect through the device SDK, the attendance database or an attendance file — directly or via the Hybrid Connector.

$80–96 /yr per device
No activation fee · Hybrid Connector + licence only
  • Works with any device brand
  • 6 hybrid connection modes
  • SDK mode: attendance + user management
  • Database / file mode: attendance only
  • No activation fee
Get Started

Hybrid Connector: $300–$360 one-time

Enterprise

Protocol Engine Lite

On-premise deployment for LAN-only environments, air-gapped networks, or large-scale self-hosted biometric infrastructure.

$500– $10,000
Based on scale · Contact sales for custom quote
  • On-premise / LAN deployment
  • Air-gapped network support
  • Dedicated support SLA
  • Custom protocol adapters
  • White-label available
Talk to Sales
About Cams Biometrics

Built by Dheeram Innovations Pvt Ltd · since 2016

Chennai, India · LinkedIn →

80K+
Devices
11K+
Customers
104
Countries
As featured in
Insights Success Frontman of the Biometric Industry
Frequently Asked

Common questions

The questions buyers and partners ask most often. Want a deeper answer? email sales.

Does Cams Biometrics store our customers' biometric data?

No raw biometric data is stored on Cams servers. Templates live on the devices themselves and on your customer's server. Encrypted mathematical representations pass through our Gateway temporarily for synchronization, and transaction queues retain delivery data for up to 30 days. Nothing biometric is permanently stored on our side.

Full details in the privacy policy §3.3 and §6.

Which biometric device brands are supported?

Cams Biometrics machines and every device verified at developer.camsbiometrics.com connect by Native Push: real-time, all 38 API operations, no local connector. Verified brands include ZKTeco, eSSL, Suprema BioStar, Hikvision, Anviz, Matrix COSEC, Morpho / IDEMIA, Virdi, Nitgen, Realtime / Startek, Mantra, Secugen and Biomax. Any other device connects by Hybrid Push, so 90+ brands work through one API.

If your device speaks HTTP or has any documented protocol, we can integrate it. Customers buy whatever hardware is locally available; one Cams integration covers them all.

How long does integration take?

First attendance event flowing into your callback URL in under 12 minutes. Full production workflow shipped in under 30 minutes. No SDK installation, no vendor negotiations — just HTTP and a webhook.

See the API documentation for the exact sequence, or jump to the three-step walkthrough above.

What does it cost?

Device-based price ranges (USD) with a one-time cost plus a low annual renewal:

· Native Push (Cams and verified devices): $120–$144 activation + $60–$72/yr per device; Protocol Update $120–$300 if the device needs one · tier details

· Hybrid Push (any other device): no activation fee; Hybrid Connector $300–$360 one-time + $80–$96/yr per device

· Enterprise (Protocol Engine Lite): $500–$10,000 scale-based, on-premise / air-gapped

No per-transaction fees. No user-count caps.

Do I need to host my own server?

No — Cams Biometric Gateway is fully cloud-hosted. You only need a publicly reachable webhook URL on your side.

For air-gapped / LAN-only / on-premise deployments, Protocol Engine Lite runs locally on Windows or Linux and syncs with the Gateway when reachable. Same API, deployed on your hardware.

Is the platform secure?

ISO 9001:2015 certified. GDPR-aligned (plus regional data-protection frameworks where applicable). TLS encryption in transit, AES-256 at rest. RBAC, 24×7 security monitoring, audit logging on every biometric transaction.

The Gateway is built as a pass-through, not a data lake — raw biometric data never lands on our servers. Full posture in the privacy policy.

Can AI agents (Claude / ChatGPT / Gemini) control biometric machines?

Yes. The Gateway exposes an MCP endpoint at https://agent.camsbiometrics.com. Claude, ChatGPT, Gemini CLI, Microsoft Copilot Studio, Perplexity, n8n, Make, Zapier, Power Automate, Claude Code, Cursor and VS Code / GitHub Copilot can connect to it and enroll users, manage devices, retrieve attendance logs, and stream events in plain language.

See the Claude integration guide for a worked example.

What if my customers are still using legacy or closed-network devices?

That's exactly what Hybrid Push and Protocol Engine Lite are for. The local connector translates legacy protocols (TCP, serial, vendor-binary) into the same standardised JSON your application already consumes from Native Push devices.

Same API surface, same payload shape — your application code stays unchanged whether the customer has a brand-new face-recognition device on Wi-Fi or a 10-year-old fingerprint reader on a LAN.

Customer reviews

What our customers say

Rated Excellent by verified businesses and integrators on Trustpilot.

★★★★★
I spent many times looking for an online solution on the way to manage easily the human resources in my company. Just after two days with the technical team of CAMS, I'm proud now because all my worries are sorted out.
Boris Nzounke Cameroon
★★★★★
Finding a good machine is now a challenge for any organisation in this crowded market. One should choose a machine which has excellent build and fabulous customer support. This is what CAMS Biometrics are known for.
Tarun K. Jain India
★★★★★
We recently purchased two devices from Cams Biometric and had them installed at our location. Your team provided excellent support and helped us integrate the devices with the software. Your prompt assistance and technical guidance made the implementation process seamless.
Admin Golden Bricks United Arab Emirates
Cams Biometrics is rated Excellent on Trustpilot, based on 29 reviews
Read all reviews on Trustpilot →
Get Started

Start building in minutes

Your first biometric event flowing into your application in under 30 minutes. No SDK. No vendor calls. Just HTTP.

API Documentation Community Support sales@camsbiometrics.com

Community Forum  ·  Device Compatibility Check  ·  Instant Code Generator

Try again
Try again