OCPI Explorer
Interactive reference for each OCPI module
Every OCPI module, and what it is for
OCPI is not one API, it is a set of modules, and an integration usually only needs some of them. Locations tells the world where your chargers are. Tokens says who may use them. Sessions and CDRs describe a charge in progress and a charge that finished. Tariffs says what it costs. Commands lets the other side start and stop a charge remotely. Credentials is the handshake that makes any of it possible.
The explorer takes each of these in turn: what the module is responsible for, what its objects look like, and which version introduced it, so you can work out what you actually have to build rather than reading the specification cover to cover.
Where to go next
Common questions
What is the OCPI Module Explorer?
The OCPI Module Explorer is an interactive reference for each OCPI 2.2.1 module including Sessions, CDRs, Locations, Tariffs, Tokens, Commands, Credentials, and Versions. It shows data models, endpoints, and field-level documentation.
Which OCPI modules are covered?
The explorer covers all core OCPI 2.2.1 modules: Sessions (charging lifecycle), CDRs (billing records), Locations (station data), Tariffs (pricing), Tokens (driver auth), Commands (remote control), Credentials (registration), and Versions (endpoint discovery).
Do I have to implement every module?
No. What you implement depends on your role and what your partners need. A CPO publishing chargers and billing for them needs Locations, Sessions, CDRs and Tariffs at minimum. Charging Profiles, Booking and Payments are optional and version dependent.
Which modules changed in 2.3.0?
2.3.0 adds Payments, the module behind paying by card at the charger, and Booking for reserving one. It also brings the tax model and the AFIR parking fields that European regulation asks for.