Charging journeys
Run one charging journey at a time against your real endpoint. ChargerDojo plays the counterparty, runs the timing and disturbances you choose, and grades every answer a rule covers.
Free sandbox, no login. Your own endpoint needs a plan.
First successful charge
An eMSP is sent a complete charging journey and each answer is graded
Authorization prerequisite
A stable token is ready
Live charging session
Session state changes over time
Completion and billing
Receiver answers for the final Session and CDR are inspected
OCPI conformance
Cites the OCPI clause it rests on
Business checks
Names the business check it rests on
Observations
Graded on their own
Run integrity is reported first. The request and response sit behind every check that sent one.
About charging journeys
A charging journey runs a timed, end-to-end OCPI charge against your registered partner endpoint: a charge with Session updates and its close, remote start and stop, catalogue pushes and recovery after an outage, and you inspect the final CDR. ChargerDojo plays the counterparty, drives configurable update cadences and real-world disturbances, and grades each answer, citing the OCPI clause or naming the business check it rests on. 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, business checks and observations are graded independently, with run integrity reported first. The request and response sit behind every check that sent one.
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 with a paid plan.
Common questions
What is a charging journey?
A charging journey drives one charge against your endpoint on a timed schedule, playing the other side of each message: find a Location, authorize, charge with live updates, close the Session and send the CDR, 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 separate lanes: OCPI conformance against the published specification text, 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.