Skip to main content
Connect BuiltSpace to KODE OS for work orders data integration

Overview

Use this integration to connect BuiltSpace to KODE OS. You can pull historical sensor and non-sensor data over REST so work orders and building context stay aligned across your portfolio.

Supported Capabilities

  • Collect Sensor Data
  • Collect Non-Sensor Data

Prerequisites

  • An active account with BuiltSpace and access to their API or developer portal
  • API key or token from the BuiltSpace platform
  • KODE OS environment with access to Data Sources

Generate API Credentials

  1. Log in to the BuiltSpace platform or admin console
  2. Navigate to the API settings, developer section, or account settings
  3. Generate a new API key or token
  4. Copy the key and store it securely — you will need it 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 BuiltSpace
  3. Click + Add Datasource
  4. Fill in the fields below and complete the three-page setup flow

What Data You Get

Inspections

Facility inspection records including checklist results, findings, and compliance status

Tasks

Facility task records including assignment, status, priority, and completion details

Polling Schedule

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

Use Cases

Once connected, this integration enables you to:
  • Centralize maintenance requests and work order status from facility management systems
  • Create and update work orders directly from KODE OS when issues are detected
  • Track maintenance KPIs including response time, completion rate, and cost

Troubleshooting

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 BuiltSpace platform.
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 BuiltSpace API.
Last modified on March 29, 2026