OCPI
Roaming connectivity with OCPI 2.1.1 and 2.2.1 on GridOS.
OCPI is how GridOS exchanges roaming data with eMSPs and hubs: locations, tariffs, sessions, CDRs, tokens, and credentials.
Versions
GridOS targets OCPI 2.1.1 and 2.2.1. Behavior and modules differ — implement and query versions in parallel where both are active.
| Version | Start here |
|---|---|
| OCPI 2.1.1 | Modules, types, transport, credentials |
| OCPI 2.2.1 | Modules plus hub client info and charging profiles |
Operator path
Credentials handshake
Establish mutual tokens and versions — Credentials handshake.
Roaming go-live
Locations, authorization, sessions, and CDRs — Roaming.
Never paste live OCPP passwords, OCPI tokens, or client certificates into tickets, chat, or public issues. Rotate anything that may have been exposed and use Dashboard or your secret store for operational credentials.
Typical modules
| Module | Purpose |
|---|---|
| Versions / Credentials | Discovery and token exchange |
| Locations | Sites, EVSEs, connectors |
| Tariffs | Pricing published to partners |
| Sessions | Live session state for roaming |
| CDRs | Charge detail records for billing settlement |
| Tokens | Authorization tokens from eMSPs |
| Commands | Start/stop and other remote commands |
Exact module set depends on role (CPO vs eMSP) and negotiated versions with each partner.
Specification indexes
OCPI 2.1.1
- Introduction
- Credentials
- Locations · Sessions · CDRs
- Tariffs · Tokens · Commands
- Types · Status codes
OCPI 2.2.1
- Introduction
- Credentials
- Locations · Sessions · CDRs
- Hub client info · Charging profiles
- Topology · Types
The left sidebar keeps module indexes (not every field table). Open the version overview or use ⌘K search — hit labels include the protocol version (for example · OCPI 2.2.1) so similarly named modules stay distinct.
See also
- GridOS product — partner configuration and Dashboard surfaces
- OCPP — charge-point connectivity that feeds roaming sessions