VW locks API for external charging control

Put simply, an API (Application Programming Interface) acts as an “interpreter” between two software applications and enables them to exchange data. In Volkswagen’s case, this means that programmes such as charging management software or smart home systems can access vehicle data — for example the battery’s state of charge — without needing direct access to the vehicle’s full onboard computer system.

The change to Volkswagen’s APIs for its ID. family of electric vehicles, announced in early April and implemented in calendar week 21 (18–24 May), has significant implications. The announcement stated that the existing “Brand App Interface” would be closed to external access from this point onward.

As a result, users of the API across Volkswagen, Audi, Cupra and Škoda vehicles can no longer use it in their applications at short notice. While some users may tolerate losing access to battery state-of-charge data in third-party apps, the consequences are more serious for customers who relied on the API to manage surplus charging from home photovoltaic systems. This particularly affects users of EVCC (Electric Vehicle Charge Controller) smart charging software.

It appears Volkswagen aims to restrict the unregulated use of its APIs with this move. The company also stated that ten charging data providers had already integrated the new interface by 2 April. This essentially means that Volkswagen will only grant access to such APIs to official partner companies in future, no longer supporting open-source solutions.

The move mirrors a similar step taken by BMW last year. In September 2025, the German carmaker sharply restricted the use of unofficial interfaces created through reverse engineering. Citing data security and vehicle protection, BMW blocked automated integrations with third-party solutions such as the widely used Home Assistant integration.

Since then, access to vehicle data has only been available through official commercial partnerships, including aggregators such as Volteras and specialised energy service providers like clever-PV, which focuses on surplus charging.

Volkswagen is now taking the same step by introducing mandatory partnerships: the end of unofficial DIY solutions in favour of a controlled, exclusive data ecosystem. Two of the companies that have already announced partnerships with Volkswagen, as with BMW, are clever-PV and Volteras.

Update 10 June 2026

Volkswagen has issued a statement about the shutdown of the API. According to the company, it originally developed the API exclusively for its own vehicle app infrastructure. Third-party providers later gained access through reverse engineering. Volkswagen was aware of this and initially tolerated it.

However, the interface was not designed to handle such high access volumes, which led to errors. “In light of increasing technical requirements and the existing architecture operating at full capacity, we have completed the transition to documented and standardised interfaces”, Volkswagen told the German portal Heise Online.

The group said it had contacted various affected companies before closing the API and enabled them to switch to official APIs, which are subject to fees. According to Volkswagen, some of these companies ‘in turn acted as a data provider for other third parties, ensuring that even smaller companies were both technically prepared for the transition and informed at an early stage about the closure of the interface.’

Charging provider Tibber, for example, now accesses vehicle data via the Enode platform. Other companies already using the new API include Kraken, Ohme, Tronity and EEVEE.

drivesomethinggreater.com (VW announcement; in German), heise.de, volteras.com (BMW), heise.de (update; in German)