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

# Zaptec

> Connect Zaptec to KODE OS for electric vehicle charging data

> Connect Zaptec to KODE OS for electric vehicle charging data integration

## Overview

Use this integration to connect Zaptec EV chargers to KODE OS. You discover equipment, poll charger status and energy metrics, and collect supporting non-sensor data over REST.

| Property            | Value                     |
| ------------------- | ------------------------- |
| **System Type**     | Electric Vehicle Charging |
| **Communication**   | REST                      |
| **Collection**      | Pull                      |
| **Collection Mode** | SNAPSHOT                  |

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* Collect Non-Sensor Data

## Prerequisites

* An active account with Zaptec and access to their API or developer portal
* Username and password credentials for the Zaptec system
* KODE OS environment with access to Data Sources

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **Zaptec**
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        |
| **Username** | Yes      | text     | The username for authenticating with the external system |
| **Password** | Yes      | password | The password for authenticating with the external system |

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Zaptec 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 Zaptec, KODE OS maps them to the following device types:

* **EV Charging Station** (`chargingStation`)

| Point                  | Display Name         |
| ---------------------- | -------------------- |
| `commit_end_date_time` | commit end date time |
| `isOnline`             | isOnline             |
| `active`               | active               |
| `signedMeterValueKwh`  | signedMeterValueKwh  |
| `operatingMode`        | operatingMode        |

## What Data You Get

### Point History

Time-series sensor readings such as temperature, humidity, CO2, occupancy counts, energy consumption, light levels, and other measurable values from physical sensors

### Polling Schedule

* **Point History** -- Default polling: 10 minutes (min: 10 minutes, max: 1 hours)
* **ChargePointSessions** -- 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 EV charger availability, session data, and energy delivered
* Track charging revenue and utilization across stations
* Generate reports on EV infrastructure usage and demand patterns

## 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. Verify the username and password are correct and the account has not been locked in the Zaptec system.
  </Accordion>

  <Accordion title="Discovery returns no devices">
    Verify the connector credentials have sufficient permissions in the Zaptec 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 Zaptec API.
  </Accordion>
</AccordionGroup>