Connect TDS Visitor Management to KODE OS for reservations data integration
Overview
Use this integration to bring TDS Visitor Management into KODE OS. You collect visitor check-in, pre-registration, and scheduling history over REST for secure, auditable visitor operations.Supported Capabilities
- Collect Sensor Data
- Collect Non-Sensor Data
Prerequisites
- An active account with TDS Visitor Management and access to their API or developer portal
- OAuth client credentials (Client ID and Client Secret) from the TDS Visitor Management developer portal
- KODE OS environment with access to Data Sources
Generate API Credentials
- Log in to the TDS Visitor Management 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
- Note the Auth URL for OAuth token exchange
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for TDS Visitor Management
- Click + Add Datasource
- Fill in the fields below and complete the three-page setup flow
What Data You Get
Bookings
Space reservation records including attendees, check-in/out times, confirmation status, and room/space details KODE OS maps TDS Visitor Management data to these standard fields:Polling Schedule
- Booking
Use Cases
Once connected, this integration enables you to:- Centralize space and resource booking data across platforms
- Track no-show rates and actual utilization versus bookings
- Coordinate meeting room conditions (HVAC, lighting) with reservation schedules
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 TDS Visitor Management 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 TDS Visitor Management API.