OCPI Message Routing
OCPI 2.2+ capability that enables hub-friendly routing patterns so platforms can exchange data through hubs without managing many bilateral connections.
Technical Details
OCPI originally assumed peer-to-peer connections between CPO and eMSP, but hub-based ecosystems need routing. With message routing, hubs can relay requests based on headers and content. Common patterns include Broadcast Push (fan-out of shared data like locations/tokens) and Open Routing Requests (routing when the destination is unknown and OCPI-to headers can be omitted toward the hub).
Fleet Applications
Speeds up roaming and interoperability onboarding by reducing the number of direct integrations and letting fleets depend on hubs/platforms for data distribution and routing across many partners.
Related Terms
OCPI 2.2.1 (Open Charge Point Interface)
Roaming interoperability protocol for exchanging charging network data (locations, tariffs, tokens, sessions, commands, and charge detail records) between CPOs, eMSPs, hubs, and multi-role platforms.
OCPI Credentials
The OCPI mechanism for establishing and maintaining trust between platforms (tokens, endpoint discovery, and version negotiation).