Repository navigation
VW Group Data Hub: Vehicle Data API for dynamic charging – Closed Beta coming in 2027 #36190
Replies: 15 comments 16 replies
|
How this differs from the API Skoda has release just a some time ago? |
|
What is With the New ID Polo? I can‘t find it in your list. |
|
Will this API meet the EU Data Act Article 4 'same quality' standard, including real-time delivery where technically feasible, or will it only expose whatever is already available on your platform, however stale? And will it be free (not requiring an active subscription), as the EU Data Act requires? Separately, and relevant to the many UK owners in the Audi Connect thread: will this API also be available to users with vehicles registered in the UK, or will it be limited to the EU? |
|
Will it also be possible to control the vehicle later on? More specifically, to start or stop charging, turn the windows and auxiliary heater on and off, etc.? |
|
@VWGroupDatahub this is a very positive surprise for a Friday the 13th. ;-) |
|
My partner has been looking forward to this day so much. Currently, evcc only works with "fast" data, and the present situation is unsatisfactory. This glimmer of hope feels like an early Christmas present. We would love to take part in the beta test. Thanks from Esther&Detlef |
|
Great news—hopefully it'll happen soon |
|
This is great news, happy to be testing it out. |
|
I'm not holding my breath. Skoda managed to deploy a working API within weeks, whereas this is VW's first communication in almost a year since shutting things down without warning. At this pace, we can expect this fancy new API sometime in 2028, right? How generous to finally abide by the regulations. Don't get me wrong. I don't blame the developers or the person posting this. You’re likely just as relieved to finally be able to share something. My criticism is aimed squarely at the management and corporate structures making these decisions. If VW could just swallow its "German engineering" pride and adopt the solution Skoda already offers, we could have everything we asked for in a month. So, yay for us finally getting some breadcrumbs at an undefined date. My ID.Buzz lease ends in December 2027, and I’d be genuinely surprised to see a useful public release before then. Until then, I have to rely on an old phone hooked up via ADB just to scrape my car's status from the screen. That sentence sounds like a joke, but it's the actual reality of being a VW customer right now. |
|
Here's a Caddy ehybrid and e-up user hoping that those will also be included later on and that you will get this ready until the time the sun is shining enough for constant PV charging again. |
|
Hey, this are really positive news. I also welcome that the smart charging use case is prioritized first. But I am Wondering why in this case it is only focussed on ready only because especially the Smart Charging use case needs to have the control button for charging from the vehicle. With the normale non callbox charger it is not possible to control charging over switches a digital switch on/off because the internal charger of my VW Passat hybrid is not capable of continuing the charing after power loss. Only a control over the VW App is possible. For me it is on to start with the read only use case when the control of the charging will come directly on next step? How is the development plan for this? |
|
It's hard to be excited for a worse access than we had before, but alas, I'll take whatever scraps the generous corporate overlords decided to provide after being legally mandated to do so... |
|
We all know that VW hasn’t exactly covered itself in glory, and there is plenty of discussion on that topic elsewhere. First of all, thanks to @VWGroupDatahub for this good news—something we’ve all been waiting for for such a long time. Let’s look at how we can get the new API up and running as quickly as possible. My offer to the developers is this:
Kind regards, |
Uh oh!
There was an error while loading. Please reload this page.
VW Group Datahub introduces the Vehicle Data API
Hi everyone,
over the past months, we have received a lot of valuable feedback from this community about access to vehicle data, including data availability, reliability, and the request for a REST API. Thank you to everyone who has shared feedback and use cases with us.
We would now like to give you an early look at what we are working on and involve the open-source community as we prepare the next step.
A first look at the Vehicle Data API
We are currently preparing a new additional read-only REST API that will allow users to access selected data from their own vehicles.
We want to make sure that the API and the underlying data delivery work reliably across our vehicle landscape before expanding the scope.
For this reason, we have decided to start with one specific use case:
Dynamic charging for EVs and PHEVs
The first version focuses on data relevant for dynamic charging and home energy management, including selected data from these areas:
The API provides the latest vehicle data available on our platform. Calling the API does not trigger direct communication with the vehicle.
We believe this is a good first real-world scenario to validate the API together with integrations such as Home Assistant, EVCC, ioBroker, and other open-source smart-home and energy-management projects.
Closed Beta planned for early 2027
We are currently preparing the Closed Beta and are aiming to start it in early 2027.
Participation in this first phase will be limited.
We are looking for developers and technically experienced users who:
Vehicles included in the Closed Beta
Audi
BEV
PHEV
Volkswagen
BEV
PHEV
Volkswagen Commercial Vehicles
BEV
PHEV
SEAT/CUPRA
BEV
PHEV
Škoda
BEV
PHEV
Bentley
PHEV
Registration for the Closed Beta
Registration for the Closed Beta is not open yet.
We plan to open registration in December 2026 and will share a separate update with details on the registration process.
Until then, there is no action required if you are interested in participating.
As participation in the first phase will be limited, registration will not guarantee participation in the Closed Beta.
Why are we sharing this now?
Because many of you have been asking for this kind of access.
Rather than designing the next steps without you, we would like to involve the community and learn from real-world usage.
We want to make the first API available to real developers and users, learn from what works and what doesn't, and use that feedback to improve the solution and inform the next steps.
Thanks for all the feedback you've given us so far, including the critical feedback. Please keep it coming.
During the beta, we will regularly share what feedback we received and which topics we are actively evaluating for future releases.
We hope this is a useful first step, and we look forward to building on it together with the community.
Kind regards,
The Data Hub Team
Volkswagen Group Info Services AG
All reactions