Skip to main content
The EV Roaming Tester runs your partner’s OCPI implementation against the specification and gives you a report you can forward, with the request and response behind every check. Everything in these guides is driven the same way: an HTTPS call to https://evsim.synergyboat.com with your evrt_ API key. It exists for one situation: you are mid-integration, you have a deadline, and you and your partner disagree about whose side is wrong.

​
The path

  1. Create an API key in the app and store it in your CI secret manager.
  2. Run the quickstart against the built-in sandbox to see a full loop work.
  3. Connect a partner: create the connection and run the live registration handshake.
  4. Run a conformance suite or a charging journey against it, from a script or from CI.
  5. Read the report and share it with your partner.
When something answers a status code you did not expect, the troubleshooting page maps every public status to what it means and, more importantly, keeps “your partner broke a rule” separate from “we did not get an answer”.

​
What these guides will not claim

A green run is not certification. We are not the EV Roaming Foundation. A run here is evidence, and good evidence, but if you need a certificate you need them, not us. A warning is not a failure. The specification distinguishes what you must do from what you should do, and so do we. A partner who declines a recommendation has broken no rule, and no verdict here will say otherwise. Read your report explains why this matters more than it sounds. The API is deliberately small. The operations documented in the API reference are the public contract, each one owner scoped and authenticated by your key. The interactive simulator in the browser is a different tool for a different job, and its internals are not part of this contract.