OCPI 2.2.1
Index of the OCPI 2.2.1 specification modules, each on its own page with field tables, examples, and JSON Schemas.
The OCPI 2.2.1 specification, one page per module — field tables, request/response examples, and JSON Schemas.
- Credentials module — OCPI 2.2.1 Credentials module — Module Identifier: credentials
- OCPI — OCPI 2.2.1 OCPI — In the OCPI Development Working Group at the EV Roaming Foundation we are always tracking unclarities in the specification and making changes to the specification document to fix…
- CDRs module — OCPI 2.2.1 CDRs module — Module Identifier: cdrs
- ChargingProfiles module — OCPI 2.2.1 ChargingProfiles module — Module Identifier: chargingprofiles
- Commands module — OCPI 2.2.1 Commands module — Module Identifier: commands
- HubClientInfo module — OCPI 2.2.1 HubClientInfo module — Module Identifier: hubclientinfo
- Locations module — OCPI 2.2.1 Locations module — Module Identifier: locations
- Sessions module — OCPI 2.2.1 Sessions module — Module Identifier: sessions
- Tariffs module — OCPI 2.2.1 Tariffs module — Module Identifier: tariffs
- Tokens module — OCPI 2.2.1 Tokens module — Module Identifier: tokens
- Status codes — OCPI 2.2.1 Status codes — There are two types of status codes:
- Terminology and Definitions — OCPI 2.2.1 Terminology and Definitions — The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and
- Supported Topologies — OCPI 2.2.1 Supported Topologies — OCPI started as a bilateral protocol, for peer-to-peer communication.
- Transport and format — OCPI 2.2.1 Transport and format — The OCPI protocol is based on HTTP and uses the JSON format. It follows a RESTful architecture for web services where possible.
- Types — OCPI 2.2.1 Types — Case Insensitive String. Only printable ASCII allowed.
- versionhistory — OCPI 2.2.1 versionhistory — Version History
- Versions module — OCPI 2.2.1 Versions module — Type: Configuration Module