What is the success rate for ZKTeco devices?

ADMS / WDMS-enabled devices range from 80% to 95%. Top performers: X628 (95%), X990 (95%), B9C (94%), K30 Pro (94%). Run your serial through the verification bot before purchase.

Is there an n8n, Zapier or Make trigger?

Yes — n8n, Zapier, Make, Pipedream and Temporal triggers are all supported. Failed runs land in a 7-day dead-letter queue you can replay manually.

How is access secured?

AES-256 end-to-end encryption, signed bearer tokens, IP allowlisting per tenant, and a per-tool rate limit. Every MCP and REST call is auditable.

New v3.0 · MCP server, AI agents & open-source ERP connectors

ZKTeco devices.
Now AI-native.

The first integration platform that treats your biometric fleet as a first-class tool for AI agents and workflow engines. One Web API for every ZKTeco device — plus a managed MCP server at mcp.camsbiometrics.com/mcp.

Verify your device Add to Claude See how it connects ↓

90–99% success on ADMS / WDMS / standalone No middleware · No SDK · No static IP REST + Webhook + MCP in one platform

How it connects

From scanner to agent in one hop.

The moment a face hits the scanner, the CAMS API receives the punch and fans it out to your AI client (Claude via MCP), your ERP (Odoo, ERPNext, Zoho), and your workflow engine (n8n) — all in under two seconds.

What it looks like in practice

claude · MCP · cams-essl

// Claude calling the ZKTeco fleet via MCP
use_tool("zkteco.attendance.search", {
  since: "2026-04-27T09:00:00+05:30",
  device_serial: "ZKV5L-44021",
  user_id: "EMP-1042"
})

→ 1 punch · IN · 09:02:14 · face · temp 36.4 · mask=true

use_tool("zkteco.user.enroll", {
  device_serial: "ZKV5L-44021",
  user_id: "EMP-1899",
  name: "Asha P.",
  templates: ["face", "finger:R-IDX"]
})

live webhook ZKTeco ZKV5L-44021

POST /your-server/punch

User

EMP-1042

Type

Latency

1.4 s

Triggered →Odoo HR

Triggered →n8n flow

Triggered →Zoho People

Triggered →Slack alert

Trusted by 11,000+ teams in 104+ countries

SAPOracleZohoBambooHRWorkdayOdooERPNextFrappeSalesforceHubSpotQuickBooksADPMindbodyGlofoxFedenaTeachmintKekagreytHRDarwinboxOrangeHRM SAPOracleZohoBambooHRWorkdayOdooERPNextFrappeSalesforceHubSpotQuickBooksADPMindbodyGlofoxFedenaTeachmintKekagreytHRDarwinboxOrangeHRM

500M+

Punches / day

150,000+

Active installations

11,000+

Customers

1,000+

Partners

200+

Integrations

104+

Countries

Platform · v3.0

Four new pillars on top of the
Universal Biometric API.

Until v2, the ZKTeco Cloud API was a webhook + REST gateway. v3 adds the glue layer that modern stacks expect — agents, workflows, MCP, and ERP-native connectors that go beyond polling.

AI Agents

Agent-callable endpoints for enrol, search, mark, lock, sync. Built-in tool schemas for OpenAI, Claude, and LangGraph.

✓ Idempotent action keys
✓ JSON-schema tool defs
✓ Per-agent rate & scope

AI Workflow integrations

First-class triggers for n8n, Zapier, Make, Pipedream, and Temporal. Every punch becomes an event you can orchestrate.

✓ Sub-2s webhook delivery
✓ Replay & dead-letter queue
✓ Pre-built recipes

MCP Communications

A managed MCP server at mcp.camsbiometrics.com/mcp — talk to your ZKTeco fleet from Claude, Cursor, or any MCP client.

✓ Streamable HTTP & stdio
✓ Tools, resources, prompts
✓ Token-scoped per tenant

ERP-native (open-source first)

Direct connectors for Odoo, ERPNext, Frappe — plus SAP, Oracle, NetSuite, MS Dynamics, Zoho. Switch ERPs in minutes.

✓ Doctype-aware mapping
✓ Auto attendance + leave
✓ Bi-directional sync

Quickstart · 3 minutes

From zero to an AI-native attendance fleet — in three steps.

No middleware, no SDK, no static IP. Just an API key, a config line, and a model that suddenly understands your biometric data.

1
Get your API key

Sign in at camsbiometrics.com and copy a tenant-scoped bearer token. Free Developer plan covers one device.
Open developer portal →
2
Register the MCP server

Point your MCP client at https://mcp.camsbiometrics.com/mcp with the bearer token. Works in Claude Desktop, Cursor, Continue and custom clients.
See client config →
3
Try a tool call

Ask the model: "List today's punches on device ZKV5L-44021". Structured response in under 2 seconds — and your audit log records the call.
View example tools →

Why this and not that

Why teams pick the CAMS API over rolling their own.

Most biometric integrations look identical on slides. Look closer at the day-2 reality and the differences are stark.

Capability	CAMS API v3	Vendor portal	Roll your own
MCP server for AI clients	Hosted & managed	—	Build it
AI agent tool schemas	Out of the box	—	Hand-write JSON-schema
Open-source ERP connectors (Odoo, ERPNext, Frappe)	Doctype-aware	CSV export	Build per-doctype
Webhook delivery	< 2 s p95, retry, DLQ	Polling only	DIY queue
Static IP / VPN required	No	Often yes	Often yes
ZKTeco firmware coverage	ADMS + WDMS + Standalone	ADMS only	Pick one
Audit log per tool call	Built-in	Limited	Build it

Deployment

Native Push or Hybrid — match your network reality.

Devices on the open internet push to us directly. Devices behind a firewall, in an air-gapped facility, or on legacy hardware go through one of four hybrid modes — same Web API, same MCP server, same downstream integrations.

Recommended

Native Push

Direct cloud webhooks. No middleware.

Modern devices speak HTTPS directly to the CAMS API the moment a face hits the scanner. The fastest, simplest, lowest-touch deployment — works for most fleets on the open internet.

Latency: < 1 s
Bandwidth: 10–50 Kbps
Setup: Plug & play

Hybrid Push For firewalled, air-gapped, regulated, or legacy stacks

Mode A

Hardware port forwarding

Edge router forwards the device port to our cloud relay. Good for fixed-IP corporate offices with a friendly network team.

~30 s Router rule

Mode B

Database port forwarding

The vendor's local DB is exposed through NAT. We poll the attendance records and ship them onward.

~30 s Vendor SDK

Mode C

Hardware local service

A small helper on a LAN box pulls from devices and ships outbound only. Air-gap and SCIF friendly.

~30 s 1 helper VM

Mode D

Database local service

A local helper queries the vendor DB and forwards. For HIPAA / regulated stacks that can't open inbound ports.

~30 s DB-aware

In production Where these modes are running today

National retail chain: 500+ stores · Native Push
Manufacturing facility: Air-gapped · Mode C
Multi-branch corporate: 50 branches · Mode A
Healthcare campus: HIPAA · Mode D
Government installation: SCIF · Mode C

Architecture write-up: Universal Deployment — 100% global device compatibility on the CAMS Biometrics forum.

Engineering foundations

Everything the v2 API was famous for — still here, sharper.

The fundamentals that the AI layer rides on top of: real-time delivery, hard security, offline survivability.

⚡

Real-time sync

Sub-2 second delivery, webhook callbacks, zero polling overhead.

🔒

Enterprise security

AES-256 encryption, token authentication, IP whitelisting.

🌐

Cloud-ready

HTTP / HTTPS, no VPN required, worldwide reachability.

👥

User management

Remote operations, template management, bulk updates.

📦

Offline support

Local storage, auto-recovery on reconnect, zero data loss.

🌡️

Health screening

Temperature capture, mask detection, compliance flags.

Industries

Built for any place where presence matters.

Same API, same MCP server. Different schema-aware ERPs and HRMS on the other end.

🏭

Manufacturing

Shift-board sync, line-level access, contractor in/out.

🏥

Healthcare

HIPAA-aware audit, multi-shift nursing, lab access.

🎓

Education

Student attendance, parent alerts, exam-hall verification.

🛒

Retail

Multi-store roster, regional manager dashboards.

🚚

Logistics & fleet

Driver biometric ignition, GPS-tagged punches.

🏨

Hospitality

Casual-rate tracking, supplier check-in, kitchen access.

🏛️

Government

Department-level audit, secure room access, citizen kiosks.

🏋️

Gym & clubs

Member check-in, RFID + face combo, class drop-ins.

Hardware

Supported ZKTeco devices

90–99% success rate across ADMS / WDMS / standalone-enabled devices. Verify yours in 30 seconds with our free bot before purchase.

Verify a device

Face recognition

SpeedFace V5L 99%
SpeedFace V4L 97%
ProFace X 96%
ProFace X (HID) 95%
UFace 802 94%
UFace 800 93%
iface 880 91%
F18 Pro 90%

Fingerprint

F18 99%
F19 97%
IN02-A 96%
S922 95%
K50 94%
K40 93%
F22 91%
KF Reader 90%

Palm recognition

SpeedPalm 100 99%
SpeedFace V5L (Palm) 97%
ProFace X (Palm) 95%
MultiBio 800 92%
MB560 90%

Time attendance

iClock 980 99%
iClock 880 97%
SenseFP 96%
ZK Zpad Plus 95%
iClock 360 94%
F18 92%
K50 91%
K40 90%

Access control

InBio Pro Plus 460 99%
InBio Pro Plus 260 97%
InBio Pro Plus 160 96%
C3-400 Plus 95%
C3-200 Plus 93%
C3-100 Plus 92%
AI Control Panel 91%
CVEdge 160 90%

Don't see your model?

If your ZKTeco device runs ADMS, WDMS, or standalone firmware, it almost certainly works. Verify your specific serial in 30 seconds before you buy.

Run compatibility check →

Success rates vary by firmware version and region. Verify your specific device using our free verification bot before purchase to confirm ADMS/WDMS compatibility.

ZKTeco coverage

Every ZKTeco family on one API.

Face, fingerprint, multi-biometric, palm, access control — across ADMS, WDMS, and the older standalone protocol. One Web API and one MCP server cover the whole ZKTeco lineup, including legacy hardware that's no longer being updated by the manufacturer.

Firmware versions

ADMS · WDMS · Standalone — full coverage of the ZKTeco firmware tree.

Network protocols

TCP/IP · HTTPS / TLS 1.2+ · WebSocket · HTTP/2 · RS232 · RS485 · Wiegand.

On-device storage

50,000 – 100,000 records buffered locally with auto-flush on reconnect — no manual sync ever.

Architecture write-up: Universal Deployment — 100% device compatibility.

200+ integrations

One API. Any ERP. Any tool.

ERP first — including the open-source stack the rest of the industry quietly skips. Then HRMS, payroll, school, gym, CRM. Switch ERPs in minutes, not months.

ERPcommercial & open-source

Odoo

ERPNext

Frappe

SAP

Oracle

NetSuite

MS Dynamics 365

Zoho One

Sage X3

Tally

Acumatica

+ 25 more

HRMS

SAP SuccessFactors

Oracle HCM

Workday

Zoho People

BambooHR

Keka HR

Darwinbox

greytHR

OrangeHRM

SeamlessHR

PeopleStrong

+ 30 more

Payroll

QuickBooks

ADP

Paychex

Gusto

RazorpayX

Sage

CRM

Salesforce

HubSpot

Zoho CRM

Dynamics 365

Pipedrive

Freshsales

School

Fedena

Teachmint

ClassPlus

SchoolLog

MyClassCampus

Edunext

Gym

Mindbody

Glofox

Zen Planner

PerfectGym

GymMaster

Vagaro

MCP & AI agents

Plug your ZKTeco fleet into any AI client.

The CAMS MCP server is live at https://mcp.camsbiometrics.com/mcp. It exposes attendance, enrolment, device, and ERP-sync as native Model Context Protocol tools. Connect it from Claude, Cursor, Continue, or roll your own client — your model can read punches, enrol users, and trigger ERP-sync the moment a face hits a scanner.

✓ 24+ MCP tools across device · user · attendance · workflow · erp
✓ Streamable HTTP and stdio transports — works with hosted & local clients
✓ Token-scoped per tenant with per-tool rate limits
✓ Audit trail for every tool call (who, when, which device)

Add to Claude Get an API key Read the API spec

~/.claude/mcp.json

{
  "mcpServers": {
    "cams-essl": {
      "url": "https://mcp.camsbiometrics.com/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer sk_live_••••••••",
        "X-CAMS-Tenant": "acme-corp"
      }
    }
  }
}

curl · MCP HTTP transport

# list tools
curl https://mcp.camsbiometrics.com/mcp \
  -H "Authorization: Bearer sk_live_••••" \
  -H "X-CAMS-Tenant: acme-corp" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

.cursor/mcp.json

{
  "cams-essl": {
    "url": "https://mcp.camsbiometrics.com/mcp",
    "headers": { "Authorization": "Bearer sk_live_••••" }
  }
}

Tools exposed (excerpt)

zkteco.attendance.searchread

zkteco.attendance.markwrite

zkteco.user.enrollwrite

zkteco.user.lockwrite

zkteco.device.healthread

zkteco.erp.syncwrite

zkteco.workflow.runwrite

zkteco.fleet.listread

n8nrecipe

Punch → Odoo HR + Slack

When a face is recognised on any X990, write the attendance line in Odoo and ping the floor manager in Slack if it's the first IN of the shift.

Zapierrecipe

New hire → enrol everywhere

When BambooHR creates a new employee, automatically enrol them across every door scanner in their location and add to the right ERP cost-centre.

Claudeagent

Agent-driven shift audit

Ask Claude "anyone clocked in but didn't badge into the lab today?" — it queries the MCP, cross-references door logs, and replies with the list.

REST · webhook · MCP

Developer-friendly by default.

Real-time attendance pushed to your server via signed HTTP POST. Same payload shape on every device family. No polling, no SDK, no static IP, no VPN.

Latency: < 2 s p95
Auth: Signed token + IP allowlist
Encryption: AES-256 end-to-end
Replay: 7-day DLQ + manual retrigger

View API documentation

POST /your-server/punch

{
  "OperationID":  "op_2KdN9lP_2026-04-27",
  "LabelName":    "Front Door · Floor 2",
  "SerialNumber": "ZKV5L-44021",
  "PunchLog": {
    "Type":        "IN",
    "Temperature": 36.4,
    "FaceMask":    true,
    "InputType":   "face",
    "UserId":      "EMP-1042",
    "LogTime":     "2026-04-27T09:02:14+05:30"
  },
  "AuthToken": "eyJhbGciOi..."
}

curl

curl https://api.camsbiometrics.com/v3/attendance/search \
  -H "Authorization: Bearer sk_live_••••" \
  -G --data-urlencode "device_serial=ZKV5L-44021" \
     --data-urlencode "since=2026-04-27T09:00:00+05:30"

python

import requests
r = requests.get(
  "https://api.camsbiometrics.com/v3/attendance/search",
  headers={"Authorization": "Bearer sk_live_••••"},
  params={"device_serial": "ZKV5L-44021",
          "since": "2026-04-27T09:00:00+05:30"},
)
print(r.json())

node

const r = await fetch(
  "https://api.camsbiometrics.com/v3/attendance/search?device_serial=ZKV5L-44021",
  { headers: { Authorization: "Bearer sk_live_••••" } }
);
console.log(await r.json());

Security & compliance

Built for the security review you'll have to pass.

Biometric data is sensitive by definition. The platform is designed so that auditors and CISOs can sign off in days, not months.

✓ AES-256 at rest, TLS 1.3 in transit
✓ Tenant-scoped API keys with per-tool rate limits
✓ IP allowlisting + signed webhook headers (HMAC-SHA256)
✓ Audit log per REST + MCP call (who, when, which device)
✓ Region-pinned data residency (IN, EU, US, AE)

🛡️

SOC 2 Type II

Attested

🇪🇺

GDPR

DPA available

📜

ISO 27001

Certified

🇮🇳

DPDP Act

Compliant

🏥

HIPAA-ready

BAA on request

🏷️

PII redaction

Per tenant

What customers say

Less plumbing, more product.

"We went from polling 40 devices every 5 minutes to a sub-2-second webhook to Odoo HR. The MCP server let our ops AI agent answer attendance questions in Slack on day one."

Vivek M.

Head of IT · 2,400-employee manufacturer

"ERPNext support was the deal-breaker. Every other vendor wanted us to write a Frappe app. CAMS just had it."

Asha P.

CTO · multi-school education group

"The 'add to Claude' button is genuinely magical. The CFO can now ask Claude how many people are in the building right now."

Rahul K.

Founder · 3-floor co-working chain

Pricing

Honest, per-device pricing. Free to start.

No per-punch fees, no per-API-call billing. Pay per device per month, with the AI/MCP/ERP layer included on every plan.

Developer

Forever · 1 device, 1 webhook

✓ Full Web API + MCP
✓ 1 webhook endpoint
✓ Community forum support
✓ All device families
— No SLA

Start free

Docs, forum, status, changelog — all in one place.

📘

API documentation

REST reference, webhook reference, and the full MCP tool catalog with JSON schemas.

Open docs →

💬

Community forum

Ask questions, share workflow recipes, get patterns from teams running the same stack.

Open forum →

📈

Status & uptime

Live status of the API, MCP server, and webhook delivery — with 90-day history.

Open status →

🆕

Changelog

v3.0 ships MCP, AI agents, and Odoo / ERPNext / Frappe connectors. Subscribe for updates.

See changelog →

FAQ

Frequently asked questions

Quick, definitive answers — and the ones search engines and AI assistants quote on the way to recommending us.

What is the CAMS MCP server, and how do I connect it to Claude?

The CAMS MCP server is a managed Model Context Protocol endpoint at https://mcp.camsbiometrics.com/mcp. It exposes 24+ tools across device, user, attendance, workflow, and ERP groups. Add the URL to your MCP client config (Claude Desktop, Cursor, Continue) with your tenant API key as a bearer token, and the model can read attendance, enrol users, and trigger ERP sync against your real ZKTeco devices.

Does this work with Odoo, ERPNext, or Frappe?

Yes — those are first-class connectors. The platform is doctype-aware: attendance lines, leave applications, shift assignments and employee records all sync bi-directionally without you writing glue code.

Can my AI agent enrol a new user?

Yes. The zkteco.user.enroll MCP tool takes a device serial, user id, name and template list. Calls are idempotent on the action key, so retries from a flaky agent never double-enrol.

Can I integrate ZKTeco with my HRMS system?

Yes — SAP SuccessFactors, Oracle HCM, Workday, Zoho People, BambooHR, Keka, greytHR, Darwinbox and any custom HRMS via signed webhooks pushed in under 2 seconds.

What's the success rate for ZKTeco devices?

ADMS / WDMS / standalone-enabled devices land at 90–99%. SpeedFace V5L (99%), iClock 980 (99%), InBio Pro Plus 460 (99%), F18 (99%) and SpeedPalm 100 (99%) are at the top. Run your serial through the verification bot before you buy.

Is there an n8n / Zapier / Make trigger?

All three, plus Pipedream and Temporal. Every webhook event is also a workflow trigger; failed runs go to a 7-day dead-letter queue you can replay manually.

Does this work with gym, school, or fleet software?

Yes — Mindbody, Glofox, Zen Planner, PerfectGym for gyms; Fedena, ClassPlus, Teachmint, SchoolLog for schools; and the fleet stack via the GPS / asset-tracking API.

Do I need a static IP, VPN, or SDK?

None of the above. The device speaks ADMS/WDMS over plain HTTPS; we handle the hard parts. No middleware to install, no SDK to maintain.

Which ZKTeco firmware versions are supported?

Both ADMS (Advanced Device Management System) and WDMS (Web-based Device Management System) firmwares are supported across the ZKTeco lineup at 90–99% success. Older fingerprint-only models on the standalone protocol can be brought online via Hybrid Push Mode A or C.

Is there a free tier?

Yes. The Developer plan is free forever for one device and one webhook endpoint. Paid plans start at $49/month (Growth) and Enterprise is custom-quoted.

Stay updated

New tools, new connectors, every fortnight.

A short, no-spam email from the engineering team — what shipped, what's about to, and the most useful workflow recipe of the week.

Ready to make your ZKTeco fleet AI-native?

Join 11,000+ customers in 104+ countries already shipping 500M+ punches a day through the CAMS API.

Verify your device Add to Claude Talk to sales

ZKTeco devices. Now AI-native.