Data Submission

Instructions

1. Upload OCPI data access address, example: https://ev.vialietuva.lt/ocpi/ 
2. Press the "Reload package data" button and wait for the station data to load

JSON Examples

• 2.3.0 version endpoint
  The version endpoint should be accessible without authorization. The version array provides all implemented OCPI standard version endpoints.
• Versions - OCPI 2.3.0 Standard Reference
• Credentials - OCPI 2.3.0 Standard Reference
• Locations - OCPI 2.3.0 Standard Reference
• Tariffs - OCPI 2.3.0 Standard Reference

EVSE ID Generation Requirements

EVSE identifiers (EVSE IDs) must be generated in the charging service operator’s system and provided through the OCPI interface.
To ensure consistency, clear data linking, and a unified structure across the entire system, each EVSE ID must follow a standardized format.

Key principles

The EVSE ID must always begin with the same prefix as the station’s Location ID.
Each charging point (connector) must have a unique suffix, appended to the station’s ID.
The structure must allow clear identification of which EVSEs belong to which charging station.
EVSE IDs must be stable — they cannot be changed after being created.

Example structure

Charging station ID (Location ID):

LT*IBG*E7GEP

EVSE IDs for this station:

LT*IBG*E7GEP*A
LT*IBG*E7GEP*B
LT*IBG*E7GEP*C
…

Logic

• The first part (LT*IBG*E7GEP) identifies the charging station.
• The final character (A, B, C, …) identifies a specific EVSE (connector).

This ensures that each EVSE ID is naturally linked to the corresponding station and enables our system to correctly recognize the hierarchy of charging infrastructure components.