OCPI & OICP Interoperability Services
Build robust EV roaming capabilities with advanced OCPI/OICP integrations. Codibly offers accelerator-driven deployment, consulting, and custom interoperability services for CPOs, eMSPs, and technology providers seeking standardized data exchange and cross-network charging support. Our technical expertise covers in-depth protocol features, from HTTP transport and JSON data structures to custom authentication flows and modular architecture.
OCPI KEY INFORMATION
What Is OCPI?
OCPI (Open Charge Point Interface) is an open protocol for EV roaming that enables communication between Charge Point Operators (CPOs) and e-Mobility Service Providers (eMSPs). It handles location sharing, tariff exchange, session authorization, real-time status updates, and billing via Charge Detail Records (CDRs). The current version is OCPI 2.2.1, with OCPI 3.0 in development.
Unlike OCPP, which handles communication between a charger and its backend (internal protocol), OCPI handles communication between different backend systems (external/roaming protocol). Think of OCPP as the “internal” language and OCPI as the “external” language for cross-network interoperability.
Governance
Maintained by the EVRoaming Foundation. eViolin and ElaadNL initiated development. OCPI 2.2.1 is current; 2.1.1 still widely used. Open-source and freely accessible.
Transport & Format
HTTP-based with JSON data. Custom header authorization tokens. Supports push/pull data exchange with pagination and filtering on GET requests.
Core Modules
Credentials, Versions, Tokens for authentication. Locations, Sessions, CDRs, Tariffs for operations. Optional: Commands, ChargingProfiles (2.2+) for smart charging.
European & Global Adoption
The most prominent EV roaming protocol across Europe, with growing adoption in North America and Asia-Pacific.
OICP OVERVIEW
What Is the Difference Between OCPI and OICP?
OCPI is a peer-to-peer protocol — CPOs and eMSPs connect directly to each other. OICP (Open InterCharge Protocol) is a hub-based protocol where all parties connect through a central roaming hub (primarily Hubject). OCPI uses HTTP/JSON, while OICP uses SOAP/XML.
OCPI offers more flexibility and lower latency for direct connections, while OICP simplifies multi-party connectivity through its hub model. Many large networks support both protocols. Codibly provides integration services for both.
Intercharge-Focused
• Ensures smooth data exchange among eMSPs and CPOs.
• Hub-based model for multi-party communication.
• Emphasis on session handling and tariff definitions.
Robust Transaction Models
• Standardized messages for charge detail records.
• Supports various authentication and authorization setups.
• Highly configurable for real-world billing scenarios.
Technical Architecture
• SOAP/HTTPS-based communication.
• XML-based data structures, configured for real-time event exchanges.
• Comprehensive protocol specs for data routing and error handling.
Codibly’s OICP Integration Services
• Implementation consulting and architectural design.
• OICP-based backend integration for eMSPs and CPOs.
• Post-launch support covering updates, bug fixes, and performance tuning.
CODIBLY’S OCPI ACCELERATOR
How Does Codibly’s OCPI Accelerator Work?
Codibly’s OCPI Accelerator reduces integration time by providing a pre-built library that handles OCPI 2.1.1 and 2.2.1 data models, credential management, and module implementations. It integrates directly with your existing CPO backend with minimal code overhead:
Seamless Integration
• Library for easy integration with your CPO backend
• Implements OCPI 2.1.1 & 2.2.1 data models
• Minimal code overhead in your existing environment
Simple Registration
• Straightforward eMSP registration flows
• Clear interface definitions for credential modules
• Easy expansions for multi-tenant usage
Database Flexibility
• Multiple DB options supported (SQL/NoSQL)
• Customizable ORM or direct queries
• High-quality test coverage for data consistency
Modularity & Extensibility
• Well-defined model-to-model mappings
• Clear separation of transport, logic, and domain
• Easy to extend for custom features or third-party tie-ins
OCPI CONSULTING & STRATEGY
How Long Does OCPI/OICP Integration Take?
A typical OCPI integration using Codibly’s accelerator takes 4–8 weeks from kick-off to production. OICP integrations via Hubject are similar in timeline. Our technical advisory process ensures smooth execution:
In-Depth Analysis
• Assessment of existing EV backend architecture
• Evaluation of data flows vs. OCPI/OICP specs
• Detailed gap analysis for performance & reliability
Risk Mitigation
• Identify potential conflicts in versioning or transport
• Suggest fallback strategies for legacy networks
• Propose redundancy and security best practices
Outcome-Oriented
• Practical integration roadmap aligned with business goals
• Enhanced EV charging operational capabilities
• Clear user acceptance testing guidelines
Request a Technical Consultation
Ready to formalize your OCPI/OICP strategies or expedite your EV roaming integration? Consult Codibly’s domain experts for a deep dive into data models, transport flows, and backend architecture.
What our clients say
“Codibly was more than just a software development company; they were a capable partner who understands the EV industry and helped us push our vision forward.”
“Working closely with Codibly has been instrumental in the successful development of the test tool for OpenADR 3.0. Their expertise and commitment to quality have ensured reliability and effectiveness for the energy industry, and we look forward to continuing our collaborative efforts to advance OpenADR technology.”
CASE STUDIES
See the success stories of our clients
Meet our Expert
As the eMobility Practice Lead at Codibly, I am responsible for driving the strategic development and growth of our electromobility division. With over 15 years of experience in the IT sector, I specialize in building strong client relationships and aligning technology solutions with business objectives. Having spent the last decade focused on the automotive and electromobility industries, I bring a wealth of expertise in delivering tailored solutions for both the public and private sectors. Prior to Codibly, I led the IT teams at Volkswagen Group Poland, where I successfully managed a range of large-scale projects and IT portfolios. Throughout my career, I have consistently focused on delivering both off-the-shelf and custom solutions that address complex business challenges.
Frequently Asked Questions
OCPI (Open Charge Point Interface) is an open protocol for EV roaming that enables communication between CPOs and eMSPs. It handles location sharing, tariff exchange, session authorization, real-time status updates, and billing (CDRs). The current version is OCPI 2.2.1, with OCPI 3.0 in development.
OCPP handles communication between a charging station and its management system (CSMS). OCPI handles communication between different parties in the EV ecosystem — CPOs and eMSPs. Think of OCPP as the “internal” protocol (charger to backend) and OCPI as the “external” protocol (backend to backend) for roaming.
EV roaming allows drivers to charge at stations operated by different CPOs using a single eMSP account. When a driver initiates a session, the eMSP sends an authorization request via OCPI or OICP to the CPO. After charging, a CDR (Charge Detail Record) is exchanged for billing. Roaming hubs like Hubject and Gireve aggregate multiple CPO and eMSP connections.
Most mature Charge Point Operators (CPOs) need both. OICP connects you to the Hubject intercharge network, instantly giving you access to thousands of eMSPs via a single contract. OCPI is best for direct, bilateral Peer-to-Peer (P2P) connections with key strategic partners where you want to avoid roaming fees or implement custom tariff structures. Codibly’s architecture supports a hybrid model to maximize coverage while minimizing costs.
Our OCPI Accelerator is a pre-built, microservices-based module that handles standard handshakes, token exchange, and CDR (Charge Detail Record) pushing out of the box. Instead of building the protocol layer from scratch (typically 4–6 months), your team only needs to map your internal API to our connector, reducing deployment time to 4–8 weeks. It supports both OCPI 2.1.1 and 2.2.1.
Yes. We build custom Translation Layers (Adapters) that allow an OCPI-native backend to communicate seamlessly with OICP hubs like Hubject, and vice versa. This middleware handles the complex mapping of EVSE IDs, status codes, and error handling between the two protocols, ensuring your system remains the “Source of Truth” without needing a complete re-architecture.
Our implementation supports the transfer of signed meter values (transparency software data) required for German Eichrecht compliance. We ensure that the digitally signed data tuples from the hardware are passed intact through the OCPI/OICP layers to the eMSP for validation, ensuring that your billing records are legally defensible and audit-proof.
Yes. We support the Tariff Module and Charging Profiles in OCPI 2.2.1. This allows CPOs to push dynamic, time-of-use pricing to eMSPs in real-time. It also enables Smart Charging commands, allowing the eMSP to request specific power limits during a session (e.g., for grid balancing services) if the commercial agreement permits it.
CONTACT US
Let’s Talk EV
Find out how Codibly’s consultancy and development services can accelerate your EV business. Book a call and let’s shape the future of eMobility together.
Recommended Articles
