OCPI roaming hub testing

Test how your roaming hub routes OCPI, release after release.

ChargerDojo joins your hub as CPO and eMSP counterparties, sends a Session through it and grades every forward against the OCPI routing rules.

OCPI 2.2, 2.2.1 and 2.3.0. Sample report free, no login. Identity checks on Integrate, $149 a month; relay and schedules on Automate, $499 a month.

ChargerDojoCPO and eMSP counterparties
Your hubUnder test
  1. CPO counterparty to hub.
    PUT/sessions Reply: 201 · 1000
  2. Hub to eMSP counterparty.
    PUT/sessions Reply: 201 · 1000
  3. CPO counterparty to hub.
    PATCH/sessions Reply: 200 · 2001
  4. Hub to eMSP counterparty.
    PATCH/sessions Reply: 200 · 2001
  5. CPO counterparty to hub.
    PUT/sessions Reply: 200 · 4001

Before these, both counterparties read your Credentials and your HubClientInfo list.

All eleven calls
  1. CPO counterparty to hub.
    GET/credentials Reply: 200 · 1000
  2. eMSP counterparty to hub.
    GET/credentials Reply: 200 · 1000
  3. CPO counterparty to hub.
    GET/hubclientinfo Reply: 200 · 1000
  4. eMSP counterparty to hub.
    GET/hubclientinfo Reply: 200 · 1000
  5. CPO counterparty to hub.
    PUT/sessions Reply: 201 · 1000
  6. Hub to eMSP counterparty.
    PUT/sessions Reply: 201 · 1000
  7. CPO counterparty to hub.
    PATCH/sessions Reply: 200 · 2001
  8. Hub to eMSP counterparty.
    PATCH/sessions Reply: 200 · 2001
  9. eMSP counterparty to hub.
    POST/commands Reply: 200 · 1000
  10. Hub to CPO counterparty.
    POST/commands Reply: 200 · 1000
  11. CPO counterparty to hub.
    PUT/sessions Reply: 200 · 4001

Both sides of the hub

Two counterparties, one Session, your hub in the middle.

You create CPO and eMSP counterparties in your test environment and issue a registration token for each. We register both with your hub, then watch what reaches each side.

The hub guide walks through each step.

OCPI versions

Moving to OCPI 2.3.0 changes how your hub names itself.

The checks follow the version you register. OCPI 2.1.1 has no routing headers, so hub testing runs on 2.2, 2.2.1 and 2.3.0.

What we readOCPI 2.2 and 2.2.1OCPI 2.3.0
How the hub names itselfThe role HUB in its Credentialshub_party_id in its Credentials
Who it reportsEach counterparty in its HubClientInfo listThe parties reachable through it, in its Credentials roles

The report

Every forward, graded against its clause.

A hub must forward each request with a new X-Request-ID, the same X-Correlation-ID and last_updated, and the receiver's status unchanged. Your report shows both requests side by side.

Routing
U01The forward names the receiving counterparty in TO and the sender in FROM.
U02The answer comes back addressed to the sending counterparty.
U03The forward carries a new X-Request-ID.
U04The X-Correlation-ID reaches the receiver unchanged.
U05The hub leaves last_updated unchanged.
Errors
U06The receiver's status reaches the CPO counterparty unchanged.
Identity
U07On 2.2 and 2.2.1 the hub reports itself only as role HUB.
U08On 2.2 and 2.2.1 it reports connected parties through HubClientInfo; a counterparty missing from that list is not tested.
U09On 2.3.0 it names itself in hub_party_id.
U10No Credentials, Versions or HubClientInfo request or response from the hub carries a routing header.
U15Each ClientInfo the hub pushed a counterparty since it registered carries every required field.
Broadcast
U23Each broadcast forward names its receiving party in TO and the hub in FROM.
U24The hub answers the broadcast addressed to the CPO counterparty.
U26The forward's URL names the pair inside the Location.
U31Each copy of the broadcast carries its own X-Request-ID.
U33Each copy of the broadcast carries an X-Correlation-ID.
GET All
U18The answer names the eMSP counterparty in TO and the hub in FROM.
U19A successful answer carries a list of whole Locations.
U20A successful answer carries X-Total-Count and X-Limit.
Recorded, not graded
U11, U12, U13, U14, U16, U17, U21, U22, U25, U30, U32: recorded in the report, explained in the hub guide.
Sent by the CPO counterparty
PUT /ocpi/2.2.1/sessions/NL/CDA/JRN-RELAY-182226b0
X-Request-ID: 810afcb9-c2a9-49ab-984c-97195d46ebdd
X-Correlation-ID: 8ca29239-606d-463e-8121-661fe98d7030
OCPI-from-party-id: CDA
OCPI-to-party-id: CDB
"last_updated": "2026-11-15T04:31:17.271Z"
Forwarded to the eMSP counterparty

new        X-Request-ID: d47a6fa7-b1a2-40b5-9855-be41e38bd8de
unchanged  X-Correlation-ID: 8ca29239-606d-463e-8121-661fe98d7030
unchanged  OCPI-from-party-id: CDA
unchanged  OCPI-to-party-id: CDB
unchanged  "last_updated": "2026-11-15T04:31:17.271Z"

Checks that catch real faults

Each fault below fails the check that names it.

Our reference hub is a test hub we run that follows every routing rule. For each fault below we run a copy with exactly that rule broken, and its check must fail. The unbroken hub must pass.

  • Copies the incoming X-Request-ID onto the forwardU03
  • Replaces the X-Correlation-ID on the forwardU04
  • Rewrites last_updated on the forwarded SessionU05
  • Swallows the receiver's error and answers successU06
  • On 2.2 and 2.2.1 lists its connected parties as its own rolesU07

After the first run

Keep it running as your hub changes.

On a schedule

Relay runs daily or weekly, and Runs shows what changed since the last run. On Automate, $499 a month. Send the report link to a partner waiting to connect.

Staging and production

Automate, $499 a month, holds 20 endpoints. Each hub environment uses two, one per counterparty, so up to 10 environments.

Partner onboarding

Onboard your hub's partners in ChargerDojo.

Set up with us. We create your partner programme with you, then you invite the CPOs and eMSPs joining your hub, give them your test list and see the latest verdict each partner chooses to share.

Write to sales@chargerdojo.com to start yours.

Before you register.

Which of our environments do you connect to?

The one you register.

More detail

Each counterparty is a registration with your hub, at the versions URL and token you give it, so a staging hub works the same as production.

Can our partners test before they reach our onboarding?

Yes. Each CPO or eMSP joining your hub can test its own endpoint against ChargerDojo before your test phase starts.

More detail

Each can also open your hub's report from the share link you send.

Do you support client certificates or an IP allow-list?

Not today.

More detail

Your test environment must accept our counterparties with token authentication alone. If your hub needs a client certificate or a fixed source IP, talk to us.

sales@chargerdojo.com

Is a report a certification?

No. ChargerDojo is an independent testing tool.

More detail

A report records the checks that ran against your hub.

We are joining a hub as a CPO or eMSP. Is this for us?

This page is about testing the hub itself.

More detail

To test your own endpoint before a hub connects you, prepare your next hub integration.

Prepare your next hub integration

Which OCPI versions does it test?

OCPI 2.2, 2.2.1 and 2.3.0, the versions that define message routing.

More detail

OCPI 2.1.1 has no routing headers.

Which plan do we need?

Identity needs one registration on Integrate, $149 a month.

More detail

Relay and schedules need a CPO and an eMSP registration on Automate, $499 a month. Need more than 20 endpoints? Custom, our quoted plan, covers identity and relay across all your hubs. It issues no certificate.

sales@chargerdojo.com

Talk to us about your hub, or register it today.

The sample hub report is free, no login. Your hub's report has the same shape.