Electra OCPI CPO API
Electra's Open Charge Point Interface implementation in the Charge Point Operator role — the roaming interface an e-mobility service provider calls to read Electra's locations and tariffs, authorise its own drivers on Electra hardware, receive session and charge-detail records, and send remote start/stop commands. Electra publishes no human documentation and no specification document for it; the surface was established entirely by anonymous probe on 2026-08-17. GET https://ocpi.go-electra.com/ocpi/cpo/versions returned HTTP 200 (application/json) advertising two concurrent protocol versions, 2.1.1 and 2.2.1. GET /ocpi/cpo/2.1.1 returned HTTP 200 enumerating seven module endpoints — cdrs, commands, credentials, locations, sessions, tariffs, tokens. GET /ocpi/cpo/2.2.1 returned HTTP 200 enumerating the same modules plus explicit OCPI 2.2.1 roles: cdrs SENDER, commands RECEIVER, credentials both SENDER and RECEIVER, locations SENDER, sessions SENDER, tariffs SENDER, tokens RECEIVER. Every module endpoint itself is closed: GET /ocpi/cpo/2.2.1/locations, /ocpi/cpo/2.1.1/locations and /ocpi/cpo/2.2.1/tariffs each returned HTTP 401 with the body `Token: Access denied.` and the header `WWW-Authenticate: Token realm="Application"`, which is OCPI's own bilateral Token authorization scheme rather than a blanket wall — sibling paths such as /ocpi/versions, /ocpi/cpo/2.0.1 and /ocpi/cpo/2.2.1/credentials returned 404, proving the 401s are real routes. Access follows a commercial roaming agreement and an OCPI credentials handshake; there is no signup, no sandbox and no self-service token. No anonymous locations, tariff or availability feed of any kind is published, so Electra exposes zero open charging-network market data.