OCPP & OCPI Integration Platform
Bridging charging hardware, central software, and roaming driver networks through standardized Open Charge Point Protocol (OCPP) and Open Charge Point Interface (OCPI) integrations. Ensure total hardware interoperability and nationwide eMSP roaming.
Standardized Open Protocols
Eliminate vendor lock-in. Connect any verified OCPP charging hardware and synchronize roaming datasets with leading mobility service providers.
Understanding OCPP vs. OCPI
Explore how hardware-to-cloud communication (OCPP) integrates with cloud-to-cloud roaming networks (OCPI) to power the modern electric vehicle charging ecosystem.
- AC Wallbox & DC Fast Dispensers
- Embedded Linux / RTOS Controller
- Hardware metering & contactors
- RFID / Dynamic QR interface
Heartbeat • BootNotification • MeterValues • RemoteStart
- Session control & authorization
- Dynamic load balancing (DLB)
- Tariff engine & billing logic
- Fault triage & telemetry storage
Locations • Tariffs • Sessions • CDRs • Tokens
- PlugOne Unified EV App
- Partner eMSP & OEM car apps
- Multi-network discovery & map
- Inter-network financial settlement
Protocol Matrix: OCPP vs. OCPI
Understanding the foundational architectural distinction between equipment communication (OCPP) and network roaming interoperability (OCPI).
| Attribute | OCPP (Open Charge Point Protocol) | OCPI (Open Charge Point Interface) |
|---|---|---|
| Primary Role | Equipment Control Governs direct communication between physical EV charging stations and the central CSMS software. | Network Interoperability Governs communication between distinct CPO networks and eMSP (e-Mobility Service Provider) platforms. |
| Supported Standards | OCPP 1.6J (JSON over WebSockets) & OCPP 2.0.1 (Device model, ISO 15118 plug-and-charge ready). | OCPI 2.2 & OCPI 2.2.1 (Standard modules: Locations, Tariffs, Sessions, CDRs, Commands, Tokens). |
| Communication Model | Persistent bidirectional WebSockets (WSS) with low-latency binary/JSON framing. | Stateless RESTful HTTPS APIs with JSON payloads and asynchronous webhook callbacks. |
| Key Functions |
|
|
| Typical Users | Charger Manufacturers, Hardware Installers, CPO Engineering Teams. | Platform Operators, EV Roaming Aggregators, Automotive OEMs, eMSPs. |
Detailed Protocol Capabilities
An in-depth look at the functions, message structures, and capabilities delivered by each integration layer.
OCPP: Hardware to CSMS Communication
The industry-standard protocol ensuring communication between physical charging stations and the central charging station management software.
- Station Telemetry: Real-time voltage, current, power factor, and meter values.
- Remote Control: RemoteStartTransaction, RemoteStopTransaction, and connector unlocking.
- Smart Charging Profiles: Dynamic load balancing limits and scheduled power capping.
- Diagnostics & Maintenance: Diagnostic log file uploads and over-the-air firmware upgrades.
- Supported Versions: OCPP 1.6 JSON (implemented) and OCPP 2.0.1 (architectural support).
OCPI: Inter-Network Roaming & eMSP
Facilitates roaming between disparate charging point operators (CPOs) and e-Mobility Service Providers (eMSPs), allowing unified driver access.
- Location & EVSE Data: Live synchronization of station coordinates, connector types, and availability.
- Tariff Broadcasting: Structured exchange of charging fees, idle tariffs, and tax components.
- Session & CDR Exchange: Automated generation and verification of Charge Detail Records.
- Cross-Network Authorization: Real-time token validation allowing app users to charge on partner networks.
- Supported Versions: OCPI 2.2 and OCPI 2.2.1.
Partner & Hardware Onboarding Process
Our structured 4-step onboarding pipeline accelerates technical integration and ensures dependable field performance.
Technical Scoping & Protocol Alignment
Reviewing your hardware EVSE model, OCPP version compatibility (1.6J or 2.0.1), or OCPI roaming endpoints (v2.2 / v2.2.1).
Sandbox Credential Provisioning
Generating secure WebSocket URL endpoints (WSS) and API token pairs within our staging environment for integration testing.
Conformance & Message Interoperability Testing
Testing message transactions: BootNotification, Heartbeat, StatusNotification, RemoteStart/Stop, MeterValues, and CDR generation.
Production Cutover & Roaming Go-Live
Transitioning to high-availability production clusters, enabling live roaming discovery via PlugOne, and activating 24/7 monitoring.
Request API Documentation & Sandbox Access
Are you an EVSE hardware manufacturer, CPO, or eMSP software platform? Request technical integration documentation, WebSocket schemas, and sandbox credentials.
OCPP & OCPI Technical FAQs
OCPP (Open Charge Point Protocol) connects physical EV chargers to a central Charge Station Management System (CSMS) to control hardware, read power meters, and monitor errors. OCPI (Open Charge Point Interface) connects one central software system to another (e.g. CPO network to eMSP driver apps), allowing drivers of one network to discover, charge, and pay at stations on another network without multiple accounts.