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

Release v1.1.3

by ReadMe API

v1.1.3 - 24.10.2022

⚡️ Features

New get-subscription-by-id endpoint

Subscriptions got a new endpoint which can be useful
for checking single subscription status or details.

Charging Key Ordering receipt improvements

New field was added to Charging Key Ordering endpoints called 'hasReceipt'.
Also, when fetching a receipt for a session, this variable is firstly checked
and an error is returned if the receipt is not available. Previously a non-working
url was sometimes returned.

🪲 Bug Fixes

Proper address validation for incorrect characters in Charging Key Ordering

Previously incorrect characters in address when ordering resulted
in 500 response code. This has been fixed and now 400 response with
a correct message will be returned.

Geosearch power filtering

In some cases power filtering would filter out valid stations.
Now the filtering works correctly for all stations.

Location-by-id returns very slowly

For some locations this endpoint returned response very slowly or even timed out.

Release v1.1.2

by ReadMe API

v1.1.2 - 04.10.2022

⚡️ Features

Location-by-id – user-based pricing

Location by id endpoint was improved, so the pricing returned
can take into account particular user's preferential pricing.

Subscription endpoints extended

Subscriptions - now when subscribing or listing user's subscriptions more details
are returned like subscription name or start and end dates.

Remote start/stop enabled for external chargers

External chargers now have the possibility to start remote charging.
This is also reflected in the capabilities field in Geosearch results.

This change is enabled at first only for some CPOs, but the coverage will be extended over time.

Release v1.1.1

by ReadMe API

v1.1.1 - 06.09.2022

⚡️ Features

Charging key ordering - handling multi-currency configuration

Charging Key ordering was restructured to account for
multiple currencies and countries.

Release v1.1.0

by ReadMe API

v1.1.0 - 26.08.2022

A quite big, summer release bringing many new features and a lot of under-the-hood improvements,
which will be continued and expanded in upcoming releases.

⚡️ Features

Charging key order - receipt and configuration

Charging Key ordering received new endpoints. Configuration endpoint let's you know
which countries and currencies are configured. Receipt endpoints gives you an url to get Receipt
if the order was successfully paid for.

New Geosearch filters - open247 and openNow

Two new filtering options appeared in Geosearch Radius and Route endpoints:

  • open247 - returns only chargers open 24/7
  • openNow - returns only chargers open at this moment
    (based on charger local time and opening times provided by CPO)

New endpoint - Delete a user

There is now a possibility to permanently remove a user from our system.
There are some requirements described further in Users section.

New API section - User Feedback

We added a new section - User Feedback.
Right now only feedback regarding a single location or connector is possible,
but we plan to add other like session feedback.

🪲 Bug Fixes

Removed ‘Missing’ values from operator name and address

Many chargers had "Missing" stated as operator name or address,
which was confusing for the users.
Now we are removing these values from those two fields.

Removed duplicated connectors

Some connectors were duplicated
(we recognize it by having two connectors of the same type on one EVSE).
Now we remove them before returning the response.