> ## Documentation Index > Fetch the complete documentation index at: https://developer.plugsurfing.com/llms.txt > Use this file to discover all available pages before exploring further. # EMP mode EMP mode is a streamlined integration designed for fleet operators, enabling efficient management of charging keys without the need for individual user accounts. It focuses on providing simple, fleet-level access to charging services, making it an ideal choice for businesses that handle user relationships independently. 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 ### Fleet Management See: [Fleet Management](/docs/drive-api/fleet-management) Learn how to create and manage fleet organizations, including creating fleets and renaming them. ### Get Charging Keys [**API Reference**](/reference/listEmpChargingKeys) 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. ### Create a Charging Key [**API Reference**](/reference/createEmpChargingKey) ### Enable Charging Key [**API Reference**](/reference/enableEmpChargingKey) Enable a key (after it was previously disabled) for charging. The key used here needs to be **created** beforehand. ### Disable Charging Key [**API Reference**](/reference/disableEmpChargingKey) Disables a key. It will immediately make Plugsurfing reject all authorization requests made with this key. Note: Some CPOs store whitelisted keys, so in some rare cases it might take a bit longer time until charging is rejected.\` ### List Available Products [**API Reference**](/reference/getEmpProducts) Returns the products available Each product may include a `printing` object with a `printing.schema` field — a [JSON Schema (Draft 2020-12)](https://json-schema.org/draft/2020-12/schema) object that describes the printing payload your customers must supply when placing an order for that product. Use this schema to build dynamic forms, validate inputs client-side, or auto-generate UI components. Not all products require printing. If a product has no `printing` field, you can place orders for it without supplying a `printing` payload. ### Create a Charging Key Order [**API Reference**](/reference/createEmpChargingKeyOrder) Creates a charging key order for a fleet organization. One request creates one card order. See: [Fleet Card Orders](/docs/drive-api/fleet-card-orders) ### List Charging Key Orders [**API Reference**](/reference/listEmpChargingKeyOrders) Fetch a list of charging key orders belonging to supported organizations. ### Mark Charging Key Order as "Assigned" [**API Reference**](/reference/assignEmpChargingKeyOrder) ### Get Stripe Publishable API Key [**API Reference**](/reference/getStripePublishableApiKey) Returns the Stripe publishable API key to be used with your Stripe client-side code, when confirming `SetupIntent` or creating a `PaymentMethod`. ### Start Session [**API Reference**](/reference/startRemoteSessionEmp) Starts a remote charging session with the given charging key on the given connector. ### Stop Session [**API Reference**](/reference/stopRemoteSessionEmp) Stops the given remote charging session. Only sessions started remotely can be remotely stopped. ### Get Session by id [**API Reference**](/reference/getSessionByIdEmp) Returns charging session details ### EMP Fleet Context EMP geosearch search endpoints and Get location by id accept `fleetId` as an optional query parameter when you need fleet-specific context. ### Geosearch radius See: [Geosearch](/docs/drive-api/geosearch#radius-search) ### Geosearch rectangle See: [Geosearch](/docs/drive-api/geosearch#rectangle-search) ### Geosearch route See: [Geosearch](/docs/drive-api/geosearch#route-search) ### Get location by id See: [Geosearch](/docs/drive-api/geosearch#location-by-id) ### Location batch See: [Geosearch](/docs/drive-api/geosearch#locations-batch) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.