> ## 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. # Get location live data > Returns live charging data for the EVSEs of a location that are in use, including since when each EVSE has had its current live status. The `charge_point_statuses` keys match the EVSE `uid` values returned by Get location by id. EVSEs without live data are omitted. Returns `404` when the location is not found or live data is not enabled for your organization. For details, check /docs/drive-api/geosearch#location-live-data ## OpenAPI ````yaml reference/openapi.json GET /emp/v1/locations/{locationId}/live-data openapi: 3.1.0 info: title: Drive API version: 1.0.0 description: >- The Drive API provides comprehensive access to Plugsurfing's charging infrastructure network. It enables you to manage users, charging keys, search for charging locations, handle payments, and control charging sessions. servers: - url: https://{environment}.plugsurfing.com variables: environment: enum: - drive-api-stage default: drive-api-stage description: >- API environment - use drive-api-stage for testing and drive-api for production security: [] tags: - name: Geosearch description: >- Search and retrieve detailed information about charging locations and stations - name: Users description: >- Manage user accounts including creation, retrieval, updates, and deletion. Handles user-specific data and preferences. - name: Charging Keys description: >- Manage physical and virtual charging keys including creation, activation, updates, and status management. Essential for user access to charging stations. - name: Sessions description: >- Access and manage charging session data including history, status, and detailed session information - name: Remote Charging description: >- Control charging sessions remotely including starting and stopping sessions, and monitoring session status - name: Payment Options description: >- Manage payment methods and handle transaction processing for charging services - name: User Groups description: Manage user group memberships - name: Vouchers description: Redeem vouchers - name: Charging Key Orders description: Handle the ordering and fulfillment process for physical charging keys - name: EMP Charging Keys description: E-Mobility Provider specific endpoints for managing charging keys - name: EMP Geosearch description: E-Mobility Provider specific endpoints for location search and information - name: EMP Orders description: E-Mobility Provider specific endpoints for managing orders - name: EMP Sessions description: E-Mobility Provider specific endpoints for managing charging sessions - name: EMP Fleets description: E-Mobility Provider specific endpoints for managing fleets paths: /emp/v1/locations/{locationId}/live-data: get: tags: - EMP Geosearch summary: Get location live data description: >- Returns live charging data for the EVSEs of a location that are in use, including since when each EVSE has had its current live status. The `charge_point_statuses` keys match the EVSE `uid` values returned by Get location by id. EVSEs without live data are omitted. Returns `404` when the location is not found or live data is not enabled for your organization. For details, check https://developer.plugsurfing.com/docs/geosearch#location-live-data operationId: getEmpLocationLiveData parameters: - name: locationId in: path description: Location id. required: true schema: type: string - name: fleetId in: query description: >- Optional - the id of the fleet organization, will be used for fleet-specific location context. If fleet id is not provided, the EMP location context will be used required: false schema: type: string responses: '200': description: Live data of the location EVSEs content: application/json: schema: $ref: '#/components/schemas/LocationLiveData' example: charge_point_statuses: ee006b89511e81534e019ca0d9a780b351e9: status: CHARGING status_since: '2025-01-15T08:12:00Z' '404': description: Location not found or live data not enabled for your organization content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: message: Resource not found '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: message: Internal server error security: - ApiKeyAuth: [] components: schemas: LocationLiveData: required: - charge_point_statuses type: object description: Live charging data of the EVSEs of a location. properties: charge_point_statuses: type: object description: >- Live data by EVSE `uid`. The keys match the EVSE `uid` values returned by Get location by id. Contains only EVSEs that are in use and have a known live status start time. Empty when no live data is available. additionalProperties: $ref: '#/components/schemas/ChargePointLiveData' ErrorResponse: title: ErrorResponse type: object properties: message: type: string ChargePointLiveData: required: - status - status_since type: object description: >- Live status of an EVSE, tracked by Plugsurfing from the charger status updates. properties: status: type: string enum: - CHARGING - OCCUPIED - RESERVED description: >- Live status of the EVSE. It is tracked separately from the EVSE `status` returned by Get location by id, so the two can differ. status_since: type: string format: date-time description: >- Time since which Plugsurfing has continuously tracked the live `status` of the EVSE. For `CHARGING`, it is the start of the current charging occupation. It is based on status updates, so it can differ from the actual session start. It is not the EVSE `last_updated`. example: '2025-01-15T08:12:00Z' securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: API key for authentication ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.