Versions

The Versions module: the MOBI.Hub endpoints, the supported OCPI versions and how participants advertise their endpoints.

Technical considerations

As of this document, MOBI.Hub supports OCPI versions 2.2.1 and 2.2. Integration with the platform requires entities to explicitly expose the corresponding OCPI endpoints through the standard Versions and Version Details modules.

It SHALL be possible for a single role to rely on more than one technical platform for its OCPI implementation. However, for a given role and module, only one endpoint SHALL be advertised in the Version Details response.

Entities shall use the endpoints according to the role represented by MOBI.Hub in each interaction (SENDER or RECEIVER).

Example for a CPO:

• Locations SHALL be sent to the endpoint advertised by MOBI.Hub for the Locations RECEIVER interface.
• CDRs SHALL be retrieved from the endpoint advertised by MOBI.Hub for the CDRs SENDER interface.

The hostname and base path used by participants are implementation specific. MOBI.Hub discovers all module endpoints dynamically through the Versions and Version Details modules and constructs the final URLs according to the rules defined by each OCPI module.

Authorization header

The Authorization header may be provided either in plain text, as defined by the OCPI specification, or encoded in Base64. The MOBI.Hub Interoperability Hub supports both formats for backward compatibility purposes, although participants are encouraged to follow the format defined by the OCPI specification.