Explanations use OCPI 2.2.1. Physical and billing-system events are authored examples.
CPO opens and pushes the Session
Advanced
5 min
CPO opens and pushes the Session
The driver plugs in and charging begins. The CPO opens Session session-4471 and pushes it to the eMSP, so the driver's app can show charging.
Sandbox run · OCPI 2.2.1
Run this exchange in the sandbox
CPO
EMSP
"When the CPO creates a Session object they push it to the corresponding eMSP by calling PUT on the eMSP's Sessions endpoint with the newly created Session object. Any changes to a Session in the CPO system are sent to the eMSP system by calling PATCH on the eMSP's Sessions endpoint with the updated Session object. Sessions cannot be deleted, final status of a session is: `COMPLETED`. When the CPO is not sure about the state or existence of a Session object in the eMSP's system, the CPO can call GET on the eMSP's Sessions endpoint to validate the Session object in the eMSP's system."OCPI 2.2.1 Sessions module · #mod_sessions_push_model
Message FlowStep 1 of 4