Steps

Expose or consume the locations endpoint returning nested Location > EVSE > Connector objects
Agree with the counterparty which OCPI interface role (owner vs receiver, push vs pull) governs location sync for this relationship
Propagate EVSE status changes (e.g. AVAILABLE, CHARGING, OUTOFORDER) promptly so eMSP-facing apps reflect real-time availability
Include connector power_type, max_electric_power, and tariff_ids so consuming parties can display accurate charging capability
Verify 2.2.1 support via the credentials/versions handshake before relying on version-specific fields like parking_restrictions

Known gotchas

OCPI supports both push and pull synchronization patterns, and the two parties must explicitly agree which role applies per module — a mismatched assumption means location updates silently stop flowing to one side
Incremental sync is governed by connector/EVSE-level last_updated timestamps combined with the date_from/date_to query parameters, not a single location-level timestamp

github.com/ocpi · 5 steps · unrated

Manage charge points with OCPP 2.0.1: device model, variables, security profiles

openchargealliance.org · 6 steps · unrated

Process OCPI 2.2.1 Sessions module real-time updates for an in-progress charging session

evroaming.org · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Publish and synchronize charge point location and connector status data via the OCPI 2.2.1 locations module

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?