Standard OCPI and Road's extensions

The Road Roaming Hub speaks standard OCPI, in versions 2.1.1, 2.2.1 and 2.3.0. A CPO or eMSP that implements the specification can connect without anything Road specific, and for most partners that is all there is to it.

Some partners need more than the standard offers. A payment terminal provider needs to know whether a plug is free, which the OCPI EVSE status does not say precisely enough. A loyalty or smart charging provider needs access to a driver's sessions, with the eMSP's permission. Road builds these as extensions: extra fields, extra endpoints and modules, and changes to how an existing endpoint behaves. They are documented so that a partner can find out what exists from the documentation, without asking us or discovering it by failing.

How extensions are enabled

Extensions are enabled per connection, and Road does it. A partner tells the roaming team what it needs, and Road turns it on for that connection. Nothing changes for any other partner, and a connection with nothing enabled behaves exactly as the OCPI specification says.

New endpoints and modules that OCPI does not have are available on every connection, and a partner that does not call them is unaffected. Anything Road pushes to a partner, such as CDR funding and delivery notifications, is sent only after the partner has asked for it and given Road its endpoint.

Because this differs between connections, the documentation describes what exists and how to get it. It does not show what is enabled on your own connection.

Where to read the details

The Roaming Hub API reference shows the full specification for each OCPI version with Road's additions marked, and How Road differs from OCPI lists them. To have an extension enabled, contact the roaming team at [email protected].