Real-time updates during charging

Intermediate

OCPI 2.1.1

Compare this step across versions

Technical details off

How the CPO keeps the eMSP informed about a Session while energy flows to the vehicle.

0 / 5 completed

Who takes part in a charging session

Starting a charging session

Real-time updates during charging

Finishing the charging session

Order the charging session messages

What happens while you're charging?

What You'll Learn:

How the CPO pushes a new Session to the eMSP with PUT
How the CPO sends each change to that Session with PATCH
What the eMSP answers

The Players in This Lesson:

CPO

eMSP

EMSP

Message Flow:

Step 0 of 2

CPO

PUT /sessions/{country_code}/{party_id}/{session_id}

eMSP

Message: New Session

Details: The CPO pushes the Session it just created to the eMSP's Sessions endpoint.

Response: {"status_code": 1000, "timestamp": "2026-10-16T09:30:00Z"}

"When the CPO creates a Session object they push it to the eMSPs by calling PUT on the eMSPs Sessions endpoint with the newly created Session object."OCPI 2.1.1 Sessions module · #11-push-model"Response code, as listed in Status Codes, indicates how the request was handled. To avoid confusion with HTTP codes, at least four digits are used."OCPI 2.1.1 Transport and format chapter · #response-format"|1000 |Generic success code"OCPI 2.1.1 Status codes chapter · #1xxx-success

CPO

PATCH /sessions/{country_code}/{party_id}/{session_id}

eMSP

Message: Session update

Details: In OCPI 2.1.1 the CPO sends every change to a Session it already pushed by calling PATCH on the eMSP's Sessions endpoint. The request carries only the fields that have to be updated; any field it does not specify is considered unchanged.

Response: {"status_code": 1000, "timestamp": "2026-10-16T09:30:00Z"}

"Any changes to a Session in the CPO system are sent to the eMSP system by calling PATCH on the eMSPs Sessions endpoint with the updated Session object."OCPI 2.1.1 Sessions module · #11-push-model"Same as the PUT method, but only the fields/objects that have to be updated have to be present, other fields/objects that are not specified are considered unchanged."OCPI 2.1.1 Sessions module · #223-patch-method

What OCPI 2.1.1 defines for this lesson

Modules in this version

Locations

Sessions

CDRs

Tariffs

Tokens

Commands

Credentials

Hub Client Info

Charging Profiles

Payments

Bookings

No advertised interface-role field

Endpoint descriptions name the module and URL without an interface-role field.

The header carries the token value

The request header carries the shared credentials token value.

Session ID uses case-sensitive text

The Session ID uses text whose letter case matters.