AFIR Article 20: What CPOs need to know about it

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.

1. Get access to Spirii’s API: you will first need to follow these authentication steps: https://developer.spirii.com/reference/authentication
2. 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.
3. Report ad hoc pricing data: via the Tariff ID in 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.

‍