Skip to main content
Connect Kahua to KODE OS for project data integration

Overview

Use this integration to connect Kahua construction and capital project data to KODE OS. REST historical collection brings project, procurement, and execution records into the platform for portfolio alignment.

Supported Capabilities

  • Collect Sensor Data
  • Collect Non-Sensor Data
  • Collect Historical Data
  • Collect Historical Multi-Entity Data

Prerequisites

  • An active account with Kahua and access to their API or developer portal
  • OAuth client credentials (Client ID and Client Secret) from the Kahua developer portal
  • KODE OS environment with access to Data Sources

Generate API Credentials

  1. Log in to the Kahua developer portal or admin console
  2. Navigate to the API or developer settings section
  3. Create a new API application or client
  4. Note the Client ID and Client Secret — you will need these when configuring the connector in KODE OS

Configure Connector in KODE OS

  1. Navigate to Data Sources in your building
  2. Click API Catalog and search for Kahua
  3. Click + Add Datasource
  4. Fill in the fields below and complete the three-page setup flow

What Data You Get

Projects

Project records including project name, status, timelines, and associated documentation

Polling Schedule

  • Project — Default polling: 1 hours (min: 1 hours, max: 1 days)
For more details on collection modes, see the Data Collection guide.

Use Cases

Once connected, this integration enables you to:
  • Centralize Kahua data in your building operations dashboard
  • Correlate data from this system with other building systems for comprehensive analytics

Troubleshooting

Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Ensure the Client ID and Client Secret match the values from the Kahua developer portal.
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 Kahua API.
Last modified on March 29, 2026