Use this page as a starting point when something fails during integration or production traffic. Each item links to the detailed reference.
Authentication
| Symptom | Likely cause | Fix |
|---|
2002 on all Hub requests | Invalid, revoked, or wrong token | Re-check credentials from exchange; see Token Rotation |
HTTP 401 with status_code: 2002 | Suspended party account | Contact your ChargeIndia account team |
| Auth works on some routes only | Raw vs Base64 token mismatch | Send Authorization: Token {Base64(UTF-8(token))} per Authentication |
Routing
| Symptom | Likely cause | Fix |
|---|
| Empty location or tariff list | No routing rules for your eMSP↔CPO pairs | Contact account team to enable routing |
Authorization failure / NOT_ROUTED | Target CPO not in your routing matrix | Verify routing with account team |
| Command reaches wrong party | Incorrect CPO country_code / party_id in path | Use owning CPO identifiers in outbound calls |
Sessions and CDRs
| Symptom | Likely cause | Fix |
|---|
| Session not received by eMSP | Missing or incorrect cdr_token on CPO push | CPO must set eMSP identity on every session - see Session Lifecycle |
| CDR not received by eMSP | Same as session - bad cdr_token or receiver URL | Verify CPO push fields and eMSP receiver registration |
| Async delivery delayed | eMSP receiver slow or temporarily down | Hub retries; ensure idempotent receivers - see Async Delivery |
Commands
| Symptom | Likely cause | Fix |
|---|
Command REJECTED | EVSE busy, invalid location/EVSE, or routing gap | Verify location IDs and routing |
| No async command result | Missing or unreachable response_url | eMSP must expose a valid callback endpoint |
| Callback auth failure | Expecting CPO token instead of Hub context | Command callbacks arrive via Hub - see Commands |
Async delivery and receivers
| Symptom | Likely cause | Fix |
|---|
| HTTP 400: invalid path party on eMSP receiver | P2P-style validation - path must be owning CPO, not eMSP or Hub | See Hub Receiver Identity (eMSP) |
| Catalog updates missing | Location has publish: false or routing not enabled | Check CPO publish flag and routing rules |
| Duplicate records after retry | Receiver not idempotent | Accept repeated PUT/POST with same IDs |
Rate limits
| Symptom | Likely cause | Fix |
|---|
status_code: 2004 or HTTP 429 | Per-party rate limit exceeded | Back off exponentially; see Rate Limits & Errors |
Connection health
| Symptom | Likely cause | Fix |
|---|
Authorization UNKNOWN | CPO unreachable or not CONNECTED | Poll HubClientInfo and fix CPO availability |
| Partner missing from HubClientInfo | Credentials or routing not complete | Finish Onboarding and routing enablement |
What to send support
When contacting your account team, include:
X-Request-ID and X-Correlation-ID- Timestamp (UTC), endpoint, HTTP method, party identity
- Request/response bodies with tokens redacted
See Support & Security for security reporting and compatibility notes.
ChargeIndia Hub Docs