OCPI roaming go-live

Use this after a successful credentials handshake.

Scope

Confirm with your partner:

• Roles (CPO / eMSP / hub)
• OCPI versions (2.1.1 and/or 2.2.1)
• Modules required for go-live (at minimum Locations + Tokens + Sessions + CDRs for most CPO setups)

Never paste live OCPP passwords, OCPI tokens, or client certificates into tickets, chat, or public issues. Rotate anything that may have been exposed and use Dashboard or your secret store for operational credentials.

Go-live steps

1. 1

   Credentials stable

   • Mutual tokens stored and rotated only via a controlled process
   • Versions endpoint returns the negotiated version
   • Dashboard partner record matches the peer role
2. 2

   Locations published

   • Sites / EVSEs / connectors you want to roam are published
   • Status updates reach the partner (push or regular pull)
   • Private / non-roaming locations are not published
3. 3

   Authorization path

   • Tokens from the eMSP authorize sessions end-to-end
   • Failures show clear reason codes (not silent drops)
4. 4

   Sessions and CDRs

   • Live session state is visible to the partner when required
   • CDRs close after stop with energy and cost fields your settlement needs
   • OCPP session lifecycle maps cleanly into OCPI sessions / CDRs
5. 5

   Operations

   • Alerting on partner 4xx / 5xx and credential expiry
   • Runbook for token rotation without dropping roaming
   • Link from the Dashboard observability into the failing module

Module indexes

The left sidebar keeps module indexes (not every field table). Open the version overview or use ⌘K search — hit labels include the protocol version (for example · OCPI 2.2.1) so similarly named modules stay distinct.

Related

• OCPI overview
• OCPP connect — field path that feeds roaming sessions
• Webhooks