Connection Health

ChargeIndia Hub tracks partner connection status and exposes it through the HubClientInfo module.

HubClientInfo statuses

Status	Meaning
`CONNECTED`	Partner is reachable and recently active
`OFFLINE`	Partner failed health checks (typically > 1 minute)
`PLANNED`	Partner registered but not yet active
`SUSPENDED`	Partner suspended by account team

Query statuses:

GET /ocpi/2.2.1/hubclientinfo
Authorization: Token {your-token}

Or for a specific party:

GET /ocpi/2.2.1/hubclientinfo/{country_code}/{party_id}

The Hub worker periodically calls GET /ocpi/versions on each partner's registered URL. Ensure your versions endpoint:

If probes fail consistently, your status transitions to OFFLINE and realtime flows (authorization, commands) may fail.

Condition	Effect
CPO `OFFLINE`	Token authorization may return `UNKNOWN`; commands may fail
eMSP `OFFLINE`	Async session/CDR delivery retries; may eventually DLQ
Either `SUSPENDED`	All authenticated Hub requests return `401`
CPO not in HubClientInfo allow-list	eMSP receiver may reject inbound location/tariff/session pushes with invalid party errors

Poll HubClientInfo for your roaming partners before initiating sessions
Use HubClientInfo to build the set of valid CPO party keys for inbound receiver validation (intersect with routing rules)
Alert on your own OFFLINE status
Log and investigate failed health probes on your platform