Connect Kastle Event Connect to KODE OS for access control and security alarm data
Overview
Use this integration to collect card access events and security alarms from Kastle Event Connect REST API v3. KODE OS stores these records as access logs and alarms for monitoring, investigation, and reporting.Supported capabilities
- Collect access logs
- Collect alarms
- Collect historical data
Prerequisites
- A Kastle Event Connect account with REST API v3 access
- A Kastle client ID and client secret
- The Kastle API base URL for your environment
- KODE OS access to
Data Sources
Configure the connector in KODE OS
- Open
Data Sourcesfor your building. - Select
API Catalog, then search forKastle API. - Select
+ Add Datasource. - Complete the connector fields.
KODE OS exchanges the client credentials for a Bearer token before requesting event data.
What data you get
Kastle provides non-sensor records. This connector does not discover devices or sensor points.Access logs
Access records include the result, credential, person, location, and event time.
KODE OS stores additional credential-holder and location attributes in
custom_fields.
Alarms
Alarm records include the alarm name, state, location, source, type, and timestamps.
KODE OS stores the location identifiers,
stimId, source, and event type in custom_fields.
Historical collection
Each Kastle request can cover up to 30 days. You can collect up to 90 days of previous events. The connector follows Kastle pagination usinglimit and offset. The default page size is 500 records, and the maximum is 2,000.
Polling schedule
- Access logs and alarms — Poll approximately every 15 minutes, subject to vendor data latency
Use cases
Once connected, you can:- Review allowed and denied access events in KODE OS
- Investigate alarms with credential-holder and location context
- Build access and security audit reports without manual exports
Troubleshooting
Authentication or connection error
Authentication or connection error
Verify the API URL, client ID, and client secret. Confirm the Kastle application can access Event Connect REST API v3.
Historical records are missing
Historical records are missing
Keep each requested window within 30 days and the complete lookback within 90 days. Account for vendor processing latency when reviewing the newest events.
Collection stops before all events load
Collection stops before all events load
Review the connector logs for pagination errors. Confirm the connection can continue through each
offset until Kastle returns the complete result set.