By April 2025, new EU regulations will change how public charging data is shared across Europe. Here’s what Charge Point Operators need to know - and how Spirii supports you to stay compliant.
Summary
|
First things first: What is AFIR?
AFIR — short for Alternative Fuels Infrastructure Regulation — is a major EU directive designed to make EV charging more accessible, transparent, and consistent across member states.
Part of that includes Article 20, which introduces data-sharing requirements for Charge Point Operators (CPOs) of public and semi-public chargers.
New to AFIR? Read our intro to the regulation here.
Or get more information directly from the European Commission
What does Article 20 require?
By April 14 2025, all CPOs operating public and semi-public chargers in the EU are required to report both static and dynamic data about their charging infrastructure to their country’s National Access Point (NAP) via an Application Programming Interface (API).
Each member state’s NAP serves as a centralised platform where the operators or owners can connect to publish their data.
The aim is simple: better interoperability, smoother user experiences, and more transparent EV charging infrastructure across Europe.
Static data includes:
- Location of the charging station
- Number of connectors
- Parking spaces for people with disabilities
- Contact details
- Opening hours
- Operator ID codes
- Connector types
- AC/DC current type
- Max power output of both station and EVSE
- Compatible vehicle types
Dynamic data includes:
- Operational status (e.g. in service/out of order)
- Real-time availability
- Ad hoc price
- Whether electricity is 100% renewable
Each country also appoints an Identification Registration Organisation (IDRO) to manage unique identification (ID) codes to identify operators of recharging points and mobility service providers.
How to share data with your National Access Point
There are two main ways to connect to your NAP, depending on the specific requirements of your country:
- Via a public API connection: CPOs can use Spirii’s API endpoint solution directly.
- If OCPI protocol is required: you or your service provider can use Spirii’s OCPI 2.3.0-compliant API endpoint as a starting point.
Failure to meet these requirements may lead to fines or limitations on your operations — so it’s important to get connected ahead of time.
Spirii makes compliance simpler
While it’s the CPO’s responsibility to report to their NAP and submit the relevant data, Spirii provides access to our flexible API endpoint solution to simplify this process and serve as the foundation for your integration.
All our endpoints follow OCPI 2.3.0, the first version fully aligned with AFIR.
Getting access to Spirii’s API and required data
By utilising Spirii's Developer Hub, CPOs can connect to their national access point (NAP) to provide the data for their public chargers.
- Get access to Spirii’s API: you will first need to follow these authentication steps: https://developer.spirii.com/reference/authentication
- Report all required static and dynamic data: this is done via the GET Locations V2 endpoint. It contains data about the location, EVSEs at the location, the operator, contact information, etc.
- Report ad hoc pricing data: via the
Tariff IDin the Locations V2 endpoint in combination with the Tariffs V2 endpoint for the detailed breakdown of the ad hoc price.
Country-specific National Access Points
Here’s an overview of how data sharing works across different EU countries:
Note: Some countries are still finalising their data-sharing frameworks under AFIR. Where the data sharing method is listed as “unknown” or “unconfirmed,” it means the national authority has not yet published a definitive standard. This information will be updated as each country completes its implementation process.
Austria
- National Access Point: https://www.mobilitaetsdaten.gv.at/en
- IDRO Authority: Federal Ministry for Climate Action
- Data Sharing Method: OCPI 2.2.1. CPOs typically use OCPI, but data is exposed from the NAP in DATEX II for EU-wide interoperability.
Austria organises the NAP as a directory without it actually collecting and storing the data itself, which is done by E‑Control at www.ladestellen.at.
Belgium
- National Access Point: Transportdata Belgium - transportdata.be
- IDRO Authority: Regional Authorities (Flanders / Wallonia)
- Data Sharing Method: API
Cyprus
- National Access Point: traffic4cyprus.org.cy
- IDRO Authority: Public Works Department
-
Data Sharing Method: Unknown.
- AFIR-compliant EV charging datasets are already published on their NAPs, while the exact protocol is not documented.
Czech Republic
- National Access Point: Czech National Traffic Information Registry - https://registr.dopravniinfo.cz/en/
- IDRO Authority: Road Traffic Authority
- Data Sharing Method: Unknown
Denmark
- National Access Point: Dataudveksler
- IDRO Authority: Danish Road Traffic Authority (Trafikstyrelsen)
- Data Sharing Method: API (OCPI 2.2.1 / 2.3.0 mapping recommended by the Danish Road Traffic Authority).
Further guidance:
- Firstly, you should request a login to get access to the Danish NAP.
- After login in you follow the guidelines here: https://du-portal-ui.dataudveksler.app.vd.dk/guides
- Choose “Reference” when choosing “the technical nature of your data set”, and the type in the url that potential users should follow to access your data.
- It is sufficient to “submit information on you API” when creating a metadata description of your available data.
France
- National Access Point: QualiCharge - transport.data.gouv.fr
- IDRO Authority: Open Data Réseaux Énergies
- Data Sharing Method: API
Germany
- National Access Point: Mobilithek - mobilithek.info
- IDRO Authority: Bundesnetzagentur
- Data Sharing Method: DATEX II data profile
Beyond AFIR, Germany enforces the Eichrecht (Metering and Calibration Regulation), which imposes strict requirements on the calibration of charging equipment and transparency in pricing.
Ireland
- National Access Point: ChargePoint Ireland - data.gov.ie
- IDRO Authority: Transport Infrastructure Ireland (TII)
- Data Sharing Method: API (OCPI widely used; no officially mandated protocol published).
Italy
- National Access Point: cciss.it
- IDRO Authority: Ministry of Transport
- Data Sharing Method: Unknown
Latvia
- National Access Point: Latvijas valsts ceļi - transportdata.gov.lv
- IDRO Authority: Latvian Railways
-
Data Sharing Method: Unknown.
- AFIR-compliant EV charging datasets are already published on their NAPs, while the exact protocol is not documented.
Luxembourg
- National Access Point: data.public.lu
- IDRO Authority: Ministry of Mobility
- Data Sharing Method: API (protocol not publicly specified).
Netherlands
- National Access Point: National Charging Registry - ntm.ndw.nu
- IDRO Authority: National Agenda Laadinfrastructuur
- Data Sharing Method: OCPI 2.2.1. CPOs typically use OCPI, but data is exposed from the NAP in DATEX II for EU-wide interoperability.
Poland
- National Access Point: EIPA Register kpd.gddkia.gov.pl
- IDRO Authority: Office of Technical Inspection
- Data Sharing Method: DATEX II.
Romania
- National Access Point: CNAP - pna.cestrin.ro
- IDRO Authority: Romanian Auto Registry
- Data Sharing Method: Unknown
Slovenia
- National Access Point: E-Mobility SI - nap.si
- IDRO Authority: Ministry of Infrastructure
- Data Sharing Method: Not publicly specified (NAP provides EV charging data and ID codes).
Spain
- National Access Point: ESNAP - nap.dgt.es
- IDRO Authority: DGT Traffic Authority
- Data Sharing Method: DATEX II v3 (via HTTP API).
Sweden
- National Access Point: NOBIL - trafficdata.se
- IDRO Authority: Swedish Energy Agency
- Data Sharing Method: OCPI 2.2.1