We added three new fleet management endpoints to support fleet organization and administration:

• POST /emp/v1/fleets - Create a new fleet organization with a unique fleet identifier and optional name
• PUT /emp/v1/fleets/{fleetId}/rename - Update the name of an existing fleet without changing its identifier
• GET /emp/v1/fleets/{fleetId}/invitation - Retrieve active invitation codes for a fleet to enable secure user onboarding

These endpoints enable centralized management of charging keys and users under fleet organizations. See the Fleet Management guide for detailed usage examples.

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

https://developer.plugsurfing.com/reference/listoperators

The batch location endpoint have been improved: pagination is now stateless, and the performance has been improved.