Terminology and Definitions
Key terms, abbreviations, market roles, provider/operator distinctions, charging topology, variable naming conventions, cardinality, and data retention rules used throughout the OCPI protocol.
Supported Topologies
Network topologies supported by OCPI, from simple peer-to-peer connections through dual and mixed-role configurations to Hub-based architectures with message routing.
Transport and Format
JSON/HTTP implementation guide covering security and authentication, pull and push models, request and response formats, message routing, unique IDs, endpoints, and offline behaviour.
Status Codes
HTTP transport status codes and OCPI content-level status codes covering the success (1xxx), client error (2xxx), server error (3xxx), and hub error (4xxx) ranges.
Versions Module
Required base module for discovering supported OCPI versions and their available endpoints, including version information, version details, data types, and GET examples.
Credentials Module
Exchange of credentials tokens for authorisation of requests between OCPI platforms, including use cases, sender and receiver interfaces, object descriptions, and data types.
Locations Module
Charging Location objects owned by the CPO, describing the operator's charging sites. Covers interfaces, object descriptions, and data types for managing locations via OCPI.
Sessions Module
Charging Session objects describing one charging session, with the session lifecycle, sender and receiver interfaces, object descriptions, and data types used between CPO and eMSP systems.
CDRs Module
Charge Detail Record describing a concluded charging session — the only billing-relevant object. Covers the CDR lifecycle, sender and receiver interfaces, object descriptions, and data types.
Guides marked Coming Soon are actively being developed. Check back for updates as more implementation guides are published.