Why OCPI matters

Beginner

OCPI 2.2.1

Compare this step across versions

Why charging networks connect through OCPI: roaming between CPO and eMSP platforms and the information those platforms exchange.

0 / 6 completed
What is OCPI?
Why OCPI matters
Key players in OCPI
How OCPI works
OCPI roles knowledge check
Where to go after the OCPI primer

OCPI makes charging your electric car much easier by solving common problems:

Roaming access

OCPI supports roaming between participating CPO and eMSP networks. A provider's card or app works where those networks support it.

Simple Info Sharing

Connected platforms exchange charging locations, prices, Token information, Sessions and CDRs.

Charging records

Platforms exchange charging records that can support billing between connected parties.

Roaming depends on participating networksConnected parties use a shared protocolExchange charging data between platforms
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.