Simulate charging sessions, validate compliance across all OCPI versions, and ship roaming integrations with confidence. Free for CPOs and eMSPs.
All OCPI versions
10 modules
No login required
evsim.synergyboat.com/ocpi-testing-tool
Whether you are a charge point operator validating roaming, an eMSP testing token flows, or a QA engineer building release gates.
Test roaming integrations before going live with new partners. Catch session failures, CDR mismatches, and credential issues in a simulator instead of production.
Open roaming testerVerify that token authorization, session updates, and tariff calculations behave correctly across OCPI versions before your drivers see errors.
Open testing toolRun reproducible OCPI scenarios against every module. Get clear pass/fail evidence for release gates instead of guessing at protocol compliance.
Open simulatorStop guessing whether your OCPI implementation is correct. Run a scenario, see where it breaks, fix it, and prove the fix works — all in one tool.
1
Choose OCPI 2.1.1, 2.2, or 2.2.1. Set whether you are acting as CPO, eMSP, or both. Define the module and scenario you want to validate.
2
Execute one charging session, credential exchange, or CDR flow. Keep variables isolated so results are conclusive, not noisy.
3
The simulator highlights the first protocol mismatch — wrong status code, missing field, unexpected sequence — with the full message context.
4
After making changes, replay the exact same scenario. Identical input, comparable output. That is how you prove the fix works.
Validate all 10 OCPI modules — from credential exchange to CDR settlement. Each includes checks for the interoperability issues that actually cause incidents.
Verify version discovery and endpoint negotiation between parties
Test credential exchange, token registration, and trust setup
Validate EVSE data, connector status, and location sync accuracy
Trace session lifecycle from start to stop with status transitions
Check billing records for completeness, accuracy, and settlement readiness
Confirm tariff rules, pricing elements, and time-based applicability
Test token authorization flow, whitelist sync, and status handling
Validate remote start/stop, reserve, and unlock command responses
Verify power limit profiles and smart charging consistency
Check role declarations and routing through roaming hubs
Interactive tutorials paired with simulator scenarios. Learn the protocol by doing — not by reading a 200-page specification.
Structured path from OCPI beginner to confident debugger
Hands-on practice with real protocol scenarios, not just docs
Team alignment shared vocabulary across QA, CPO, and eMSP roles
1
Learn what CPOs and eMSPs exchange, which modules matter, and how roaming actually works under the hood.
2
Follow a charging session from authorization through CDR closure. See the exact API calls between parties.
3
Run failure scenarios — expired tokens, missing fields, wrong status codes — and learn to recognize common interoperability bugs.
4
Combine protocol knowledge with simulator evidence to pinpoint exactly where and why an integration fails.
Quick answers for CPOs, eMSPs, and engineering teams evaluating this tool.
Yes. The EV charging simulator and protocol testing tool are free to use without login. You can simulate full OCPI flows, inspect message payloads, and validate compliance at no cost.
Open EV Charging SimulatorThe platform covers OCPI 2.1.1, 2.2, and 2.2.1 across all 10 core modules: Versions, Credentials, Locations, Sessions, CDRs, Tariffs, Tokens, Commands, Charging Profiles, and Hub Client Info.
View module coverageOCPP handles communication between chargers and management systems. OCPI handles roaming between CPOs and eMSPs — a different layer entirely. This tool focuses on OCPI roaming interoperability, not charger-level OCPP messaging.
Learn OCPI vs OCPPYes. The Learn Hub pairs interactive tutorials with simulator scenarios so new engineers, QA, and product team members can build practical OCPI understanding — not just read documentation.
Open Learn HubPick your OCPI version and role (CPO or eMSP), run a single scenario like a charging session or credential exchange, inspect where the protocol behavior diverges from the spec, fix the issue, and replay the same scenario to confirm.
See how teams use it“We used to find OCPI bugs in production after partner complaints. Now we catch them before the first deploy.”
Integration Engineer, CPO
“The simulator finally gave our QA team a repeatable way to test roaming scenarios instead of manually crafting API calls.”
QA Lead, eMSP
“Onboarding new engineers on OCPI went from weeks of reading specs to days of hands-on practice.”
Engineering Manager, Charging Network