Skip to content
Start testing
Integrations

OCPP and OCPI integration testing by charger vendor and roaming hub

Use these pages to validate charger-profile behavior and partner-workflow readiness before you connect production systems.
Start your testingBook technical demo
The workspace's OCPP 1.6 message log with the ABB charger's BootNotification open: chargePointVendor "ABB", chargePointModel "Terra AC". Beside it, the OCPI logs hold each roaming hub's opening credentials call: GIREVE POST /ocpi/2.2.1/credentials, Hubject POST /ocpi/2.2.1/credentials.
The workspace's OCPP 1.6 message log with the ABB charger's BootNotification open: chargePointVendor "ABB", chargePointModel "Terra AC". Beside it, the OCPI logs hold each roaming hub's opening credentials call: GIREVE POST /ocpi/2.2.1/credentials, Hubject POST /ocpi/2.2.1/credentials.

OCPP charger vendors

ABB OCPP testing

Terra AC wallboxes on OCPP 1.6J next to Terra DC and Terra 360 units that add OCPP 2.0.1 on newer firmware, so one CSMS has to handle both versions.

chargePointVendor: "ABB" · chargePointModel: "Terra AC"

View ABB scope

Alfen OCPP testing

Eve Single and Eve Double Pro-line on OCPP 1.6J, where SetChargingProfile limits from your CSMS meet Alfen Active Load Balancing.

chargePointVendor: "Alfen BV" · chargePointModel: "Eve Single Pro-line"

View Alfen scope

EVBox OCPP testing

Elvi and Liviqo AC units next to multi-connector Troniq DC units, so connector count and StatusNotification timing differ within one vendor's lineup.

chargePointVendor: "EVBox" · chargePointModel: "Elvi"

View EVBox scope

Wallbox OCPP testing

Pulsar Plus, Commander 2 and Supernova on OCPP 1.6J: a Pulsar Plus session from Preparing through MeterValues to a backend RemoteStopTransaction.

chargePointVendor: "Wallbox" · chargePointModel: "Pulsar Plus"

View Wallbox scope

OCPI roaming hubs

GIREVE OCPI testing

Validate OCPI 2.1.1 and 2.2.1 integrations for GIREVE onboarding: credentials, locations, sessions, CDRs, tariffs, and the GIREVE workbook cases.

POST /ocpi/2.2.1/credentials

View GIREVE scope

Hubject roaming readiness

Prove the OCPI side of your roaming backend before Hubject onboarding. OCPPLab connects as a CPO or eMSP party over OCPI; it does not speak OICP.

POST /ocpi/2.2.1/credentials · OCPPLab as eMSP

OICP stays with Hubject QA

View Hubject scope

Need another vendor or roaming partner page?

OCPPLab runs custom charger-vendor and roaming-hub checks.

Book technical demoSee protocol coverage