---
title: "5. Configuration Guide"
space: "CAMS Biometric Integration"
url: "https://docs.navari.co.ke/cams-biometric/configuration-guide"
updated: "2026-05-27"
---

Configuration happens in two places: the CAMS API Monitor (on the CAMS side) and CAMS Biometric Settings (on your FrappeHR side).



### Step 1: Configure CAMS Biometric Settings in FrappeHR

Navigate to: **HR > Settings > CAMS Biometric Settings** (or use the search bar).



Fill in the following fields:


| Field              | Description                                                                       | Where to find it              |
| ------------------ | --------------------------------------------------------------------------------- | ----------------------------- |
| **Service Tag ID** | Unique identifier for your biometric device on the CAMS platform                  | Your CAMS API Monitor account |
| **Auth Token**     | 32-character authentication token                                                 | Your CAMS API Monitor account |
| **Start Date**     | *(for historical retrieval only)* — Start of the date range for punch log loading | Set manually when needed      |
| **End Date**       | *(for historical retrieval only)* — End of the date range                         | Set manually when needed      |


Save the document after filling in credentials.



### Step 2: Construct Your Callback URL

Your site exposes a single public API endpoint for receiving punch data. The URL format is:



```
https://{your-site-domain}/api/method/navari_cams_biometric.cams_biometric.controllers.cams_call.attendance

```



**Example:** If your site is `https://hr.acmecorp.erpnext.com`, your callback URL is:



```
https://hr.acmecorp.erpnext.com/api/method/navari_cams_biometric.cams_biometric.controllers.cams_call.attendance

```



> **Important:** The endpoint must be accessible over the public internet. If you are running a self-hosted site behind a firewall or on a private IP, you need to configure port forwarding or a reverse proxy. The CAMS Protocol Engine sends punches from their cloud infrastructure, so your site needs to be reachable from external IP addresses on ports 80 (HTTP) or 443 (HTTPS). HTTPS with a valid SSL certificate is strongly recommended.



### Step 3: Configure CAMS API Monitor

1. Log in to your CAMS account at [camsunit.com](https://camsunit.com/) (or the new portal at [camsbiometrics.com](https://camsbiometrics.com/))
2. Navigate to **API Settings** or **API Monitor** for your device
3. Paste your Callback URL into the **Callback URL** field
4. Save the configuration

Once saved, any punch event on the device will immediately trigger a POST request to your Callback URL.



### Step 4: Test the Webhook

You can verify the connection is working by:

1. Having an enrolled employee punch the biometric device
2. In FrappeHR, navigating to **HR > Attendance > Employee Checkin**
3. Checking whether a new record appears within a few seconds

Alternatively, use the FrappeHR error log (**Settings > Error Log**) to inspect any failures.