The Open Charge Point Interface (OCPI) is the protocol that enables EV roaming between Charge Point Operators (CPOs) and e-Mobility Service Providers (eMSPs). It handles everything from location data sharing to real-time authorization, charging session management, and billing reconciliation through Charge Detail Records (CDRs).
Testing OCPI is challenging because it requires two parties. You can’t test your CPO implementation without an eMSP to connect to, and vice versa. That gets even harder when you need to validate both OCPI 2.1.1 and OCPI 2.2.1 behavior across core roaming and hub-oriented modules.
Validate the widely deployed roaming baseline used by many CPO and eMSP integrations today: credentials, locations, sessions, CDRs, tariffs, tokens, and commands.
Extend that validation to newer hub and smart-charging workflows including HubClientInfo, ChargingProfiles, richer tariff semantics, and newer interoperability requirements.
If you connect to EV roaming through GIREVE, Hubject, or e-clearing, OCPPLab simulates the hub’s behavior so you can test your integration end-to-end.
Test the full OCPI credentials handshake between your platform and a simulated eMSP or hub.
Validate that tokens from partner eMSPs are correctly authorized at your charge points.
Verify that charging sessions are correctly reported to roaming partners in real time.
Test CDR generation, transmission, and reconciliation across CPO-eMSP boundaries.
Validate that EVSE availability, pricing, and connector status propagate correctly.
Test how your platform handles expired tokens, network timeouts, and malformed responses.
Simulate CPO, eMSP, and hub endpoints. Validate OCPI end-to-end.
Last updated: