Hub Client Info
Hub Client Info in OCPI 2.2.1
The Hub owns ClientInfo and sends connection information to connected parties, which act as Receivers. The typical-role module table is guidance, not a mandatory roster. A platform can provide combined CPO and eMSP services. ClientInfo.role follows this version's wire Role enum. This version includes HUB in its Role enum; that value is not universal across later versions.
Sources (7)
Example payload · connected-cpo
{
"country_code": "NL",
"party_id": "EXA",
"role": "CPO",
"status": "CONNECTED",
"last_updated": "2026-01-01T00:00:00Z"
}Example payload · offline-emsp
{
"country_code": "NL",
"party_id": "EXB",
"role": "EMSP",
"status": "OFFLINE",
"last_updated": "2026-01-01T00:00:00Z"
}Which endpoints does this module define?
These paths illustrate the requests. Use the URLs advertised by your partner, replace the placeholders and choose the matching interface. A listed method does not establish that this site's simulator implements it.
Connected party · receiver interface
Retrieve a ClientInfo object as it is stored in the connected clients system.
GET/ocpi/ 2.2.1/ clientinfo/ {country_code}/ {party_id} Push new/updated ClientInfo object to the connect client.
PUT/ocpi/ 2.2.1/ clientinfo/ {country_code}/ {party_id}
Source
Hub · sender interface
Get the list of known ClientInfo objects, last updated between the {date_from} and {date_to} paginated)
GET/ocpi/ 2.2.1/ clientinfo/
Source
Try an endpoint
Send a request to this site's OCPI endpoints and read the answer. It never reaches your own system.