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}
Health probes
The Hub worker periodically calls GET /ocpi/versions on each partner's registered URL. Ensure your versions endpoint:
- Responds within timeout limits
- Returns OCPI 2.2.1 in the version list
- Is reachable over HTTPS
If probes fail consistently, your status transitions to OFFLINE and realtime flows (authorization, commands) may fail.
Impact on roaming
| Partner status | 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 |
Monitoring recommendations
- Poll HubClientInfo for your roaming partners before initiating sessions
- Alert on your own
OFFLINEstatus - Log and investigate failed health probes on your platform