Software House - C•Cure 9000 - KODE Labs

Connect Software House - C•Cure 9000 to KODE OS for access control data integration

Overview

Use this integration to connect Software House C•CURE 9000 to KODE OS. You can discover devices and points, collect access and security sensor and non-sensor data, and run supported actions from KODE OS when your deployment exposes them.

Property	Value
System Type	Access Control
Communication	REST
Collection	Pull
Collection Mode	SNAPSHOT
Actions	Supported

Supported Capabilities

Discover Devices & Points
Collect Sensor Data
Collect Non-Sensor Data
API Requests

Prerequisites

An active account with Software House - C•Cure 9000 and access to their API or developer portal
API key or token from the Software House - C•Cure 9000 platform
KODE OS environment with access to Data Sources

Generate API Credentials

Log in to the Software House - C•Cure 9000 platform or admin console
Navigate to the API settings, developer section, or account settings
Generate a new API key or token
Copy the key and store it securely — you will need it when configuring the connector in KODE OS

Configure Connector in KODE OS

Navigate to Data Sources in your building
Click API Catalog and search for Software House - C•Cure 9000
Click + Add Datasource
Fill in the fields below and complete the three-page setup flow

Field	Required	Type	Description
URL	Yes	text	The base URL or IP address of the external system
Username	Yes	text	The username for authenticating with the external system
Password	Yes	password	The password for authenticating with the external system
Client Name	Yes	text	The client application name registered with the vendor
API Key	Yes	password	The API key for authenticating with the external system
Client Version	Yes	dropdown	The version of the vendor’s API client

Discover Devices and Points

After configuring the connector, click Discover on the connector detail page. KODE OS will query the Software House - C•Cure 9000 system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the Discovery guide.

What Data You Get

Point History

Time-series sensor readings such as temperature, humidity, CO2, occupancy counts, energy consumption, light levels, and other measurable values from physical sensors

Audit Logs

Access and security event records including badge swipes, door access events, person identification, timestamps, and access results KODE OS maps the collected data to these standard fields:

KODE Field	Description
ID	Unique log entry identifier
Description	Event description
Person Name	Name of the person involved
Credential ID	Badge or credential identifier used
Credential Type	Type of credential (e.g., Card, PIN, Biometric)
Role	Access role or clearance level
Type	Event type (e.g., Entry, Exit, Denied)
Result	Access result (Granted, Denied, Error)
Access Point	Door or access point name
Location	Physical location of the access point
Access Time	Timestamp of the access event
Created At	Timestamp when the log was recorded

Visitor Logs

Visitor registration and tracking records including visitor name, host, check-in/out times

Polling Schedule

Point History — Default polling: 30 seconds (min: 30 seconds, max: 1 hours)
Audit Log — Default polling: 1 days (min: 1 days, max: 1 days)

For more details on collection modes, see the Data Collection guide.

Available Actions

Register Visitor

Type: Write Registers a new visitor in the Software House access control system

Field	Type	Required	Input	Options / Default
Type	STRING	Yes	Text Box	—
Visit Name	STRING	Yes	Text Box	—
Description	STRING	No	Text Box	—
Visit Site ID	STRING	Yes	Text Box	—
Visit Start	DATE_TIME	Yes	Text Box	—
Visit End	DATE_TIME	Yes	Text Box	—
Personnel ID	STRING	Yes	Text Box	—

Example Request

{
  "type": "example-value",
  "visitName": "example-value",
  "visitSiteId": "12345",
  "visitStart": "2026-03-29T10:00:00Z",
  "visitEnd": "2026-03-29T10:00:00Z",
  "childrenPersonnelId": "12345",
  "description": "example-value"
}

Expected Result

KODE OS sends the action to the external API using the configured connector credentials
The external system returns success (typically HTTP 2xx) and processes the requested operation

Register Visit

Type: Write Registers a new visit record in Software House

Field	Type	Required	Input	Options / Default
Type	STRING	Yes	Text Box	—
Name	STRING	Yes	Text Box	—
Hosting Mode	STRING	Yes	Text Box	—
Partition	STRING	Yes	Text Box	—

Example Request

{
  "type": "example-value",
  "name": "example-value",
  "hostingMode": "example-value",
  "partition": "example-value"
}

Expected Result

KODE OS sends the action to the external API using the configured connector credentials
The external system returns success (typically HTTP 2xx) and processes the requested operation

Delete Visit

Type: Write Deletes a visit record from Software House

Field	Type	Required	Input	Options / Default
Type	STRING	Yes	Text Box	—
Visit ID	STRING	Yes	Text Box	—

Example Request

{
  "type": "example-value",
  "id": "12345"
}

Expected Result

KODE OS sends the action to the external API using the configured connector credentials
The external system returns success (typically HTTP 2xx) and processes the requested operation

Get All Registered Visitors

Type: Read Retrieves all registered visitors for a site

Field	Type	Required	Input	Options / Default
Type	STRING	Yes	Text Box	—
Visit Site ID	STRING	Yes	Text Box	—

Example Request

{
  "type": "example-value",
  "visitSiteId": "12345"
}

Expected Result

KODE OS sends the action to the external API using the configured connector credentials
The external system returns success (typically HTTP 2xx) and processes the requested operation

For more details on how actions work, see the Actions guide.

Use Cases

Once connected, this integration enables you to:

Centralize access event monitoring across all entry points and zones
Generate audit trails for security compliance and investigation
Correlate access patterns with occupancy and energy data for building optimization

Troubleshooting

Authentication or connection error

Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Ensure the API key or token is valid and has not been revoked or expired in the Software House - C•Cure 9000 platform.

Discovery returns no devices

Verify the connector credentials have sufficient permissions in the Software House - C•Cure 9000 system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.

Data collection stops or gaps appear

Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Software House - C•Cure 9000 API.

Get Started

Capabilities

All Integrations

Software House - C•Cure 9000

Overview

Supported Capabilities

Prerequisites

Generate API Credentials

Configure Connector in KODE OS

Discover Devices and Points

What Data You Get

Point History

Audit Logs

Visitor Logs

Polling Schedule

Available Actions

Register Visitor

Example Request

Expected Result

Register Visit

Example Request

Expected Result

Delete Visit

Example Request

Expected Result

Get All Registered Visitors

Example Request

Expected Result

Use Cases

Troubleshooting

​Overview

​Supported Capabilities

​Prerequisites

​Generate API Credentials

​Configure Connector in KODE OS

​Discover Devices and Points

​What Data You Get

​Point History

​Audit Logs

​Visitor Logs

​Polling Schedule

​Available Actions

​Register Visitor

​Example Request

​Expected Result

​Register Visit

​Example Request

​Expected Result

​Delete Visit

​Example Request

​Expected Result

​Get All Registered Visitors

​Example Request

​Expected Result

​Use Cases

​Troubleshooting

Overview

Supported Capabilities

Prerequisites

Generate API Credentials

Configure Connector in KODE OS

Discover Devices and Points

What Data You Get

Point History

Audit Logs

Visitor Logs

Polling Schedule

Available Actions

Register Visitor

Example Request

Expected Result

Register Visit

Example Request

Expected Result

Delete Visit

Example Request

Expected Result

Get All Registered Visitors

Example Request

Expected Result

Use Cases

Troubleshooting