For developers & home automation integrators

NRGkick API: connect your charging cable to your smart home

With the NRGkick’s local API, you integrate your charging cable directly into your smart home system and program your own automations. Unlike the app, the API lets you retrieve even more precise data and control the charging process fully automatically.

Request your quote

Discover the NRGkick

What is a local API?

An API (Application Programming Interface) is a set of commands that lets two devices exchange information directly. Each request has a predefined response — no data can be sent outside these fixed commands, making the integration both powerful and secure. The NRGkick’s local API is available in two protocols, each with its own advantages.

JSON API

A local REST API that returns information via clear endpoints, such as GET /info for device data (serial number, MAC address) and GET /values for real-time measurement data (power, energy, temperatures). Ideal when you want to quickly and easily read human-readable data.

Modbus API

Works with individual memory addresses instead of bundled endpoints. All registers use little-endian format and are readable via Unit ID 1. The advantage: you request exactly the values you need, without transmitting unnecessary data.

20251017_Blogpost_NRGkick-MID-Business-Header

More possibilities than the app

Where in the NRGkick app you have to actively adjust your charging current yourself, the API lets you automate this entirely. This way you can build your own logic based on real-time data — for example to automatically adjust based on your solar panel output or your total household electricity consumption.

More precise and detailed data than via the app
Fully automatable, no manual intervention needed
Two protocols: JSON API and Modbus TCP API
Optional BasicAuth authentication for extra security
Extensive, official documentation available

Everything you need to know about the NRGkick API

From activation to concrete applications: find all the technical details about the local API here.

How do I activate the local API on my NRGkick?

You must first activate the local API via the NRGkick app. Open the app, connect to your device, go to Settings → JSON API, and enable the API. Optionally you can set up BasicAuth authentication right away, so only authorised devices get access to your NRGkick. A similar activation via the app settings applies for the Modbus API.

What data can I read via the JSON API?

The GET /info endpoint returns identification data such as the serial number and MAC address, letting you uniquely identify your device within your system. The GET /values endpoint provides real-time telemetry: current power, energy consumed and temperature measurements. Both endpoints can also be queried per section, so you only receive the data you need — useful if you want to limit the load on your own system.

How exactly does the Modbus TCP API work?

The Modbus API works via numbered register addresses instead of endpoints. All registers use little-endian format and can be queried via Unit ID 1. Important: addresses must always be read with their correct register length; as long as you stay within the correct alignment, you can also read multiple addresses at once. This protocol is especially interesting for integration with industrial energy management systems that already work with Modbus as standard.

Practical example: integration with Home Assistant

Thanks to the open, documented JSON API, there is even an open-source Python library that lets developers link their NRGkick directly to Home Assistant, a popular open-source home automation platform. This immediately demonstrates the power of the local API: you’re not limited to the official NRGkick app, but can (yourself, or via your home automation integrator) build fully custom automations.

Combining the API with solar charging or Peak Shaving

The API is the ideal foundation to automate solar charging even further: instead of relying on the fixed charging strategies in the app, you read your solar energy output in real time via the API and adjust the charging current yourself. If you manage multiple charge points or large consumers, the API also forms the technical foundation for our Peak Shaving system, and it connects seamlessly with OCPP charging network integrations for fleet managers.