Integrate a CPO or eMSP with the Hubject OICP eRoaming hub for cross-network EV charging authorization

domain: hubject.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Determine whether the integration is on the CPO side or EMP (eMobility Provider) side, since OICP publishes distinct CPO and EMP service specifications (OICP CPO 2.3 API / OICP EMP 2.3 API)
  2. Implement EVSE data and EVSE status push/pull operations so charge point availability stays in sync with the Hubject hub
  3. Implement authorization operations so a roaming driver's token can be validated in real time at a foreign charge point
  4. Exchange charge detail record/billing data per the CPO/EMP service definitions for post-session settlement
  5. Use OICP 2.3, the current version, for new implementations rather than building against older 2.1/2.2 specs

Known gotchas

Related routes

Perform real-time remote charging authorization with Hubject OICP eRoamingAuthorizeStart / eRoamingAuthorizeStop
hubject.com · 5 steps · unrated
Implement the OCPI 2.2.1 ChargingProfiles module to exchange smart-charging commands between an eMSP and CPO
evroaming.org · 5 steps · unrated
Implement the OCPI Locations module to publish or consume EV charging site data between a CPO and eMSP
github.com/ocpi · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans