Endpoints
| Method | Path | Description |
|---|---|---|
GET | /ocpi/2.2.1/hubclientinfo | List all connected parties |
GET | /ocpi/2.2.1/hubclientinfo/{country_code}/{party_id} | Single party status |
Hub role: SENDER (Hub provides data to partners)
Status values
| Status | Description |
|---|---|
CONNECTED | Partner reachable and active |
OFFLINE | Health checks failing |
PLANNED | Registered, not yet active |
SUSPENDED | Suspended by account team |
Response example
{
"status_code": 1000,
"data": [
{
"party_id": "ABC",
"country_code": "IN",
"role": "CPO",
"status": "CONNECTED",
"last_updated": "2025-06-23T10:00:00.000Z"
}
]
}
Use cases
- Check roaming partner availability before initiating sessions
- Monitor your own connection status
- Build operational dashboards
See Connection Health for probe details.
OCPI spec
See OCPI 2.2.1 HubClientInfo module for full object definitions.