Version discovery agrees on an OCPI version

Technical · 3 min

OCPI 2.1.1, 2.2.1 and 2.3.0

Showing OCPI 2.2.1. Physical and billing-system events are authored examples.

Part of the lesson OCPI charging session lifecycle

Step 1 of 4 · Roaming connection setup
versionseMSPsendsCPOreceives
versionsCPOreceiveseMSPsends
Legend

The line follows the selected step. Actor dots identify the parties; they show no conformance verdict.

Step 1 of 4 · Paused

Selected step

All 2 actors

CPO · eMSP

Selected exchange

The CPO created CREDENTIALS_TOKEN_A for the eMSP, which is the Sender in this registration. With token A in the Authorization header, the eMSP reads the CPO's versions list, picks 2.2.1, and reads that version's details for the CPO's module endpoints.

eMSP → CPO · versions

Source
"This is the required base module of OCPI. This module is the starting point for any OCPI connection. Via this module, clients can learn which versions of OCPI a server supports, and which modules it supports for each of the versions."OCPI 2.2.1 Version information endpoint chapter · #versions_module
Why this matters

Version discovery lists the OCPI versions and module endpoints available from the other platform.

Explore the versions module

Sandbox run · OCPI 2.2.1

Run this exchange in the sandbox

Test this flow

Test this flow runs against an eMSP endpoint you have registered.