Example OCPI report
See what your partner can open. A real run against our owned local reference-hub fixture, with the saved exchanges and rules behind each result.
Example · Captured · OCPI 2.2.1
Roaming-hub relay: identity, Session forwarding, error propagation and Configuration observation. Credentials and identifiers are sanitized; exchange hosts are replaced with non-resolving example addresses. This scoped example does not certify an endpoint.
Report: ChargerDojo reference-hub fixture
OCPI 2.2.1
The journey has partial coverage
2 checks were not graded. The ledger shows the missing evidence.
plan 43d7e932d1258e44 · roaming-hub-relay @ charging-journeys-depth-v7
Journey evidence
1
config-window-cpo
Watch for the partner request
2
config-window-emsp
Watch for the partner request
3
hub-credentials-cpo
GET · HTTP 200 · 4ms
4
hub-credentials-emsp
GET · HTTP 200 · 5ms
5
hub-clients-cpo
GET · HTTP 200 · 6ms
6
hub-clients-emsp
GET · HTTP 200 · 5ms
7
relay-window
Watch for the partner request
8
relay-put
PUT · HTTP 201 · 55ms
9
relay-arrival
Await the partner request
10
refusal-window
Watch for the partner request
11
refusal-patch
PATCH · HTTP 200 · 114ms
12
refusal-arrival
Await the partner request
13
unknown-receiver
PUT · HTTP 200 · 5ms
14
config-check-cpo
Await the partner request
15
config-check-emsp
Await the partner request