Charging Journeys
Prove one outcome at a time against your real endpoint. We run the timed OCPI journey and grade the answers.
I'm testing
against
Use your own setup
Tune a template, or import JSON to edit existing steps, timing and values.
About charging journeys
Charging Journeys runs timed, end-to-end OCPI journeys against your registered partner endpoint: find a charger, authorize, charge with live updates, stop, and inspect the final CDR. The tool plays the counterparty, drives configurable update cadences and real-world disturbances, and grades every answer against the official OCPI text with the clause cited. Runs are durable: a browser refresh, a lost stream, or our own runner restarting never invents a failure or loses evidence.
Verdicts stay separate: OCPI conformance, partner compatibility, business checks, and observations are graded independently, with run integrity reported first. Every verdict links to the exact request and response that proves it.
Choose a journey to start, or run a conformance suite for individual protocol checks.
Protocol and workflow detail
Write a custom journey that runs a 40 minute PUT-only session and delivers its CDR late, then save it and replay it from CI on the Integrate plan.
Common questions
What is a charging journey?
A charging journey is a timed, end-to-end OCPI story run against your endpoint: find, authorize, charge with live updates, stop, and bill, on a real or accelerated clock, with configurable disturbances such as dropped updates, a non-monotonic meter, or a late CDR.
How is a charging journey graded?
Every run is graded in four separate lanes: OCPI conformance against the published specification text, partner compatibility against named network profiles, business checks, and observations. A SHALL failure fails the lane, a SHOULD divergence warns, and simulator downtime is recorded as run-evidence integrity, never charged to the target platform.
Which OCPI versions can run a charging journey?
Charging journeys run against OCPI 2.1.1, 2.2.1, and 2.3.0 endpoints, for eMSP receiver and CPO sender roles, with a registered sandbox endpoint available so a journey can run without your own endpoint first.