Skip to main content
Connect Blink to KODE OS for electric vehicle charging data integration

​
Overview

Use this integration to connect Blink EV chargers to KODE OS. You discover stations and connectors, then collect session, energy, and status data over REST with historical retention for utilization analysis.

​
Supported Capabilities

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

​
Prerequisites

  • An active account with Blink and access to their API or developer portal
  • API key or token from the Blink platform
  • KODE OS environment with access to Data Sources

​
Generate API Credentials

  1. Log in to the Blink platform or admin console
  2. Navigate to the API settings, developer section, or account settings
  3. Generate a new API key or token
  4. Copy the key and store it securely — you will need it 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 Blink
  3. Click + Add Datasource
  4. 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 Blink 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.

​
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: 5 minutes (min: 5 minutes, max: 1 hours)
  • ChargePointSessions
For more details on collection modes, see the Data Collection guide.

​
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

Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Ensure the API key or token is valid and has not been revoked or expired in the Blink platform.
Verify the connector credentials have sufficient permissions in the Blink system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
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 Blink API.
Last modified on March 29, 2026