Skip to main content
Connect Tririga - FDH to KODE OS for reservations data integration

​
Overview

Use this integration to connect IBM Tririga FDH reservations data to KODE OS. You pull snapshot reservation and related operational records over REST for centralized monitoring and reporting.

​
Supported Capabilities

  • Collect Sensor Data
  • Collect Non-Sensor Data

​
Prerequisites

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

​
Generate API Credentials

  1. Log in to the Tririga - FDH 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 Tririga - FDH
  3. Click + Add Datasource
  4. Fill in the fields below and complete the three-page setup flow

​
Devices and Points

​
What Data You Get

​
Reservations

Space and resource reservation records from the TRIRIGA platform

​
Polling Schedule

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

​
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

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