Connect Parcel Pending to KODE OS for smart locker data integration
Overview
Use this integration to connect Parcel Pending smart lockers to KODE OS. You discover lockers, poll status and metadata, and collect historical utilization data over REST.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- Collect Non-Sensor Data
Prerequisites
- An active account with Parcel Pending and access to their API or developer portal
- OAuth client credentials (Client ID and Client Secret) from the Parcel Pending developer portal
- KODE OS environment with access to Data Sources
Generate API Credentials
- Log in to the Parcel Pending 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 Parcel Pending
- 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 Parcel Pending 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 Parcel Pending, KODE OS maps them to the following device types and data points:Smart Locker
Canonical Type:default
What Data You Get
Point History
Time-series readings including Locker Status, Connection Status, collected at regular intervals from connected devicesEvent Logs
System and security event records with timestamps, event types, and associated devices KODE OS maps Parcel Pending data to these standard fields:Polling Schedule
- Point History — Default polling: 30 minutes (min: 30 minutes, max: 1 hours)
- EventLog — Default polling: 30 minutes (min: 30 minutes, 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 Parcel Pending developer portal.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Parcel Pending 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 Parcel Pending API.