Skip to main content
Connect Quercus to KODE OS for parking data integration

Overview

Use this integration to connect Quercus LPR and parking systems to KODE OS. You discover devices, poll status and sensor history, pair reservations and non-sensor data, and run configured API actions from the platform.

Supported Capabilities

  • Discover Devices & Points
  • Collect Sensor Data
  • Collect Non-Sensor Data
  • API Requests

Prerequisites

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

Generate API Credentials

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

Discover Devices and Points

After configuring the connector, click Discover on the connector detail page. KODE OS will query the Quercus system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the Discovery guide.

Devices and Points

When you discover devices from Quercus, KODE OS maps them to the following device types and data points:

Presence / Occupancy Sensor

Canonical Type: presenceDetection

What Data You Get

Point History

Time-series readings including Status, collected at regular intervals from connected devices

Reservations

Space reservation records including booking details, attendees, and confirmation status

Access Events

Access control events from the Quercus platform including badge reads and door events

Polling Schedule

  • Point History — Default polling: 30 seconds (min: 30 seconds, max: 30 seconds)
  • QuercusAccessEvent — Default polling: 1 days (min: 1 days, max: 1 days)
  • QuercusReservation — Default polling: 1 days (min: 1 days, max: 1 days)
For more details on collection modes, see the Data Collection guide.

Use Cases

Once connected, this integration enables you to:
  • Monitor real-time parking space availability across facilities
  • Track occupancy trends to optimize parking allocation and signage
  • Generate utilization reports for parking revenue and capacity planning

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 Quercus platform.
Verify the connector credentials have sufficient permissions in the Quercus system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
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 Quercus API.
Last modified on March 29, 2026