ChargeIndia Hub DocsBefore you integrate, ensure your organization has a commercial agreement with ChargeIndia and has been assigned OCPI credentials.
Prerequisites
Commercial
- Contact your ChargeIndia account team to register as a CPO or eMSP.
- Receive your assigned
country_codeandparty_id(e.g.IN+ABC). - Confirm which partner networks you will roam with (routing rules are configured per eMSP↔CPO pair).
Technical
- OCPI 2.2.1 compliance on your platform
- HTTPS with a valid TLS certificate on your OCPI endpoints
- Ability to implement both sender and receiver interfaces as required by your role
- Persistent logging with correlation IDs for support
Environments
| Environment | Base URL |
|---|---|
| Production | https://hub.chargeindia.com |
| Sandbox | https://sandbox-hub.chargeindia.com |
Use Sandbox for integration and UAT. Use Production for live roaming traffic. Your account team issues tokens and credentials for each environment.
Your account team will provide:
- Hub base URL for your target environment (see table above)
- Initial Hub-issued token for credentials exchange
- Credentials exchange URL (
POST /ocpi/2.2.1/credentials)
Integration checklist
All partners
- [ ] Complete credentials exchange
- [ ] Implement authentication on all Hub calls
- [ ] Expose
GET /ocpi/versionsfor Hub health monitoring - [ ] Register receiver module URLs with your account team
- [ ] Verify routing rules cover your target partners
CPO partners
- [ ] Push locations and tariffs to Hub
- [ ] Implement token authorization receiver
- [ ] Implement command receiver (
START_SESSION,STOP_SESSION, etc.) - [ ] Push sessions and CDRs to Hub
eMSP partners
- [ ] Implement token authorization caller
- [ ] Implement command sender
- [ ] Implement session and CDR receivers (async push from Hub)
- [ ] Pull locations and tariffs from Hub
Coordinated testing
Run integration tests against Sandbox (https://sandbox-hub.chargeindia.com) with your ChargeIndia account team using a coordinated test matrix.
Prerequisites
- Commercial onboarding complete with assigned
country_code,party_id, and Hub token - Credentials exchange finished - see Onboarding
- Receiver URLs registered and routing enabled for your test partner pair
- Both parties available for a scheduled test window
Suggested test matrix
Run these steps in order with your account team observing Hub logs:
| Step | Actor | Action | Verify |
|---|---|---|---|
| 1 | Both | GET /ocpi/versions and GET /ocpi/2.2.1 | OCPI 2.2.1 listed; modules present |
| 2 | Both | GET /ocpi/2.2.1/hubclientinfo | Counterparty shows CONNECTED |
| 3 | eMSP | Token authorize via Hub | CPO returns ALLOWED |
| 4 | eMSP | START_SESSION command | CPO accepts; async result on response_url |
| 5 | CPO | Push active session with valid cdr_token | eMSP receives async session update |
| 6 | eMSP | STOP_SESSION command | CPO completes session |
| 7 | CPO | POST CDR | eMSP receives async CDR |
See Session Lifecycle and Certification for detailed sign-off criteria.
If a step fails, start with Troubleshooting before contacting support.
Continue to your path
After completing the shared checklist above, follow your role-specific integration path:
- CPO: CPO Integration Guide - push locations, tariffs, sessions, and CDRs; receive authorization and commands
- eMSP: eMSP Integration Guide - authorize tokens, send commands, receive async updates
Verify connectivity
After credentials exchange, call:
GET /ocpi/versions
Authorization: Token {your-hub-token}
You should receive OCPI version 2.2.1 with a URL to version details. Then call version details to confirm module endpoints:
GET /ocpi/2.2.1
Authorization: Token {your-hub-token}
Related docs
- Onboarding - credentials handshake
- Authentication - headers and response envelope
- CPO Integration Guide - CPO integration path
- eMSP Integration Guide - eMSP integration path
- API Reference - per-module endpoints
- Troubleshooting - common integration issues