# Chargefox

> Chargefox is Australia's largest public electric-vehicle charging network and, since 2023, a charging software platform rather than a hardware owner. Founded in 2017, headquartered in Melbourne, and owned outright since 2022 by Australian Motoring Services — the joint vehicle of six state motoring clubs (NRMA, RACV, RACQ, RAA, RAC, RACT). It publishes two API surfaces: a small, documented, read-only Fleets API described by OpenAPI 3.0.1, and a full Open Charge Point Interface (OCPI) Charge Point Operator implementation across protocol versions 2, 2.1.1, 2.2 and 2.2.1. Both are entirely closed — every endpoint returns 401 to an anonymous request, there is no self-service signup, no sandbox and no developer key. Chargefox publishes zero open market data: no anonymous locations feed, no tariff feed, no network-status feed. This file was generated by API Evangelist from the provider's own public documentation; Chargefox does not publish an llms.txt.

## What an agent needs to know first

- There is no way to get a credential without a commercial relationship. Fleet customers request a bearer token from fleetsupport@chargefox.com. Roaming partners exchange OCPI Token credentials after signing a roaming agreement.
- The entire public REST contract is GET-only. Nothing here creates, updates or deletes anything.
- Rate limits are tight and published per endpoint — 18 requests / 15 minutes on usage and sessions. Honour `X-RateLimit-Reset` and cache aggressively.
- The Australian Consumer Data Right does not apply. Chargefox is not on the ACCC CDR Register (checked 2026-07-27); it operates charge points rather than holding a retail electricity licence.

## APIs

- [Chargefox Fleets API](https://app.chargefox.com/developers/docs/fleets): Four read-only GET operations for fleet customers — usage, sessions, vehicles, invoices. OpenAPI 3.0.1, bearer auth, page-number pagination at 100 records per page. Base URL https://app.chargefox.com/api/fleets/v1
- [Chargefox OCPI CPO API](https://app.chargefox.com/developers/docs/rate_limits): OCPI Charge Point Operator implementation covering locations, sessions, CDRs, tariffs, tokens and commands. Base path https://app.chargefox.com/ocpi/cpo. No specification document is published by Chargefox; the endpoint inventory is documented only in its rate-limits page.

## Operations (Fleets API)

- `GET /api/fleets/v1/usage` — every charge session completed by a fleet's managed vehicles anywhere on the Chargefox network, with per-charging-period consumption, tariff, GST and AUD amount. Params: date_from, date_to, page.
- `GET /api/fleets/v1/sessions` — every charge session completed on a fleet's own charge stations, with the site-host revenue/cost/GST split. Params: date_from, date_to, page.
- `GET /api/fleets/v1/vehicles` — the fleet's managed-vehicle register: VIN, registration, contract number, effective dates, attached RFID cards. Params: page.
- `GET /api/fleets/v1/invoices` — fleet and site-host invoices with line items, billed vehicles and the charge sessions behind them. Params: date_from, date_to, page.

## Docs

- [Getting Started](https://app.chargefox.com/developers/docs/getting_started): How to obtain access and make a request; includes the canonical curl example.
- [Fleets API reference](https://app.chargefox.com/developers/docs/fleets): Redoc rendering of the OpenAPI 3.0.1 contract.
- [Rate limits](https://app.chargefox.com/developers/docs/rate_limits): The full per-endpoint limit table for both the Fleets API and the OCPI CPO API, plus the X-RateLimit-* header contract.
- [OCPI specification](https://github.com/ocpi/ocpi): The open industry standard Chargefox implements in the CPO role (third-party, not Chargefox).

## Specs and artifacts

- [OpenAPI 3.0.1 — Fleets API](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/openapi/chargefox-fleets-api-openapi.json): The provider's contract, harvested verbatim.
- [APIs.json index](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/apis.yml): The full API Evangelist index for Chargefox.
- [API conventions](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/conventions/chargefox-conventions.yml): Auth, pagination, filtering, error envelope, rate-limit signalling, units and money handling.
- [Rate limits](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/rate-limits/chargefox-rate-limits.yml): All 25 published limits, structured.
- [Error catalog](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/errors/chargefox-problem-types.yml): 401, 403 and 429 — the whole declared error surface.
- [Authentication](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/authentication/chargefox-authentication.yml): The bearerAuth profile.
- [Data model](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/data-model/chargefox-data-model.yml): Entity graph — Customer, Vehicle, Card, ChargeSession, ChargingPeriod, Location, EVSE, Connector, Invoice.
- [Conformance](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/conformance/chargefox-conformance.yml): OCPI 2.1.1/2.2/2.2.1 CPO conformance and the cross-cutting standards posture.
- [Lifecycle](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/lifecycle/chargefox-lifecycle.yml): Versioning, status page, and the absence of a deprecation policy or changelog.
- [Response examples](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/examples/_index.yml): The four 200 payloads extracted from the contract.
- [Agent skills](https://raw.githubusercontent.com/api-evangelist/chargefox/refs/heads/main/skills/_index.yml): Packaged operating instructions for the marquee fleet flows.

## Operations and status

- [Status page](https://www.chargefox.com/status): Atlassian Statuspage with components for OCPI, Platform, Fleet Management API, Mobile Application, APIs and Hardware Vendors.
- [Status JSON API](https://chargefox.statuspage.io/api/v2/summary.json): Anonymous, machine-readable, and the only Chargefox-operated endpoint in this index that returns data without a credential.
- [Trust Center](https://trust.chargefox.com/): Vanta-hosted. Certifications are rendered client-side and are not asserted here.

## Company

- [Website](https://www.chargefox.com/)
- [About](https://www.chargefox.com/company)
- [News](https://www.chargefox.com/news)
- [Partners](https://www.chargefox.com/partners)
- [Support](https://support.chargefox.com/hc/en-au)
- [GitHub](https://github.com/chargefox): Five public repositories, none of them a client for these APIs.
- [Terms and conditions](https://www.chargefox.com/legal/terms-conditions)
- [Roaming partner terms](https://www.chargefox.com/legal/roaming-partner-terms-and-conditions)
- [Privacy policy](https://www.chargefox.com/legal/privacy-policy)

## What does not exist

Recorded so an agent does not waste calls looking: no SDKs in any package registry, no CLI, no Postman collection, no MCP server, no GraphQL endpoint, no AsyncAPI or documented webhooks, no `/.well-known/` documents of any kind (no security.txt, no OAuth or OIDC discovery), no sandbox, no changelog, no public pricing page for API access, and no OAuth — authentication is an opaque bearer token for Fleets and an OCPI Token for roaming.