Before 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 | Status |
|---|---|
| Production | Available for onboarded partners |
| Sandbox | Planned — not yet available |
A dedicated sandbox environment is on the roadmap. Until it is available, coordinate test sessions with your account team before production cutover.
Your account team will provide:
- Hub base URL (e.g.
https://hub.chargeindia.com) - 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
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
- API Reference — per-module endpoints