Free device check · ~5 minutes

Does your biometric device work with our API? Find out in 5 minutes.

Test any fingerprint, face, palm, or RFID device against the Cams Biometric Gateway. If it's verified, you unlock real-time Native Push. If not, Hybrid Push still connects it. No device left behind.

Verify My Device See how it works
Free · No SDK · No signup · Works with 90+ brands
ZKTeco· eSSL· Suprema· Hikvision· Anviz· Mantra· Realtime ISO 9001 + 27001 GDPR-aligned
Two paths, one API

Every device connects — one way or another

The check decides which path your device takes. Both expose the exact same REST + webhook API to your application, so your integration code never changes.

Verified → Native Push

Native Push API

For devices that talk to the Gateway directly.

  • Sub-second, real-time event delivery
  • All 38 API operations (callback + RESTful)
  • No local connector, no middleware to host
  • Full user, template & device control
  • MCP-ready — AI agents can drive the device
Not verified → Hybrid Push

Hybrid Push API

For legacy, closed-network & non-internet devices.

  • Local connector relays events to the Gateway
  • Protocol Engine Lite for air-gapped / LAN-only fleets
  • Translates legacy protocols to standardised JSON
  • Same API surface your app already consumes
  • Works with 90+ brands out of the box

Bottom line: whatever device your customer owns, it ends up on the Cams Biometric Gateway.

How verification works

Three steps. About five minutes.

No SDK to install, no account to create. Just your device and an internet connection.

01

Describe your device

Tell us the brand, model, and serial number — plus how to reach you with the result.

02

Push a test event

Point the device at the Cams test endpoint and make one punch. The device sends a live event to our server.

03

Get your verdict

Event arrives → Native-Push verified. Doesn't → you're routed to the Hybrid path. Either way, the result is emailed to you.

Start the free check
Why it's worth it

One integration. Every device, every ERP.

Verifying once puts the device on the same gateway that powers attendance, access control, and visitor management for 1,000+ integration partners.

Single REST + webhook API
One interface for every device brand — no per-vendor SDK juggling.
Any ERP / HRMS / payroll
Push events straight into your stack: SAP, Zoho, Odoo, Greythr, custom apps.
MCP-ready for AI agents
Claude, ChatGPT, Gemini can enrol users & manage devices in natural language.
38 operations
Attendance, enrollment, template sync, access windows, device control.
ISO 9001 + 27001 certified
GDPR-aligned. No raw biometric data stored on Cams servers.
No SDK, any language
Raw JSON over HTTPS — PHP, Node, Python, Go, Java, Ruby, C#.
Supported hardware

Bring the device you already have

These brands are tested and known to work. The verification tells you whether yours runs Native or Hybrid — and 90+ more brands connect via Hybrid Push.

ZKTeco Suprema BioStar Hikvision Anviz eSSL Matrix COSEC Morpho / IDEMIA Virdi Nitgen Realtime / Startek Mantra Secugen Biomax Cams Biometrics + 90 more via Hybrid Push
Questions

Before you verify

What does it mean for my device to be "verified"?
Verified means your device can push biometric events directly to the Cams Biometric Gateway in real time — so it qualifies for the Native Push API: sub-second delivery and the full set of 38 API operations, with no local connector.
What happens if my device is NOT verified?
Nothing is lost. Devices that can't push natively connect through Hybrid Push — a local connector (or Protocol Engine Lite for air-gapped / closed networks) that translates the device's protocol into the same standardised JSON the Native API uses. Every device ends up on the same API surface.
Is the device check really free?
Yes. The verification tool is free, needs no signup, and takes about five minutes. You only pay if you go on to activate the API on the device.
Do I need to install an SDK or software?
No SDK. The check is pure device-to-server over HTTP — you just point the device at the Cams test endpoint and make one punch.
What's the difference between Native Push and Hybrid Push?
Native Push is for devices that send events to the Gateway directly — sub-second, no middleware. Hybrid Push is for legacy, closed-network, or non-internet devices — a local connector relays events to the Gateway. Both expose the identical REST + webhook API to your application.
What data do you collect during the test?
Only your contact details (so we can send the result) and the device's brand/model/serial. The test punch is a connectivity check; no raw biometric templates are stored on Cams servers.
Can AI agents control verified devices?
Yes. Once a device is on the Gateway, it's reachable via the Model Context Protocol endpoint at mcp.camsbiometrics.com/mcp, so agents like Claude, ChatGPT, and Gemini can enrol users and manage the device in natural language. See the integration guide.
Which biometric device brands are supported?
ZKTeco, Suprema, Hikvision, Anviz, eSSL, Matrix COSEC, Morpho / IDEMIA, Virdi, Nitgen, Realtime / Startek, Mantra, Secugen, Biomax, Cams Biometrics, plus 90+ other brands via Hybrid Push. Browse the full device catalog.

Verify your device now

Free, no signup, about five minutes. Find out if you're Native-ready — or get your Hybrid path.

Start the free check Read the API docs