Learning Hub/Scenarios
Explanations use OCPI 2.2.1. Physical and billing-system events are authored examples.

CPO sends a PATCH with the energy so far

Advanced
5 min
OCPI 2.1.1, 2.2.1 and 2.3.0
CPO sends a PATCH with the energy so far

As power flows, the CPO sends a PATCH with the energy delivered so far and a new last_updated. The eMSP's copy is ACTIVE at 18.4 kWh.

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
Explore the sessions module →
Message Flow⚡UUserCChargerCCPOsendereeMSPreceiverStep 2 of 4