Skip to content
Start testing
Protocols

OCPP and OCPI protocol testing

OCPP runs between a charger and its CSMS. OCPI is the roaming API between CPOs and eMSPs.
Start your testingBook technical demo
Protocol map: a charger talks OCPP 1.6, 2.0.1, or 2.1 to the CSMS, which as a CPO talks OCPI 2.1.1, 2.2.1, or 2.3.0 to an eMSP, directly or through an optional hub. One charging session crosses both: StartTransaction reaches the CSMS, then PUT /sessions reaches the eMSP with status: ACTIVE.
Protocol map: a charger talks OCPP 1.6, 2.0.1, or 2.1 to the CSMS, which as a CPO talks OCPI 2.1.1, 2.2.1, or 2.3.0 to an eMSP, directly or through an optional hub. One charging session crosses both: StartTransaction reaches the CSMS, then PUT /sessions reaches the eMSP with status: ACTIVE.

OCPP charger to CSMS

Best OCPP emulators compared

OCPP 1.6

Validate charger onboarding, authorization, transactions, status notifications, meter values, and remote commands for widely deployed OCPP 1.6 fleets.

StartTransaction.req {connectorId: 1, idTag, meterStart}

Explore OCPP 1.6 testing

OCPP 2.0.1

Test modern OCPP 2.0.1 workflows including smart charging, device management, security profiles, ISO 15118-adjacent flows, and TransactionEvent handling.

TransactionEventRequest {eventType: Started, seqNo: 0}

Explore OCPP 2.0.1 testing

OCPP 2.1

Cover OCPP 2.1 in the workspace: V2G/V2X setpoints, DER control, local tariffs, BatterySwap, and AFRR message sequences.

SetChargingProfileRequest {operationMode: CentralSetpoint}

Explore OCPP 2.1 testing

OCPI CPO to eMSP roaming

OCPI 2.1.1

Cover core roaming interoperability for credentials, locations, sessions, CDRs, tariffs, tokens, and commands between CPOs and eMSPs.

POST /ocpi/2.1.1/credentials

Explore OCPI 2.1.1 testing

OCPI 2.2.1

Validate newer roaming and hub workflows including ChargingProfiles, HubClientInfo, richer tariff structures, and broader hub interoperability requirements.

PUT /hubclientinfo/{country_code}/{party_id}

Explore OCPI 2.2.1 testing

OCPI 2.3.0

Cover OCPI 2.3.0 in the workspace: hub_party_id credentials, the PTP role, HubClientInfo routing, and the OCPPLab Bookings extension.

POST /ocpi/cpo/2.3.0/bookingsOCPPLab extension

Explore OCPI 2.3.0 testing

Protocols & standards

The core EV charging and energy protocols OCPPLab speaks, from charger-to-backend communication through roaming between networks.

OCPP

Charger to CSMS, JSON over WebSocket. Virtual chargers run 1.6, 2.0.1 and 2.1 against your CSMS.

OCPI

CPO to eMSP roaming over REST: the credentials handshake, then Locations, Sessions, CDRs, Tariffs, Tokens and Commands in 2.1.1, 2.2.1 and 2.3.0.

Adjacent standards (not supported)

EEBUS and Modbus often sit next to chargers in energy and site setups. OCPPLab does not implement them.

EEBUS

Wallbox to home energy manager (SHIP transport, SPINE data model). Sits beside the OCPP link; not simulated.

Modbus

Register reads from meters and inverters on the site controller. Sits below the charger's OCPP link; not simulated.

Need coverage across multiple protocol versions?

OCPPLab lets you test mixed fleets and roaming stacks from one cloud platform.

See platform featuresBook technical demo