Release v1.1.18
by ReadMe APIv1.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.
Release v1.1.17
by ReadMe APIv1.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.
Release v1.1.16
by ReadMe APIv1.1.16 - 26.07.2023
Unavailable price not presented
Sometimes the price is not available for a connector due to a mistake.
Until now, we were presenting "0" as a price in such cases, which was misleading for the end-user.
Now, for those cases, the price object will not be returned at all.
More details in: Prices
Bugfix: Charging key reservation dates
During code refactors there was a bug introduced, due to which some keys were reserved with incorrect validity dates.
A fix to this bug was pushed as a hotfix last week. Tests were also improved to catch such problems.
Internal changes
Among them was alarm fine-tuning, to avoid false-positive alarms and improved logging.
Release v1.1.15
by ReadMe APIv1.1.15 - 11.07.2023
Minor improvements
Several minor changes and improvements:
- unified ways of fetching prices across Plugsurfing services – enabling easier and more
centralized control over future improvements in pricing - improved internal alarming parameters and logging
- better input parameter validation
Release v1.1.14
by ReadMe APIv1.1.14 - 15.06.2023
New Geosearch filter
New Countries code filter which allows to search locations
by 3-letter country code values.
Fixed problem with remote session not being found for a brief moment
In some cases, right after starting a session and fetching this session
by id, an error was returned instead of the session.
It occurred only for less than a second after starting, but this problem is fixed now.
Release v1.1.13
by ReadMe APIv1.1.13 - 24.05.2023
New Geosearch filter
New EVSE Ids filter which allows to search locations
by parts of EVSE Ids.
Release v1.1.12
by ReadMe APIv1.1.12 - 09.05.2023
New event types
New event types are available to inform about session stopping or failing.
This provides the possibility to rely only on events received from Drive API,
instead of repeatedly checking session's status.
More details on Events page.
Remote charging – testing setup
We have created a setup designated for testing remote charging.
It allows to test both successful and error scenarios.
Details are described on Sessions page.
Release v1.1.11
by ReadMe APIRelease v1.1.10
by ReadMe APIv1.1.10 - 14.03.2023
Added contractId field for Charging Keys
In compliance with latest OCPI versions we have added a 'contractId' field
to Charging Keys responses (activate, get and patch Key endpoints).
We will be gradually filling this field for existing Charging Keys and
starting to fill it for newly created ones, so for now it's mostly a placeholder
for upcoming changes.
Further improvements to operator name
Continuing improvements from last release, we are making the operator name even more user-friendly
by having a possibility to set a display name that is separate from our internal organization name.
This display name, if available, will be reflected directly in the
operator.name field of a location. We will also very soon set this name for major CPOs.