Connect Condeco API to KODE OS for reservations data integration
Overview
Use this integration to bring Condeco room and desk reservations into KODE OS. Discovery, REST polling, and webhooks keep utilization, bookings, and workspace status aligned with your building operations.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- Collect Non-Sensor Data
- Receive Webhook Data
- Collect Historical Data
Prerequisites
- An active account with Condeco API and access to their API or developer portal
- OAuth client credentials (Client ID and Client Secret) from the Condeco API developer portal
- KODE OS environment with access to Data Sources
Generate API Credentials
- Log in to the Condeco API developer portal or admin console
- Navigate to the API or developer settings section
- Create a new API application or client
- Note the Client ID and Client Secret — you will need these when configuring the connector in KODE OS
- Note the Auth URL for OAuth token exchange
Configure Webhook
This integration uses webhooks for real-time data delivery. After creating the connector in KODE OS:- Copy the webhook URL provided on the connector detail page
- In the Condeco API platform, navigate to the webhook or notification settings
- Add a new webhook endpoint using the KODE OS URL
- Configure the authentication header as specified on the connector detail page
- Save and enable the webhook
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for Condeco API
- Click + Add Datasource
- Fill in the fields below and complete the three-page setup flow
Discover Devices and Points
After configuring the connector, click Discover on the connector detail page. KODE OS will query the Condeco API 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.Devices and Points
When you discover devices from Condeco API, KODE OS maps them to the following device types and data points:Presence / Occupancy Sensor
Canonical Type:presenceDetection
What Data You Get
Point History
Time-series readings including resource_occupied, collected at regular intervals from connected devicesBookings
Space reservation records including attendees, check-in/out times, confirmation status, and room/space details KODE OS maps Condeco API data to these standard fields:Polling Schedule
- Point History — Default polling: 1 days (min: 1 days, max: 1 days)
- Booking — Default polling: 1 hours (min: 1 hours, max: 1 days)
Use Cases
Once connected, this integration enables you to:- Centralize space and resource booking data across platforms
- Track no-show rates and actual utilization versus bookings
- Coordinate meeting room conditions (HVAC, lighting) with reservation schedules
Troubleshooting
Authentication or connection error
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 Client ID and Client Secret match the values from the Condeco developer portal.
Webhook data not arriving
Webhook data not arriving
Verify the webhook URL is correctly registered in the Condeco platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the Condeco system can reach the KODE OS webhook endpoint over the network.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Condeco 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
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 Condeco API.