OCPI Interoperability Tester
Every run you have made and the endpoints they ran against
Latest runs
Endpoints
Quick actions
Run a charging journey
Drive a timed OCPI journey against your endpoint and read graded verdicts
Run a conformance suite
Execute OCPI conformance tests against the sandbox or your own endpoint
Walk a guided scenario
Step through a complete charging session, message by message
Explore OCPI modules
Interactive reference for Sessions, CDRs, Locations, and more
An OCPI integration rarely fails loudly. It fails as a session that never closes, a charge detail record the other side rejects, a tariff that does not match the one the driver was quoted. By the time anyone notices, the evidence is an incident report from a partner and a log you cannot reproduce.
This is the surface where you catch that first. Register the endpoint you are building, run a conformance suite against it, and read what actually came back. Every check keeps the request it sent and the response it received, so a failure names the field, the status code, and what the specification expected instead. Runs are durable, so you can fix, replay, and prove the fix with the same input.
Where to start
If nothing here has run yet, the fastest first result is a suite against the built-in sandbox in the OCPI testing tool. If the protocol itself is new to you, read what the Open Charge Point Interface is and watch a charging session run end to end in the simulator before you test one. The Learning Hub takes a team from the basics to debugging in about two hours.
Common questions
What is EV roaming?
Roaming is what lets a driver charge on a network they have no contract with. Their e-mobility service provider vouches for them, the charge point operator runs the session, and the two settle up afterwards with a charge detail record. OCPI is the protocol they use to have that conversation.
What does this dashboard show me?
The endpoints you have registered, the conformance runs you have made against them, and the result of the most recent ones. On a first visit it is empty, which is the honest state: nothing has been run yet.
How do I get my first result?
Run a conformance suite. A sandbox peer is already registered for you, so you can get a real pass and fail report in the browser without registering an endpoint or signing in. Point a suite at your own endpoint when you want to test the integration you are shipping.
What does a failing check tell me?
Which request was sent, what came back, and which assertion the response failed. For example, that a response carried OCPI status_code 1000 where the specification required 2001, or that a session object was missing cdr_token. A failure you can act on, rather than a score you have to trust.