Changelog

All notable changes to the public ChargePilot REST API.

1.2.3 - 2026-08-13

Added

• GET /error-events/site/{id} - error events per site
• GET /error-events/site/{id}/{event_id} - error event details

1.2.2 — 2026-08-06

Fixed

• Getting Started signing example now signs the full request path (including the /rest/v1 prefix), so the generated signature matches what the API validates.
• Corrected the documented GET /charging-events/site/{id} response to match the API — a JSON array of event objects (TransactionID, StartAt, EnergyDelivered, …) rather than a wrapped object with snake_case fields.
• Added the missing live-data scope (covering /rest/v1/live) to the Scopes reference.
• Corrected the sort_field query parameter name in the Live Data reference and removed an invalid trailing comma from the Scopes example response.

1.1.12 — 2026-07-02

Added

• This changelog page, documenting public REST API changes per version.

1.1.11

Changed

• Increased rate limiting from 12 requests / api-key / endpoint to 40 requests / api-key / endpoint

1.1.9

Added

• GET /live/site/{id}/charging-points — current status of every charging point at a site.
• GET /live/site/{id}/power-and-limits — time-series site power consumption and active limits.
• GET /scopes — discover which resources and endpoints your API key can access.

Changed

• Query parameters are now snake_case across the REST API.

1.1.5

Added

• API keys can now be scoped to specific resources, restricting which endpoints a key may call.
• API key usage is now logged for auditing.

1.0.0

Initial public release of the ChargePilot REST API.

Added

• GET /ping — an unauthenticated endpoint for wellness checks.
• GET /sites — list all sites associated with the API key.
• GET /sites/{id} — retrieve a specific site by ID.
• GET /ocpp-logs/site/{id} — retrieve OCPP protocol logs for a site.
• GET /charging-events/site/{id} — retrieve historical charging events for a site.
• HMAC request signing via the x-api-key and x-signature headers.
• Per-endpoint rate limiting.
• Protection behind Cloudflare API Shield.