OCPI 2.2.1 Testing
Validate newer OCPI 2.2.1 roaming and hub workflows including ChargingProfiles, HubClientInfo, richer tariff behavior, and broader hub interoperability.
What is OCPI 2.2.1 testing?
OCPI 2.2.1 testing extends core roaming validation with newer workflows often required by hubs and advanced roaming setups. Teams typically need to validate not only the classic modules, but also newer structures and modules such as ChargingProfiles and HubClientInfo, along with richer tariff and interoperability behavior.
Supported modules and flows
- All core roaming modules from earlier OCPI versions plus newer 2.2.1 coverage where required.
- ChargingProfiles workflows for smart charging across the roaming chain.
- HubClientInfo and hub-oriented participant synchronization.
- Extended tariff structures, newer fields, and broader interoperability behavior expected by hubs.
Best for
- Hub-connected roaming stacks that need more than the core OCPI 2.1.1 baseline.
- Teams validating smart-charging-related roaming workflows and newer tariff behavior.
- Implementations migrating from OCPI 2.1.1 to OCPI 2.2.1 and needing side-by-side validation.
Example OCPI 2.2.1 hub-oriented flow
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
eMSP or Hub -> CPO: POST /chargingprofiles
CPO -> eMSP or Hub: 200 OK
CPO -> eMSP: PUT /sessions/{country_code}/{party_id}/{session_id}
eMSP -> CPO: 200 OKSupported hub and smart-charging profiles
Teams 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. |
What to test
- Core roaming module coverage across credentials, locations, sessions, CDRs, tariffs, tokens, and commands.
- ChargingProfiles behavior across the roaming chain.
- HubClientInfo and hub-oriented participant workflows.
- Compatibility with newer roaming and interoperability requirements.
Common scenarios
Hub onboarding
Validate your OCPI 2.2.1 implementation before connecting to hub infrastructure that expects newer module and field coverage.
Smart charging over roaming
Exercise ChargingProfiles-related workflows where charging control needs to pass through the roaming chain.
Migration from 2.1.1
Check field, module, and behavior differences before upgrading an existing roaming stack to OCPI 2.2.1.
Related resources
Test OCPI 2.2.1 workflows before hub integration goes live
Validate newer roaming modules and hub behavior in a controlled environment instead of debugging against live partners.