ChargeIndia Hub Docs

Hub Receiver Identity (CPO)

How CPOs set country_code and party_id when pushing catalog and session data to ChargeIndia Hub.

When you push locations, tariffs, and sessions to ChargeIndia Hub, URL paths and object bodies use your CPO identity. Hub authenticates with the Hub token, then forwards the same CPO {country_code}/{party_id} to routed eMSPs.

For the shared model (auth = Hub, path = owning CPO), see Hub Receiver Identity.

Requirements

When pushing data to Hub:

  1. Use your own CPO country_code and party_id in URL paths and object bodies.
  2. Hub forwards the same identifiers to routed eMSPs, do not use Hub (CIH) in your push paths.
  3. Include cdr_token with the eMSP's party on every session so Hub can route async delivery.

Location forward example

You send:

PATCH /ocpi/2.2.1/locations/IN/CPO/LOC1/EVSE1
Authorization: Token {cpo-token}
Content-Type: application/json

{ "status": "CHARGING", "uid": "EVSE1" }

Hub forwards the same path and body to eMSP receivers. The path uses your identifiers, not Hub (IN / CIH).

Checklist

  • [ ] Location/tariff/session pushes to Hub use your CPO {country_code}/{party_id} in path and body
  • [ ] Session cdr_token identifies the correct eMSP on every update

Troubleshooting

SymptomLikely causeFix
Location push succeeds on Hub but eMSP never updateseMSP receiver rejecting path partyAsk the eMSP to follow eMSP Hub Receiver Identity
Session not delivered to eMSPMissing cdr_token on session pushSet eMSP identity on every session update