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. We have also added support for multiple keys per contract_id, so your organization can be configured to either only allow one key or multiple keys per contract_id. For details, see Tokens module.

A new webhook event is now available: SESSION_FEE_INCURRING.
This event notifies your system that an ongoing charging session may incur an additional non-energy fee if it is not stopped before a specified time (e.g., occupancy, congestion, or blocking fees). This can be used to trigger proactive push notifications to drivers to help them avoid fees. More information can be find on the Session incurring fee section of the documentation.

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.