Guest organisation
OCPI
Learn reference
Guest organisation
OCPI
Learn reference

Real-time updates during charging

By Abhishek Uniyal · Updated

Step 3 of 11

OCPI 2.2.1

Compare versions

OCPI Session updates carry changes from the charging network operator to the driver service provider. A Session is the shared charging record; its updates describe the state and recorded energy.

What changes in OCPI 2.2.1
Modules in OCPI 2.2.1
Sessions
CDRs
Locations
Tariffs
Tokens
Commands
Credentials
Versions
Hub Client Info
Charging Profiles
Payments · extension
Advertised sender and receiver interfaces

An endpoint declares how another platform can pull or push data. Credentials uses the same interface for both roles.

The header token is encoded

The request header carries an encoded token; the Credentials body still carries the raw token.

Billing records name the Token owner

A charge record names the country and company that own the driver's Token.

Which OCPI messages are exchanged?

  1. CPOeMSP

    New Session

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

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

    Response

    {"status_code": 1000, "timestamp": "2026-10-16T09:30:00Z"}
    Sources (4)
    "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."OCPI 2.2.1 Sessions module · #mod_sessions_push_model"We also advise that in such cases, platform sending the response leave the `data` field unset in the response format. This applies for example to PUT requests when pushing Session objects, and PATCH requests to add charging periods to Sessions."OCPI 2.2.1 Transport and format chapter · #transport_and_format_response_format"OCPI status code, as listed in Status Codes, indicates how the request was handled. To avoid confusion with HTTP codes, OCPI status codes consist of four digits."OCPI 2.2.1 Transport and format chapter · #transport_and_format_response_format1000: Generic success codeOCPI 2.2.1 Status codes chapter · #status_codes_1xxx_success
  2. CPOeMSP

    Session update

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

    In OCPI 2.2.1 and 2.3.0 the CPO sends every change to a Session it already pushed by calling PATCH on the eMSP's Sessions endpoint. Only the fields that need to be updated have to be present, and any field it does not specify is considered unchanged. Every PATCH request SHALL contain last_updated.

    Response

    {"status_code": 1000, "timestamp": "2026-10-16T09:30:00Z"}
    Sources (3)
    "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."OCPI 2.2.1 Sessions module · #mod_sessions_push_model"Same as the PUT method, but only the fields/objects that need to be updated have to be present. Fields/objects which are not specified are considered unchanged."OCPI 2.2.1 Sessions module · #mod_sessions_patch_method"Any request to the PATCH method SHALL contain the `last_updated` field."OCPI 2.2.1 Sessions module · #mod_sessions_patch_method