> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Parcel Pending

> Connect Parcel Pending to KODE OS for smart locker data

> 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.

| Property            | Value        |
| ------------------- | ------------ |
| **System Type**     | Smart Locker |
| **Communication**   | REST         |
| **Collection**      | Pull         |
| **Collection Mode** | HISTORICAL   |

## 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

1. Log in to the Parcel Pending developer portal or admin console
2. Navigate to the API or developer settings section
3. Create a new API application or client
4. Note the **Client ID** and **Client Secret** -- you will need these 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 **Parcel Pending**
3. Click **+ Add Datasource**
4. Fill in the fields below and complete the three-page setup flow

| Field             | Required | Type     | Description                                                |
| ----------------- | -------- | -------- | ---------------------------------------------------------- |
| **URL**           | Yes      | text     | The base URL or IP address of the external system          |
| **Client ID**     | Yes      | text     | The OAuth client ID from the vendor's developer portal     |
| **Client Secret** | Yes      | password | The OAuth client secret from the vendor's developer portal |
| **Property ID**   | Yes      | password |                                                            |

## 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](/products/integrations/capabilities/discovery).

## 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`

| # | Point               | Description                                                           | Unit | Writable | Collection |
| - | ------------------- | --------------------------------------------------------------------- | ---- | -------- | ---------- |
| 1 | `Locker Status`     | Current lock state                                                    | --   | No       | Polling    |
| 2 | `Connection Status` | **True** -- device is connected / **False** -- device is disconnected | --   | No       | Polling    |

## What Data You Get

### Point History

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

### Event Logs

System and security event records with timestamps, event types, and associated devices

KODE OS maps Parcel Pending data to these standard fields:

| KODE Field    | Source Field             | Notes       |
| ------------- | ------------------------ | ----------- |
| **category**  | `EventCategory.DELIVERY` | --          |
| **id**        | `id`                     | --          |
| **name**      | `parcelStatus`           | --          |
| **status**    | `status.stringValue`     | transformed |
| **location**  | `propertyId`             | --          |
| **deviceId**  | `lockerId`               | --          |
| **createdAt** | `creationTime`           | --          |
| **updatedAt** | `lastUpdateTime`         | --          |

### 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)

For more details on collection modes, see the [Data Collection guide](/products/integrations/capabilities/data-collection).

## 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

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>