OCPI Roaming & Interoperability Testing
Test your OCPI 2.1.1 and OCPI 2.2.1 implementation without waiting for roaming partners. OCPPLab simulates CPO endpoints, eMSP endpoints, and hub connections so you can validate interoperability before going live.
What is OCPI?
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.
OCPI 2.1.1 Coverage
Validate the widely deployed roaming baseline used by many CPO and eMSP integrations today: credentials, locations, sessions, CDRs, tariffs, tokens, and commands.
OCPI 2.2.1 Coverage
Extend that validation to newer hub and smart-charging workflows including HubClientInfo, ChargingProfiles, richer tariff semantics, and newer interoperability requirements.
OCPI Modules We Test
- Credentials: Registration, version handshake, and token exchange
- Locations: Push and pull location, EVSE, and connector data
- Sessions: Real-time charging session monitoring and updates
- CDRs: Charge Detail Record generation and reconciliation
- Tariffs: Tariff data sync between CPO and eMSP
- Tokens: Authorization token validation (RFID, app, contract)
- Commands: Remote start/stop, reserve, and unlock connector
- ChargingProfiles: Smart-charging orchestration across the roaming chain (OCPI 2.2.1)
- HubClientInfo: Hub participant discovery and metadata exchange (OCPI 2.2.1)
GIREVE Hub Testing
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.
- Simulate GIREVE hub endpoints for CPO and eMSP roles
- Test hub-specific authentication and credential flows
- Validate CDR exchange through the hub
- Test multi-party roaming scenarios (CPO → Hub → eMSP)
- Verify location data propagation through hub infrastructure
CPO Registration
Test the full OCPI credentials handshake between your platform and a simulated eMSP or hub.
Cross-Platform Authorization
Validate that tokens from partner eMSPs are correctly authorized at your charge points.
Real-Time Session Sync
Verify that charging sessions are correctly reported to roaming partners in real time.
CDR Reconciliation
Test CDR generation, transmission, and reconciliation across CPO-eMSP boundaries.
Location Data Updates
Validate that EVSE availability, pricing, and connector status propagate correctly.
Error Handling
Test how your platform handles expired tokens, network timeouts, and malformed responses.
Related Resources
Test roaming without roaming partners
Simulate CPO, eMSP, and hub endpoints. Validate OCPI end-to-end.
Last updated: