Send a Session update

OCPI 2.1.1

Technical details off

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.

"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

Sandbox run · OCPI 2.1.1

Run this exchange in the sandbox

Sessions cannot be deleted. The final status of a Session is COMPLETED.

"Sessions cannot be deleted, final status of a session is: `COMPLETED`."OCPI 2.1.1 Sessions module · #11-push-model

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.