Guest organisation
OCPI
Learn reference
Guest organisation
OCPI
Learn reference

Explore the OCPI messages

By Abhishek Uniyal · Updated

Step 4 of 5

OCPI 2.2.1

Compare versions

An OCPI message has a sender, a receiver and an endpoint. Inspect the request and read the HTTP status separately from the response body.

What changes in OCPI 2.2.1
Modules in OCPI 2.2.1
Sessions
CDRs
Locations
Tariffs
Tokens
Commands
Credentials
Versions
Hub Client Info
Charging Profiles
Payments · extension
Advertised sender and receiver interfaces

An endpoint declares how another platform can pull or push data. Credentials uses the same interface for both roles.

The header token is encoded

The request header carries an encoded token; the Credentials body still carries the raw token.

Billing records name the Token owner

A charge record names the country and company that own the driver's Token.

What should I inspect in a message?

Read the protocol result in this response excerpt. It does not prove what a billing system did.

Teaching example · OCPI 2.2.1 response body excerpt

{
  "status_code": 1000
}

The OCPI response field status_code describes the protocol result; 1000 is generic success. Use Protocol details on a guided step to open its payload excerpt and the source clauses. An excerpt may omit required fields.

Sources (2)
"OCPI status code, as listed in Status Codes, indicates how the request was handled. To avoid confusion with HTTP codes, OCPI status codes consist of four digits."OCPI 2.2.1 Transport and format chapter · #transport_and_format_response_format1000: Generic success codeOCPI 2.2.1 Status codes chapter · #status_codes_1xxx_success
Read the new Session request