ChargeIndia Hub connects Charge Point Operators (CPOs) and e-Mobility Service Providers (eMSPs) so drivers can charge across networks through a single roaming relationship. The Hub implements the OCPI HUB role: it routes messages between parties, enforces routing rules, and maintains an audit trail of roaming activity.
What the Hub does
- Routes OCPI 2.2.1 messages between registered CPOs and eMSPs
- Stores and forwards locations, sessions, and CDRs according to routing rules
- Provides realtime paths for token authorization and remote commands
- Exposes connection health via HubClientInfo so partners can monitor availability
What the Hub does not do (Phase 1)
- Process UPI payments, wallets, or prepaid top-ups
- Generate or store GST tax invoices
- Act as a settlement or escrow provider
- Offer self-service signup (contact your account team to onboard)
Supported parties
| Role | Description |
|---|---|
| CPO | Owns charge points; publishes locations, sessions, and CDRs |
| eMSP | Offers drivers access; issues tokens and initiates charging |
| HUB | ChargeIndia Hub (IN / CIH) — the roaming intermediary |
Hub identity
| Field | Value |
|---|---|
| Country code | IN |
| Party ID | CIH |
| OCPI version | 2.2.1 only |
Base URL layout
All Hub OCPI modules are served under:
https://{hub-domain}/ocpi/2.2.1/{module}
Partners authenticate every request with the standard OCPI header:
Authorization: Token {your-token}
OCPI modules
| Module | Hub role |
|---|---|
| Credentials | Mutual registration and token exchange |
| Versions | Advertise supported version and endpoints |
| HubClientInfo | Expose connected party statuses |
| Locations | CPO push; eMSP pull (routing-filtered) |
| Tariffs | CPO push; eMSP pull |
| Tokens | Realtime authorization (eMSP → CPO via Hub) |
| Commands | Remote start/stop and reservations |
| Sessions | CPO push to Hub; async push to eMSP |
| CDRs | CPO push to Hub; async push to eMSP |
Payload shapes follow the OCPI 2.2.1 specification. These docs describe Hub-specific routing, authentication, and integration behavior.
Next steps
- Getting Started — prerequisites and environments
- CPO Integration Guide — if you operate charge points
- eMSP Integration Guide — if you offer driver access