OCPI 2.3.0

Test OCPI 2.3.0

Test your endpoint against a controllable counterparty. Inspect the requests, responses and rules behind each graded result.

Run a conformance suiteInspect an example report

Sandbox-tested against our own endpoints.CPO and eMSP discovery. Bookings 2.3.0-booking-1.1.Try the sandbox free. Your endpoint needs a paid plan.

Owned loopback reference-hub capture · OCPI 2.2.1

Request excerpt

GET /ocpi/2.2.1/credentials
Authorization: [redacted]

Response excerpt · HTTP 200 · 4 ms

{
  "status_code": 1000,
  "timestamp": "2026-10-26T11:04:35Z"
}

This 2.2.1 excerpt shows the report format.

Open the saved report

What we test on OCPI 2.3.0

Every core OCPI 2.3.0 module, Payments included, with the AFIR parking model, the new tax model and open enums, plus Bookings from the separately published document 2.3.0-booking-1.1.

Sandbox-tested. These suites have run against ChargerDojo's own sandbox. This is not independent partner validation or certification.

Sender and receiver name OCPI interfaces. Your run also selects its CPO or eMSP business role and the modules your endpoint implements.

Advertised interfaces with conformance suites
ModuleInterface rolesDefined inMaturity
CredentialsSenderCore OCPI 2.3.0Sandbox-tested
CommandsSender and receiverCore OCPI 2.3.0Sandbox-tested
BookingsSender and receiver2.3.0-booking-1.1Sandbox-tested
PaymentsSender and receiverCore OCPI 2.3.0Sandbox-tested
Hub Client InfoSender and receiverCore OCPI 2.3.0Sandbox-tested
Charging ProfilesReceiver onlyCore OCPI 2.3.0Sandbox-tested
LocationsSender and receiverCore OCPI 2.3.0Sandbox-tested
TariffsSender and receiverCore OCPI 2.3.0Sandbox-tested
SessionsSender and receiverCore OCPI 2.3.0Sandbox-tested
CDRsSender and receiverCore OCPI 2.3.0Sandbox-tested
TokensSender and receiverCore OCPI 2.3.0Sandbox-tested

Known limitations

  • The sandbox reserves UNKNOWN-LOCATION and UNKNOWN-EVSE Commands IDs, which always return REJECTED, and UNKNOWN-SESSION, which always returns UNKNOWN_SESSION.

  • Registration discovers endpoints for CPO and eMSP peers; other roles can register, but registration does not discover their endpoints.

A version's available suites are not the same as checks graded in one run. Read each report's tested and not-tested scope.

Run an OCPI conformance suiteCompare OCPI versionsExplore charging journeys

See the evidence first

The public example is an owned loopback reference-hub capture. The excerpt shows a missing Session error returned through the hub.

The current example was captured with OCPI 2.2.1. It is a report-format example, not evidence of a 2.3.0 run. A pass covers the checks graded in that run; it does not certify your endpoint or replace partner approval.

Captured request and response · OCPI 2.2.1

Request

PATCH /ocpi/2.2.1/sessions/NL/CDA/JRN-RELAY-MISS-177cb655
{
  "kwh": 1,
  "last_updated": "2026-10-26T11:05:35.132Z"
}

Response · HTTP 200 · 114 ms

{
  "status_code": 2001,
  "status_message": "Session with ID JRN-RELAY-MISS-177cb655 not found",
  "timestamp": "2026-10-26T11:04:37Z"
}

The hub forwarded the eMSP test party's error back to the CPO test party. The saved report holds the full exchange and graded rule.

Open the saved report