# Electra OCPI CPO API

**Canonical:** https://apis.io/apis/go-electra/go-electra-ocpi-cpo-api/  
**Provider:** Electra — https://apis.io/providers/go-electra/  
**Base URL:** https://ocpi.go-electra.com/ocpi/cpo  
**Documentation:** https://ocpi.go-electra.com/ocpi/cpo/versions

Electra OCPI CPO API is published by [Electra](https://apis.io/providers/go-electra/) on the [APIs.io](https://apis.io/) network. Tagged areas include EV Charging, OCPI, Roaming, Charge Point Operator, and Locations. The published artifact set on APIs.io includes authentication docs and rate-limit docs.

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.

## Machine-readable artifacts (9)

- **Specification** — https://github.com/ocpi/ocpi
- **Authentication** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/authentication/go-electra-authentication.yml
- **Conformance** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/conformance/go-electra-conformance.yml
- **Conventions** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/conventions/go-electra-conventions.yml
- **ErrorCatalog** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/errors/go-electra-problem-types.yml
- **Examples** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/examples/_index.yml
- **RateLimits** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/rate-limits/go-electra-rate-limits.yml
- **Lifecycle** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/lifecycle/go-electra-lifecycle.yml
- **APIsJSON** — https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/apis.yml

## Tags

EV Charging, OCPI, Roaming, Charge Point Operator, Locations, Tariffs, Charging Sessions, Europe

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/go-electra/go-electra-ocpi-cpo-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/go-electra/.