OCPI 2.2.1

The OCPI 2.2.1 specification, one page per module — field tables, request/response examples, and JSON Schemas.

• Credentials module — Module Identifier: credentials
• 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 these for later ve…
• CDRs module — Module Identifier: cdrs
• ChargingProfiles module — Module Identifier: chargingprofiles
• Commands module — Module Identifier: commands
• HubClientInfo module — Module Identifier: hubclientinfo
• Locations module — Module Identifier: locations
• Sessions module — Module Identifier: sessions
• Tariffs module — Module Identifier: tariffs
• Tokens module — Module Identifier: tokens
• Status codes — There are two types of status codes:
• Terminology and Definitions — The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and
• Supported Topologies — OCPI started as a bilateral protocol, for peer-to-peer communication.
• 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 — Case Insensitive String. Only printable ASCII allowed.
• versionhistory — Version History
• Versions module — Type: Configuration Module