EMP mode

Drive API's EMP mode (eMobility Service Provider mode) is designed for companies and service providers who manage fleets and need a simplified integration to handle charging keys without managing individual user accounts through Plugsurfing. This mode focuses on enabling charging services for your fleet efficiently, without adding unnecessary complexity.

Key features of EMP mode

Charging Key Management: You can create, enable, disable, and retrieve charging keys for your fleet. These keys are the primary tool for accessing charging services.
Fleet-Centric Operations: All operations are performed at the fleet level. Plugsurfing does not store or manage individual user accounts, making the process lightweight and streamlined.
Simplified Integration: EMP mode is ideal for organizations that prefer to manage their user relationships independently while leveraging Plugsurfing for charging key services.

Who is EMP mode for?

This mode is perfect for businesses or mobility providers who:

Operate EV fleets and require a straightforward way to manage charging access.
Want to keep user management entirely within their own systems.
Are looking for a minimalistic integration focused on charging key functionality.

How EMP mode differs from standard mode

Unlike the standard mode, which provides full-featured integration—including user account management, real-time charging station data, remote session control, and payment processing—EMP mode focuses solely on managing charging keys for fleets. It is a simpler, more targeted approach for businesses that do not need the additional user-level features.

By choosing EMP mode, you gain a lightweight, fleet-focused solution for accessing Europe’s largest EV charging network through Plugsurfing.

This document provides an overview of the endpoints that do not require a user association in the request.

Endpoints

Get Charging Keys

API Reference

Returns all charging keys associated for the given fleetId. If no fleetId is set, returns all charging keys.

The response is paginated, and if there are more keys than can be returned in a single response, a cursor property is included. This cursor can be used in subsequent requests to retrieve additional keys, until there are no more results, at which point the cursor will be omitted from the response.