Release v1.1.13

by ReadMe API

v1.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 API

v1.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 API

v1.1.11 - 03.04.2023

Charging Key info added in session data

Session response data has a new field called 'chargingKeyType'.
It will help distinguish sessions started with rfid from remote sessions.

Release v1.1.10

by ReadMe API

v1.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.

Release v1.1.9

by ReadMe API

v1.1.9 - 02.03.2023

Improved operator name

Operator name was not always readable and ready to be exposed to the end-user.
Automatic clean-up of this field was implemented (i.e. cleaning up company-postfix like "GmbH" or "AB").
Soon we will do further improvements to make this field even better for end-users.

Release v1.1.8

by ReadMe API

v1.1.8 - 13.02.2023

New domain

Both Drive API and the Swagger docs have new URLs! The API of course stays available also on the current URL.
Swagger on the previous URLs is not up to date for now, we will try to bring it in line with the new URL, though
please try to switch to the new one provided below (only Stage version will be used from now on).

Hopefully new domains will make it easier to access the API and documentation and differentiate between environments.

Drive API URL: https://drive-api.plugsurfing.com/ (https://drive-api-stage.plugsurfing.com/ for stage environment).

Swagger: https://drive-api-docs-stage.plugsurfing.com/

Minor improvements

  • Power output of connectors truncated to the whole watt (previously it could include decimal values based on the data received from CPO)
  • Improved response times for specific endpoint calls due to improved caching
  • Optimized utilization of resources through reusing connections to internal services
  • Improved logging for better and faster identification of issues

Release v1.1.7

by ReadMe API

v1.1.7 - 17.01.2023

Performance improvements of some internal processes, improved error handling.

⚡️ Features

Charging Key Reservations API

New endpoint in charging keys section that reserves a key
under the caller organization. Reserved key is ready to be activated
using the activation endpoint.

Release v1.1.6

by ReadMe API

v1.1.6 - 19.12.2022

⚡️ Features

New fields in geosearch results

We've added openNow, max_amperage and max_voltage
fields to geosearch results.

openNow flag state is based on opening_hours and is a helper
so the timezone-based logic does not have to be implemented on client-side.

Together with status field can be used to display charger status in a better way.

🪲 Bug Fixes

Fixed search area for geosearch-route

Geosearch-route search area was smaller
than expected based on distance field.

Release v1.1.5

by ReadMe API

v1.1.5 - 07.12.2022

⚡️ Features

Remote Charging enabled for external chargers

Now both external and internal chargers, supporting remote-charging,
have this feature enabled. Some CPOs are still disabled, because
the integration wasn't working as well as expected. We're
in contact with them to resolve any issues.

Release v1.1.4

by ReadMe API

v1.1.4 - 21.11.2022

🪲 Bug Fixes

Headers are case-insensitive

Solved the case-sensitivity problem for request headers that could result in unintuitive errors.

Error handler for the charging key patch endpoint

Charging Key - added an error handler for the charging key patch endpoint to return more details about caught errors.

Other

Upgraded Node.js to version 16