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

# JLL OneView

> Connect JLL OneView to KODE OS for other data

> Connect JLL OneView to KODE OS for other data integration

## Overview

Use this integration to connect JLL OneView portfolio data to KODE OS. Historical REST feeds deliver asset performance, occupancy, leasing, and operational KPIs for real estate analytics.

| Property            | Value      |
| ------------------- | ---------- |
| **System Type**     | Other      |
| **Communication**   | REST       |
| **Collection**      | Pull       |
| **Collection Mode** | HISTORICAL |

## Supported Capabilities

* Collect Sensor Data
* Collect Non-Sensor Data

## Prerequisites

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

## Generate API Credentials

1. Log in to the JLL OneView 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 **JLL OneView**
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        |
| **Username**              | Yes      | text     | The username for authenticating with the external system |
| **Password**              | Yes      | password | The password for authenticating with the external system |
| **User Key**              | Yes      | text     | The user-specific key from the vendor platform           |
| **Client ID**             | Yes      | text     | The OAuth client ID from the vendor's developer portal   |
| **Building Reference ID** | Yes      | text     | The building reference identifier in the external system |
| **Subscription Key**      | Yes      | password | The subscription key for the vendor's API                |

## What Data You Get

### Leases

Lease records including tenant, space, lease terms, dates, and financial details

### Lease Costs

Lease cost and billing records including charges, payment schedules, and cost breakdowns

### Event Logs

System and security event records with timestamps, event types, and associated devices

KODE OS maps JLL OneView data to these standard fields:

| KODE Field       | Source Field          | Notes                |
| ---------------- | --------------------- | -------------------- |
| **category**     | `EventCategory.LEASE` | --                   |
| **id**           | `id`                  | --                   |
| **name**         | `eventType`           | --                   |
| **status**       | `actionStatus`        | --                   |
| **createdAt**    | `createdOn`           | transformed          |
| **updatedAt**    | `updatedOn`           | transformed          |
| **customFields** | `(custom fields)`     | custom fields object |

### Polling Schedule

* **Lease** -- Default polling: 7 days (min: 7 days, max: 7 days)
* **LeaseCost**
* **EventLog**

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 JLL OneView data in your building operations dashboard
* Correlate data from this system with other building systems for comprehensive analytics

## 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 Client ID and Client Secret match the values from the JLL OneView developer portal.
  </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 JLL OneView API.
  </Accordion>
</AccordionGroup>