OCPI 2.2.1
Compare this step across versionsHow two OCPI platforms register, discover each other's module endpoints and then exchange locations, tokens, Sessions and CDRs.
0 / 6 completed
One platform asks and the other answers. Here is the shape of one exchange between an eMSP and a CPO:
One exchange
eMSP
→
Asks for information
→
CPO
CPO
→
Sends the answer back
→
eMSP
Authorization follows the Token's whitelist policy. ALWAYS uses whitelisting without real-time authorization; NEVER requires a real-time authorization request.
What they exchange
Locations
Tariffs
Tokens
Sessions
CDRs
Commands
One platform asks, the other answersEach module carries one kind of dataAuthorization follows the Token whitelist policy
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.