Connect Precise Park to KODE OS for parking data integration
Overview
Use this integration to bring Precise Park data into KODE OS. You discover devices per building API ID, monitor space counts and violation or service flags, and ingest related non-sensor parking records.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- Collect Non-Sensor Data
Prerequisites
- An active account with Precise Park and access to their API or developer portal
- Username and password credentials for the Precise Park system
- KODE OS environment with access to Data Sources
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for Precise Park
- Click + Add Datasource
- 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 Precise Park 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 Precise Park, 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 is_in_violation, is_occupied, is_out_of_service, is_reserved, available, occupied, out_of_service, reserved, and 2 more, collected at regular intervals from connected devicesBookings
Space reservation records including attendees, check-in/out times, confirmation status, and room/space details KODE OS maps the collected data to these standard fields:Polling Schedule
- Point History — Default polling: 30 seconds (min: 30 seconds, max: 1 hours)
- Booking — Default polling: 1 days (min: 1 days, max: 1 days)
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
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. Verify the username and password are correct and the account has not been locked in the Precise Park system.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Precise Park system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
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 Precise Park API.