Hub role: SENDER (Hub → eMSP async + pull)
Endpoints
| Method | Path | Description |
|---|---|---|
GET | /ocpi/2.2.1/sessions | Pull sessions belonging to this eMSP (paginated) |
GET | /ocpi/2.2.1/sessions/{cc}/{pid}/{session_id} | Pull one session (must own via cdr_token) |
PUT, PATCH | Your sessions RECEIVER URL | Async session updates from Hub |
Push + pull
You receive sessions via async push. Use GET /sessions (with optional date_from) for backfill. Pull returns only sessions where cdr_token identifies your party.
Async delivery
After CPO PUT / PATCH, the Hub worker forwards with the same HTTP method to:
PUT|PATCH /ocpi/2.2.1/sessions/{cpo_cc}/{cpo_pid}/{session_id}
on your registered receiver URL. Path uses the owning CPO's identifiers. See Hub Receiver Identity (eMSP).
Related docs
OCPI spec
See OCPI 2.2.1 Sessions module for full Session object definitions.