--- title: "Kisi Access Control Integration" slug: "kisi-access-control" updated: 2026-11-11T11:38:09Z published: 2026-11-11T11:38:09Z canonical: "docs.hunters.ai/kisi-access-control" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.hunters.ai/llms.txt > Use this file to discover all available pages before exploring further. # Kisi Access Control Integration ## TL;DR | Supported data types | 3rd party detection | Hunters detection | IOC search | Search | Table name | Log format | Collection method | | --- | --- | --- | --- | --- | --- | --- | --- | | Kisi Access Control Events | | ✅ | | ✅ | `kisi_access_control_events` | JSON | Webhook, S3, GCP Bucket List, Azure Block Storage List | ## Overview Kisi is a cloud-based physical access control platform that manages locks, readers, and user access to doors and places such as offices, server rooms, and loading docks. Kisi emits a webhook event for every significant action in the system—door unlocks, forced/held-open alarms, tailgating detection, lockdowns, reader tampering, logins, and role/credential changes—as a single JSON object per event. If you already forward Kisi events to cloud storage (S3, GCS or Azure Blob) as JSON files, Hunters can collect them from there instead. Integrating Kisi with Hunters provides a full audit trail of who accessed which physical space, when, and how they authenticated, while surfacing physical security alarms (forced open, tailgating, tamper) that may indicate intrusion attempts or policy violations. ## Supported data types ### Kisi Access Control Events **Table name:** `KISI_ACCESS_CONTROL_EVENTS` This data type contains the full stream of Kisi access control events, including door unlock attempts (successful and failed), physical security alarms such as forced-open doors, tailgating, and reader tampering, as well as administrative actions like logins, lockdowns, guest registrations, and role/credential changes. Each event shares a common schema that identifies the actor, the target object (lock, reader, place, etc.), the action taken, and whether it succeeded. **Expected format** Logs are expected in JSON format. `{"uuid":"c1d2e3f4-0b0b-5e11-8f9e-e71a5624fa20","type":"lock.forced_open","actor_type":null,"actor_id":null,"actor_name":null,"actor_email":null,"authenticated_by_type":null,"authenticated_by_id":null,"authorized_by_type":null,"authorized_by_id":null,"authorized_by_role_id":null,"object_type":"Lock","object_id":512033,"object_name":"Loading Dock","action":"forced_open","created_at":"2026-11-04T09:01:34Z","message":"Loading Dock was forced open","success":true,"code":null,"sequence":"d2e3f4a5-94f2-53a1-9d03-a8944a86c421","organization_id":60001,"place_id":70001,"error_code":null,"error_message":null,"references":[]}` ## Send data to Hunters Hunters supports the collection of Kisi logs using Webhook, S3 List, S3 Notifications, GCP Bucket List, and Azure Block Storage List. **To connect Kisi logs:** ### Connect using Webhook Kisi sends events to Hunters through its Event Webhook integration. Kisi can't add custom headers to its requests, so Hunters authenticates each event by the signature Kisi adds to it (the `X-Signature` header) instead of a bearer token. 1. Connect the data source in the Hunters portal as described in [this section](https://docs.hunters.ai/docs/connect-a-data-source-using-apiwebhook), choosing **Kisi Access Control via Webhook**. 2. Get the webhook URL and key of the new connection. If the portal doesn't show them, contact Hunters Support. 3. Sign in to the [Kisi dashboard](https://web.kisi.io) as an organization admin. 4. Go to **Settings > Integrations** and click **Add Integration**. 5. Name the integration (for example, "Hunters") and choose **Event Webhook** in the **Type** dropdown. 6. Paste the Hunters webhook URL into **Event Webhook URL**. 7. Paste the Hunters key into the signature key field. Kisi marks this field as optional, but Hunters requires it and rejects events that aren't signed with this key. 8. Select the event types to send to Hunters, enable the integration and click **Add**. Kisi starts sending events as soon as the integration is saved. For more about the integration, see Kisi's [Event Webhooks documentation](https://docs.kisi.io/marketplace/workflow_automation/event_webhooks/). ### Connect using S3 List or S3 Notifications 1. Route Kisi logs into an AWS S3 bucket. 2. Once logs are in S3, follow the steps in [this section](https://docs.hunters.ai/docs/connect-data-through-aws-s3). ### Connect using Azure Block Storage List 1. Route Kisi logs into an Azure Storage container as block blobs. 2. Once logs are in the container, follow the steps in [this section](https://docs.hunters.ai/docs/connect-data-through-azure-storage). ### Connect using GCP Bucket List 1. Route Kisi logs into a Google Cloud Storage bucket. 2. Once logs are in the bucket, follow the steps in [this section](https://docs.hunters.ai/docs/connect-data-through-gcp).