OCPI 2.2.1
Compare this step across versionsInspect one OCPI request, its response and its outcome in the simulator message log.
0 / 5 completed
Now let's dive deep into the OCPI messages that flow between entities. Understanding message structure and content is key to working with OCPI.
Message Types You'll See
Authorization Messages
Used to verify if a driver is allowed to charge.
POST /tokens/NL/TNM/123456/authorize
Session Messages
Track charging progress and status.
PUT /sessions/NL/TNM/ABC123
CDR Messages
Final billing records for completed sessions.
POST /cdrs
Location Messages
Charging station and EVSE information.
PUT /locations/NL/TNM/LOC001
What OCPI 2.2.1 defines for this lesson
Modules in this version
Locations
Sessions
CDRs
Tariffs
Tokens
Commands
Credentials
Hub Client Info
Charging Profiles
Payments
Bookings
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.