We’ve added a new field, operator_display_name, to locations. This field provides more accurate information about the site’s operator. A single operator can have different operator_display_name values across locations.

For details, see the API Reference.


We’ve added support for real-time authorization of locally started sessions. This allows you, for example, to pre-authorize a user’s payment method and then allow or deny the session start based on the result.

For details, see the Session pre-authorization guide.


We've added support for verifying HMAC signatures on incoming webhook requests to enhance security and ensure data integrity.

Learn how to implement it in your integration: Verifying HMAC Signature.

Release v1.1.24

by Plugsurfing

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.

Release v1.1.23

by ReadMe API

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.

Release v1.1.22

by ReadMe API

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.