For charger brands

Register your integration

Do you build chargers? Register your integration here and we read your customers' charging sessions and file them with the NEa, the Dutch emissions authority. This is the technical track. It runs without a commercial contract, because the customers who own your charger stand on their own.

MID first

Without a MID meter inside the charger housing, an integration produces no billable kWh. So that question comes first.

Three routes

Your cloud API, OCPP 1.6J, or the back-office you run on. We pick the route.

Test setup

With a demo unit or a sandbox we validate the sessions before anything goes live.

Already connected

We read 15 brands through their own cloud API.

Blue Current
ChargeAmps
Easee
Ecotap
Enphase
go-e
NexBlue
Ohme
Smappee
SolarEdge
Tesla
V2C
Victron
Volt Time
Wallbox
Zaptec

Plus charging platforms, CPO portals and any other brand over OCPP 1.6J.

Brand and company

Brand name

Company name

Country

Website

Contact person

Preferably someone who knows the technology. We contact this person about outages and new models.

Name

Phone

Role

Models

One row per part number. MID status often differs per variant: the same model name has no meter in single phase and does have one in three phase. As evidence, a link to the manufacturer declaration, the type-examination certificate or the datasheet page that names the meter is enough.

Model 1

Model name

Part number

Power (kW)

Phases

MID-certified meter

Meter inside the charger housing

Link to the MID evidence

Integration route

Your own cloud APIWe fetch the sessions from your backend, with the customer's consent.OCPP 1.6JThe charger talks to our gateway directly. No integration code needed.Through a back-officeYour chargers run on another party's platform.Not sure yetWe pick the route and tell you what it takes.

Notes on the route

Test setup

We check on our test environment whether the sessions are billable. A demo unit works, and so does a sandbox account on an existing charger. What we look for:

•Every session carries a start time, a stop time and a kWh value.
•There is a meter reading at start and at stop, not just the difference.
•The device is identified by a serial number that survives a reboot.
•History goes back to 1 January 2026, or to commissioning.
•Fetching twice never produces a duplicate session.

Can you supply a test setup

Notes

Finally

What do you want to discuss

This choice changes nothing about the integration. We build that without a contract too.

Anything else

We reply within two working days. Want to read the technical side first? It is on the developer page.