Which machines the Gateway supports, how each one connects (Native Push or Hybrid Push), and which API operations are available in each mode.
Introduction
Machine Compatibility
The Cams Biometric Gateway supports all biometric attendance and access control machines. The only decision you make is which connection mode suits your setup.
Cams Biometric Machines: SlimBeast (i34), Macronium (i35), Hawking Plus (f38+), Hawking (f38), Ultron MultiFaceFP (f34), Ultron MultiFace (f35), Galaxy (f36), Ultron GPS (f37), CanBio34, GymBio34, RSP10i3, RSP10f1, and more.
Introduction
Connection Modes & API Availability
Every biometric machine connects to the Cams Biometric Gateway through one of two push modes. Your device type determines which mode to use.
Native Push Cams & Verified Devices
All Cams Biometrics machines and devices verified at developer.camsbiometrics.com connect via Native Push. No additional setup needed — the device communicates directly with the Biometric Gateway over the internet.
Full API support. All 38 operations work with no limitations — both Callback and RESTful APIs. Zero latency on callbacks, ~15 seconds for RESTful commands.
Hybrid Push All Other Machines
For non-Cams and non-verified machines, you choose a Hybrid Push connection mode that suits your environment. The combination of communication method and deployment topology determines which API features are available.
Communication Methods
(a) Device SDKThe Gateway communicates with the hardware via the device manufacturer's SDK. All features the SDK supports are available through the API. Best option for full API access.
(b) DB PullThe Gateway reads from a local database installed on the site computer (where the device software stores attendance). Only attendance/punch log push to your server is supported. No RESTful APIs (no add/delete user, no load log, etc.).
(c) File ProcessingA designated attendance file on the local computer is placed under continuous surveillance. Every time the file is updated by the device software, new attendance records are automatically detected, pulled, and pushed to your Callback URL in real time. Same API limitations as DB Pull -- attendance push only, no RESTful APIs.
Deployment Topologies
(X) DirectThe site computer has a public IP with port forwarding to the local network. The Biometric Gateway connects to the device/DB/files directly over the internet.
(Y) IndirectA Hybrid Connector is installed on the local computer. It acts as a bridge between the local machine/DB/files and the Biometric Gateway — no public IP required on the customer side.
Hybrid Push — Feature Availability Matrix
Mode
Communication
Topology
Callback API
RESTful API
Direct Device
(a) SDK
(X) Public IP
Full
Full (SDK limits)
Indirect Device
(a) SDK
(Y) Hybrid Connector
Full
Full (SDK limits)
Direct DB
(b) DB Pull
(X) Public IP
Attendance only
Not supported
Indirect DB
(b) DB Pull
(Y) Hybrid Connector
Attendance only
Not supported
Direct File
(c) File
(X) Public IP
Attendance only
Not supported
Indirect File
(c) File
(Y) Hybrid Connector
Attendance only
Not supported
Which mode should I choose? If your non-Cams device has an SDK supported by the Gateway, choose Device SDK mode (a) for full API access. If not, DB Pull (b) or File Processing (c) will still get attendance data flowing. For topology, choose Indirect (Y) with Hybrid Connector if you cannot set up a public IP — it is the easiest to deploy.
Hardware limitations may further restrict API features. Even in Device SDK mode, specific APIs may not function depending on the device model's firmware or SDK capabilities. Always test with your hardware and verify with the Cams support team.
