API for status of public chargers (at least Germany)

Does anybody know of an API of sorts to get the current status of an public ev charger?
like in some Charging Apps it’s shown:


(sorry for german)

I’d like to integrate these data points:
(1) the current state (free, occupied, defect/offline)
(2) the time since it is occupied

Someone found an API for this? There should be a european-wide database, but I don’t seem to find an API for that…?

What about this one
https://ladestationen.api.bund.dev/
Or

Or

1 Like

Thanks!
The TomTom one seems to have status at least. The other ones are just a directory.

For everyone else, the TomTom-API is what I was looking for. And currently in the free plan you’ll get 2500 non-tile request per day, which is more than sufficient to observe a chargepoint. :wink:

You could

  1. either use the “Nearby search” (/search/2/evsearch vor v2 of the endpoint), which will have the station and its status in the response also:
    Here it would be object►results►0►chargingStations►0►chargingPoints►0►status
  1. or use the TomTom ID (object►results►0►id) for a specific search (/search/2/evbyid also v2), which will have the same payload.
    (see above EV Search API)

  2. or use the TomTom ID (object►results►0►id) for a availability search (/search/2/chargingAvailability.{ext} for v2 of the endpoint):
    Then it would be object►connectors►0►availability►current►available/occupied/...

I use the 3. option, for it spits out already the number of available/occupied/offline loadpoints. That’s already a good start for a rule.

1 Like

Might become a candidat for a new Binding :wink:

:wink:
You don’t want me to write a binding!
But I’m thinking about writing a Tutorial for how to us http-binding and rules for that.

No, I might find some time to start it. We’ll see :wink:
Tutorial would be fine, especially a guidance, what you would expect from such a binding…

2 Likes

:white_check_mark: done

1 Like