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

# Monta

> Connect Monta to KODE OS for electric vehicle charging data

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

## Overview

Use this integration to connect Monta-managed charge points to KODE OS. REST discovery and polling plus webhooks keep station state and events synchronized for operations and automation.

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

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* Receive Webhook Data

## Prerequisites

* An active account with Monta and access to their API or developer portal
* OAuth client credentials (Client ID and Client Secret) from the Monta developer portal
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the Monta 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 Webhook

This integration uses webhooks for real-time data delivery. After creating the connector in KODE OS:

1. Copy the webhook URL provided on the connector detail page
2. In the Monta platform, navigate to the webhook or notification settings
3. Add a new webhook endpoint using the KODE OS URL
4. Configure the authentication header as specified on the connector detail page
5. Save and enable the webhook

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **Monta**
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      | password | The OAuth client ID from the vendor's developer portal     |
| **Client Secret**   | Yes      | password | The OAuth client secret from the vendor's developer portal |
| **Team ID**         | Yes      | password | The team identifier in the external system                 |
| **API Building ID** | Yes      | password | The building or source identifier in the external system   |

## Discover Devices and Points

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

### EV Charging Station

Canonical Type: `default`

| # | Point           | Description                                                                    | Unit            | Writable | Ontology Field           | Collection |
| - | --------------- | ------------------------------------------------------------------------------ | --------------- | -------- | ------------------------ | ---------- |
| 1 | `Power`         | Current power reading (kW)                                                     | kW              | No       | `run_power_sensor`       | Webhook    |
| 2 | `Type`          | Charger or connector type                                                      | --              | No       | --                       | Webhook    |
| 3 | `State`         | Current operating state                                                        | --              | No       | --                       | Webhook    |
| 4 | `Energy`        | Cumulative energy consumption (kWh)                                            | kilowattPerHour | No       | `run_energy_accumulator` | Webhook    |
| 5 | `Cable Plugged` | **True** -- Cable Plugged is active / **False** -- Cable Plugged is not active | --              | No       | --                       | Webhook    |

## What Data You Get

### Point History

Time-series readings including Power, Type, State, Energy, Cable Plugged, collected at regular intervals from connected devices

### Polling Schedule

* **Point History**
* **ChargePointSessions**

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. Ensure the Client ID and Client Secret match the values from the Monta developer portal.
  </Accordion>

  <Accordion title="Webhook data not arriving">
    Verify the webhook URL is correctly registered in the Monta platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the Monta system can reach the KODE OS webhook endpoint over the network.
  </Accordion>

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