Chargefox OCPI CPO API
Chargefox's Open Charge Point Interface implementation in the Charge Point Operator role, used for roaming so that another network's drivers can authorise, charge and be billed on Chargefox infrastructure. No OCPI specification document is published by Chargefox, but the surface is documented by the company in its own developer rate-limits page, which names the endpoints version by version and module by module: locations under /ocpi/cpo/2/, /ocpi/cpo/2.1.1/, /ocpi/cpo/2.2/ and /ocpi/cpo/2.2.1/ (with separate index and show limits); sessions under 2.1.1, 2.2 and 2.2.1; CDRs under 2.2 and 2.2.1; tariffs under 2.2 and 2.2.1; a PUT tokens endpoint under 2.2 and 2.2.1; and a POST commands endpoint under 2.2. Existence was independently confirmed by anonymous probe on 2026-07-27 — GET /ocpi/cpo/versions, /ocpi/cpo/2.1.1/, /ocpi/cpo/2.2/, /ocpi/cpo/2.2.1/, /ocpi/cpo/2.1.1/locations and /ocpi/emsp/versions all returned HTTP 401 with the header `WWW-Authenticate: Token realm="Application"`, which is OCPI's own Token authorization scheme, while sibling paths such as /ocpi/, /ocpi/cpo/ and /ocpi/xyz/versions returned 404, proving the 401 is a real route and not a blanket wall. Access is partner-only: an OCPI credentials handshake follows a commercial roaming agreement, and Chargefox publishes roaming partner terms and conditions rather than a developer signup.