New Endpoint: Get User's Prepaid Balance
by PlugsurfingWe have added a new endpoint that lets you retrieve a user's prepaid balance.
More details on the API reference.
We have added a new endpoint that lets you retrieve a user's prepaid balance.
More details on the API reference.
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.
We added a new endpoint that lets you list charging keys of a given fleet. If no fleet identifier is passed, all charging keys of the organization will be returned.
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.
The batch location endpoint have been improved: pagination is now stateless, and the performance has been improved.
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.
We fine-tuned our caching mechanism. Thanks to this, long geosearch queries
should happen much less often.
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.
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.
We've made some minor performance enhancements to our geosearch endpoints,
aiming to reduce the processing time of the most time-consuming requests.
We've addressed an issue where sessions that failed to initiate were not being
returned through the session-by-id endpoint in certain scenarios.
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.
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.