CPO pushes its Locations to the eMSP

Technical · 3 min

OCPI 2.1.1, 2.2.1 and 2.3.0

Showing OCPI 2.2.1. Physical and billing-system events are authored examples.

Part of the lesson OCPI charging session lifecycle

Step 3 of 4 · Roaming connection setup
locationsCPOsendseMSPreceives
locationsCPOsendseMSPreceives
Legend

The line follows the selected step. Actor dots identify the parties; they show no conformance verdict.

Step 3 of 4 · Paused

Selected step

All 2 actors

CPO · eMSP

Selected exchange

Now connected, the CPO pushes its charging locations to the eMSP. Each location includes EVSEs, connectors, and real-time availability so drivers can find and navigate to chargers.

CPO → eMSP · locations

Source
"The Location objects live in the CPO back-end system. They describe the charging locations of an operator."OCPI 2.2.1 specification · #mod_locations_locations_module
Why this matters

The CPO publishes information about its charging locations to connected platforms.

Explore the locations module

Sandbox run · OCPI 2.2.1

Run this exchange in the sandbox

Test this flow

Test this flow runs against an eMSP endpoint you have registered.