> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tririga - FDH

> Connect Tririga - FDH to KODE OS for reservations data

> 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.

| Property            | Value        |
| ------------------- | ------------ |
| **System Type**     | Reservations |
| **Communication**   | REST         |
| **Collection**      | Pull         |
| **Collection Mode** | SNAPSHOT     |

## 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

| Field            | Required | Type     | Description                                              |
| ---------------- | -------- | -------- | -------------------------------------------------------- |
| **URL**          | Yes      | text     | The base URL or IP address of the external system        |
| **Auth URL**     | Yes      | text     | The OAuth authorization URL for token exchange           |
| **External URL** | Yes      | text     | An additional external URL for the integration           |
| **Username**     | Yes      | password | The username for authenticating with the external system |
| **Password**     | Yes      | password | The password for authenticating with the external system |
| **API Key**      | Yes      | password | The API key for authenticating with the external system  |

## Devices and Points

| Point          | Display Name |
| -------------- | ------------ |
| `status`       | status       |
| `country`      | country      |
| `collected_at` | collected at |

## 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](/products/integrations/capabilities/data-collection).

## 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

<AccordionGroup>
  <Accordion title="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 Tririga - FDH platform.
  </Accordion>

  <Accordion title="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 Tririga - FDH API.
  </Accordion>
</AccordionGroup>