Chargefox

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.

GitHub

Documentation

📖
RateLimits
https://app.chargefox.com/developers/docs/rate_limits
📖
Documentation
https://app.chargefox.com/developers/docs/getting_started
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/rate-limits/chargefox-rate-limits.yml
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/authentication/chargefox-authentication.yml

Other Resources

🔗
Specification
https://github.com/ocpi/ocpi
🔗
Legal
https://www.chargefox.com/legal/roaming-partner-terms-and-conditions
🔗
Partners
https://www.chargefox.com/partners
🔗
Conformance
https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/conformance/chargefox-conformance.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/chargefox-ocpi-cpo-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: chargefox:chargefox-ocpi-cpo-api
name: Chargefox OCPI CPO API
description: '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.'
humanURL: https://app.chargefox.com/developers/docs/rate_limits
baseURL: https://app.chargefox.com/ocpi/cpo
tags:
- EV Charging
- OCPI
- Roaming
- Charge Point Operator
- Locations
- Tariffs
- Australia
properties:
- type: RateLimits
  url: https://app.chargefox.com/developers/docs/rate_limits
- type: Documentation
  url: https://app.chargefox.com/developers/docs/getting_started
- type: Specification
  url: https://github.com/ocpi/ocpi
- type: Legal
  url: https://www.chargefox.com/legal/roaming-partner-terms-and-conditions
- type: Partners
  url: https://www.chargefox.com/partners
- type: RateLimits
  url: rate-limits/chargefox-rate-limits.yml
- type: Authentication
  url: authentication/chargefox-authentication.yml
- type: Conformance
  url: conformance/chargefox-conformance.yml