We introduced a new endpoint that returns the list of Charging Point Operators (CPOs) whose chargers are available through the geosearch endpoints. It can be used to let users filter on specific operators.

https://developer.plugsurfing.com/reference/listoperators

The batch location endpoint have been improved: pagination is now stateless, and the performance has been improved.

v1.1.24 - 18.01.2024

New webhook event – Order Assigned

After ordering a charging key, a webhook event will be triggered
when the supplier starts processing the order. It will include orderId and userId.

This mechanism allows to let the user know that his order is being worked on.

v1.1.23 - 12.12.2023

Configurable supported countries

We have added a new configuration to only allow charging in specific countries.
Thanks to this setting, only chargers from selected countries will be returned from the API and charging
will be authorized only in these specified countries.

The list of supported countries can be set by our Support team. All countries are supported by default.

This configuration could help you roll out the integration gradually to selected countries,
or restrict charging sessions in countries where you don't yet operate in.

Geosearch performance improvements

We fine-tuned our caching mechanism. Thanks to this, long geosearch queries
should happen much less often.

v1.1.22 - 23.11.2023

Removing duplicated EVSEs and connectors

In very rare instances Drive API returned 2 available EVSEs with the same id within the same location.
This was caused by duplicated data received from CPOs which we'll clean up programmatically before
returning response.

Improved error handling in subscriptions

For some errors in subscriptions it wasn't clear what is the reason of a failure.
We've enhanced error messages for subscription issues to provide more insight.

v1.1.21 - 02.11.2023

Performance improvements

We've made some minor performance enhancements to our geosearch endpoints,
aiming to reduce the processing time of the most time-consuming requests.

Bugfix – returning sessions that failed to start

We've addressed an issue where sessions that failed to initiate were not being
returned through the session-by-id endpoint in certain scenarios.

Internal changes

We have successfully consolidated the configuration settings for the Drive API
into a unified location along with our other tools. This will allow to improve the Drive API tools.

v1.1.20 - 21.09.2023

Internal improvements

In this release, there are no modifications to the API. Instead, we're setting the stage for enhancements
in subscription and configuration management. Additionally, we've upgraded the NodeJS runtime version to 18.x,
resulting in some minor performance boosts and extended support with security updates.

v1.1.19 - 06.09.2023

Internal improvements

This release consists of internal improvements to monitoring
and some minor code cleanups, without changes to the API.

v1.1.18 - 24.08.2023

New option for Geosearch queries

Until now, locations returned from geosearch requests contained all EVSEs and connectors, even if some of them didn't match the filters
(it was enough that at least one EVSE or connector matched the filters for the whole location to be returned).
If that's not the expected behaviour, there is a new option for geosearch queries: filterEvsesAndConnectors.

With this option enabled, and filters set, the payload will be smaller because all EVSEs and connectors not matching
the filters will be removed from the response.

v1.1.17 - 09.08.2023

Limit geosearch result size

A new optional parameter is added to geosearch queries: limit.
It allows to control the maximum number of locations returned from the API,
making the data transfer faster when fewer locations are needed.

Operator hotline added to geosearch results

Hotline number has been added to some of the more popular CPOs and now this data
is also exposed in the API (in operator.hotline field). Look at Location response.