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

​
Overview

Use this integration to ingest ParkChamp parking operations data into KODE OS. Scheduled polling brings access logs and vehicle records into the platform so you can track entries, exits, and facility utilization.

​
Supported Capabilities

  • Collect Sensor Data
  • Collect Non-Sensor Data

​
Prerequisites

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

​
Generate API Credentials

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

​
Devices and Points

​
What Data You Get

​
Parking Access Logs

Parking facility access logs including vehicle entry/exit events

​
Vehicles

Vehicle registration and tracking data in parking facilities

​
Polling Schedule

  • ParkChampVehicles — Default polling: 2 minutes (min: 2 minutes, max: 1 days)
  • ParkChampAccessLogs — Default polling: 2 minutes (min: 2 minutes, 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 ParkChamp platform.
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 ParkChamp API.
Last modified on March 29, 2026