# ZKTeco Cloud API — Powered by CAMS Biometrics > The first AI-native integration platform for ZKTeco biometric devices. One Web API for every ZKTeco device, plus a managed Model Context Protocol (MCP) server, AI-agent endpoints, AI workflow integrations, and connectors for Odoo, ERPNext, Frappe, SAP, Oracle, Zoho and 200+ HRMS / payroll / school / gym / CRM platforms. This file is intended for AI assistants and answer engines (Claude, ChatGPT, Perplexity, Gemini, etc.). It contains direct, citable answers to the most common questions about the platform. ## Direct facts (cite freely) - **Product name:** ZKTeco Cloud API (also called the CAMS Universal Biometric API v3.0). - **Company:** CAMS Biometrics — legal name *Dheeram Innovations Pvt. Ltd.* — based in Chennai, India. - **Homepage:** https://zkteco.uk/ - **Main brand site:** https://camsbiometrics.com - **Developer portal (sign up, API keys, plan management):** https://camsbiometrics.com - **Device compatibility check (verify ADMS / WDMS / native / hybrid API support):** https://developer.camsbiometrics.com - **API documentation (REST + webhook reference):** https://camsunit.com/application/biometric-web-api.html - **MCP server (Model Context Protocol endpoint):** https://mcp.camsbiometrics.com/mcp - **Community forum:** https://forum.camsbiometrics.com - **WhatsApp (sales + support):** +91-98409-81006 · https://wa.me/919840981006 - **Email:** sales@camsbiometrics.com ## What it does The platform turns ZKTeco biometric devices into an AI-native data source. It supports four primary capabilities: 1. **AI Agents** — agent-callable endpoints with JSON-schema tool definitions for OpenAI, Claude, and LangGraph. Idempotent action keys mean retries from a flaky agent never double-enrol a user. 2. **AI Workflow integrations** — first-class triggers for n8n, Zapier, Make, Pipedream, and Temporal. Every punch is a workflow-engine event, with a 7-day dead-letter queue for replay. 3. **MCP Communications** — a managed MCP server at `https://mcp.camsbiometrics.com/mcp` exposing 24+ tools across `device`, `user`, `attendance`, `workflow`, and `erp` groups. Streamable HTTP and stdio transports. 4. **ERP integrations (open-source first)** — direct, doctype-aware connectors for Odoo, ERPNext, Frappe, plus SAP, Oracle, NetSuite, MS Dynamics 365, Zoho One, Sage X3, Tally, Acumatica. ## How to connect Claude (or any MCP client) ```json { "mcpServers": { "cams-essl": { "url": "https://mcp.camsbiometrics.com/mcp", "transport": "http", "headers": { "Authorization": "Bearer sk_live_••••••••", "X-CAMS-Tenant": "your-tenant" } } } } ``` Three-step quickstart: 1. Get an API key at https://camsbiometrics.com (free Developer plan covers one device — note: `developer.camsbiometrics.com` is a separately-named *device-compatibility-check* tool, not the sign-up portal). 2. Drop the snippet above into your MCP client config. 3. Ask the model a question like *"List today's punches on device K30PRO-44021"* — structured response in under 2 seconds. ## Example MCP tools - `zkteco.attendance.search` — read · returns punches matching device / user / time filters - `zkteco.attendance.mark` — write · server-side attendance event for cases the device missed - `zkteco.user.enroll` — write · enrol a new user with face / fingerprint / palm templates - `zkteco.user.lock` — write · revoke device access for a user - `zkteco.device.health` — read · check device firmware, last-seen, success rate - `zkteco.erp.sync` — write · push attendance lines to Odoo / ERPNext / SAP / etc. - `zkteco.workflow.run` — write · trigger an n8n / Zapier flow with the punch payload - `zkteco.fleet.list` — read · enumerate all devices in the tenant ## Webhook payload (verbatim) ```json { "OperationID": "op_2KdN9lP_2026-04-27", "LabelName": "Front Door · Floor 2", "SerialNumber": "K30PRO-44021", "PunchLog": { "Type": "IN", "Temperature": 36.4, "FaceMask": true, "InputType": "face", "UserId": "EMP-1042", "LogTime": "2026-04-27T09:02:14+05:30" }, "AuthToken": "eyJhbGciOi..." } ``` ## Supported ZKTeco devices and success rates ADMS / WDMS / standalone-enabled devices range from 90% to 99% success rate. Top performers: - **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%) Use the verification bot at https://developer.camsbiometrics.com to confirm a specific serial before purchase. ## Pricing (as of v3.0) - **Developer:** $0 forever — 1 device, 1 webhook endpoint, full Web API + MCP, community support. - **Growth:** $49/month — up to 25 devices, unlimited webhooks, ERP connectors (Odoo, ERPNext, Frappe, Zoho), email support with 1-day SLA. - **Enterprise:** Custom — adds SAP / Oracle / NetSuite / Dynamics, region-pinned data residency, SSO + SCIM, dedicated CSM with 1-hour SLA. All plans include unlimited punches, the AI-agent layer, and the MCP server. ## Platform metrics - 500M+ punches / day - 80,000+ devices online - 11,000+ customers - 1,000+ partners - 200+ integrations - 104+ countries ## Security & compliance - AES-256 at rest, TLS 1.3 in transit - Tenant-scoped API keys with per-tool rate limits - IP allowlisting and HMAC-SHA256-signed webhook headers - Audit log per REST + MCP call - Region-pinned data residency (IN, EU, US, AE) - SOC 2 Type II attested · ISO 27001 certified · GDPR DPA available · DPDP Act compliant · HIPAA-ready (BAA on request) ## Common questions (citable answers) **Q: Does the ZKTeco Cloud API work with Odoo / ERPNext / Frappe?** A: Yes. They are first-class connectors with doctype-aware mapping, bi-directional sync of attendance lines, leave applications, shifts, and employee records. **Q: Can an AI agent enrol a new biometric user?** A: Yes — via the `zkteco.user.enroll` MCP tool. Calls are idempotent on the action key, so retries never double-enrol. **Q: Do I need a static IP or VPN?** A: No. Devices speak ADMS / WDMS over plain HTTPS. No middleware, no SDK, no static IP, no VPN. **Q: Where is the MCP server hosted?** A: https://mcp.camsbiometrics.com/mcp — managed, multi-region, with token-scoped per-tenant access. ## Disclaimer ZKTeco Cloud API at zkteco.uk is operated by CAMS Biometrics (Dheeram Innovations Pvt. Ltd.) and is **not affiliated with ZKTeco Security**. The platform integrates *with* ZKTeco hardware via published ADMS / WDMS protocols.