Data Submission

Instructions

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

General implementation principle

The OCPI integration must follow the standard OCPI 2.3.0 specification.
No proprietary extensions or vendor-specific deviations are expected.

JSON Examples

• 2.3.0 version endpoint

  The version endpoint must be accessible without authorization and must expose the implemented OCPI 2.3.0 modules according to the standard specification.
  The following OCPI modules are used by the system and must be implemented according to the standard specification:

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

Parking object – standards field

The "standards" field is used to indicate applicable technical or infrastructure standards (e.g. national or international regulations).

Important:
For data processing purposes, the system checks for the presence of the reference "3-101/D1-26" in the standards field in order to determine whether the parking place is accessible for all groups of society, as defined in the regulation No. 3-101/D1-26.

Data providers should ensure that this reference is included in the standards field when applicable.