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.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
- Log in to the Yale Accentra 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
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for Yale Accentra
- Click + Add Datasource
- Fill in the fields below and complete the three-page setup flow
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:Polling Schedule
- Audit Log — Default polling: 1 days (min: 1 days, max: 1 days)
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
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 Yale Accentra developer portal.
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 Yale Accentra API.

