Why OCPI matters

Beginner

By Abhishek Uniyal · Updated

Step 2 of 6

OCPI connects charging platforms for roaming. They exchange locations, prices, authorization and charging records used for billing.

Sources (2)
"The Open Charge Point Interface (OCPI) enables a scalable, automated EV roaming setup between Charge Point Operators and e-Mobility Service Providers."OCPI 2.2.1 specification · #introduction_introduction_and_background"A *Charge Detail Record* is the description of a concluded charging session. The CDR is the only billing-relevant object."OCPI 2.2.1 CDRs module · #mod_cdrs_cdrs_module
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.

Why do charging networks connect?

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.

Which information can they share?

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