OCPI 2.2.1 testing extends core roaming validation with newer workflows often required by hubs and advanced roaming setups. Teams validate the classic modules plus newer ones such as ChargingProfiles and HubClientInfo. They also check richer tariff structures and broader interoperability behavior.
OCPI 2.2.1 still uses the core credentials and version-discovery flow, but teams often also need to validate newer hub and smart-charging modules introduced in the newer version.
Party A -> Party B: GET /versions
Party A -> Party B: GET /versions/2.2.1
Party A -> Party B: POST /credentials
Party B -> Party A: 200 OK with token + endpoints
Hub -> Party: PUT /hubclientinfo/{country_code}/{party_id}
Party -> Hub: 200 OK
SCSP or eMSP -> CPO: PUT /chargingprofiles/{session_id}
CPO -> SCSP or eMSP: 200 OK (ChargingProfileResponse: ACCEPTED)
CPO -> SCSP or eMSP: POST {response_url} (async ChargingProfileResult)
CPO -> eMSP: PUT /sessions/{country_code}/{party_id}/{session_id}
eMSP -> CPO: 200 OKTeams usually reach for OCPI 2.2.1 when the roaming stack needs more than baseline partner interoperability and has to cover newer hub and charging-control scenarios.
| Profile | Coverage | Typical validation |
|---|---|---|
| Hub-oriented roaming | HubClientInfo and broader participant synchronization | Prepare for hub onboarding and multi-party coordination paths. |
| ChargingProfiles over roaming | OCPI 2.2.1 charging-control flows | Validate schedule-aware and smart-charging-related partner behavior. |
| Advanced tariff and field coverage | Newer metadata and richer interoperability requirements | Exercise upgraded payloads before production partner rollout. |
Validate your OCPI 2.2.1 implementation before connecting to hub infrastructure that expects newer module and field coverage.
Exercise ChargingProfiles-related workflows where charging control needs to pass through the roaming chain.
Check field, module, and behavior differences before upgrading an existing roaming stack to OCPI 2.2.1.
Validate newer roaming modules and hub behavior in a controlled environment instead of debugging against live partners.