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

# Yale Accentra

> Connect Yale Accentra to KODE OS for smart locker data

> Connect Yale Accentra to KODE OS for smart locker data integration

## Overview

Use this integration to connect Yale Accentra smart lockers to KODE OS. Scheduled polling collects lock events, battery health, and fault signals with historical retention for reliability tracking.

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

## Supported Capabilities

* Collect Sensor Data
* Collect Non-Sensor Data
* Collect Historical Data

## Prerequisites

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

## Generate API Credentials

1. Log in to the Yale Accentra 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 **Yale Accentra**
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          |
| **Client ID**     | Yes      | text     | The OAuth client ID from the vendor's developer portal     |
| **Client Secret** | Yes      | password | The OAuth client secret from the vendor's developer portal |
| **System ID**     | Yes      | password | The system identifier in the external platform             |

## What Data You Get

### Audit Logs

Access and security event records including badge swipes, door access events, person identification, timestamps, and access results

KODE OS maps the collected data to these standard fields:

| KODE Field          | Description                                     |
| ------------------- | ----------------------------------------------- |
| **ID**              | Unique log entry identifier                     |
| **Description**     | Event description                               |
| **Person Name**     | Name of the person involved                     |
| **Credential ID**   | Badge or credential identifier used             |
| **Credential Type** | Type of credential (e.g., Card, PIN, Biometric) |
| **Role**            | Access role or clearance level                  |
| **Type**            | Event type (e.g., Entry, Exit, Denied)          |
| **Result**          | Access result (Granted, Denied, Error)          |
| **Access Point**    | Door or access point name                       |
| **Location**        | Physical location of the access point           |
| **Access Time**     | Timestamp of the access event                   |
| **Created At**      | Timestamp when the log was recorded             |

### Polling Schedule

* **Audit Log** -- Default polling: 1 days (min: 1 days, 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:

* Monitor locker availability and assignment status across facilities
* Track parcel delivery and pickup events for tenant services

## 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 Yale Accentra 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 Yale Accentra API.
  </Accordion>
</AccordionGroup>