Guided Scenarios
Walk through real OCPI workflows step by step. Each scenario explains what happens, why it matters, and shows the actual payloads exchanged between parties.
How roaming works
Follow a real OCPI flow end to end, from the first message to the final record.
When it breaks
The failures worth being able to spot: a refusal, a silent gap, a bill that does not add up. Each one shows what the spec requires.
The failures worth being able to recognise
A guided scenario is a roaming flow that goes wrong on purpose. An expired token, a status code that says success where the specification demands an error, a CDR with a field the other side requires and you never sent. You run it, watch it break, and learn what that particular failure looks like from the outside.
This matters because in production you never get told what is wrong. You get a partner saying sessions are not reconciling, and a log. Recognising the shape of a failure you have seen before is most of the debugging.
Where to go next
Common questions
What are OCPI guided scenarios?
Guided scenarios are step-by-step walkthroughs of real-world OCPI workflows such as charging sessions, roaming registration, remote commands, and billing. Each scenario shows the actual API payloads exchanged between CPO and eMSP.
How do guided scenarios help with OCPI integration?
Scenarios break complex multi-step OCPI flows into individual steps with explanations and real payloads, so integration teams can understand exactly what data is exchanged at each stage before writing code.
Are these real failures?
They are the failure modes the conformance suites assert against, which are the ones the specification defines and partners actually hit: wrong envelope status codes, missing required fields, methods that are not allowed on an interface, and sequences that arrive out of order.