Chargers

Charger endpoints expose EV chargers linked to an address, including latest charge state and energy consumption history.

Base path: /api/v2/addresses/:address_uuid/chargers
Permission: READ_CHARGER_DATA

What we provide

Method	Path	Purpose
`GET`	`/`	List chargers for the address
`GET`	`/:charger_uuid/energy/consumption`	Charger energy consumption over a time range

Payload

Typical charger object includes:

Identity (identifier)
Brand, model, year
Capability flags such as isSteerable and liveDataSupported
lastChargeState, including fields such as:
- isPluggedIn
- isCharging
- chargeRate
- maxCurrent
- powerDeliveryState
- time
Created / updated / deleted timestamps

Consumption

The consumption route returns time-bounded energy usage for analytics, settlement previews, and operational reporting. Use date-range filters documented in OpenAPI for that operation.

Guidance

Use list + latest charge state for live operational boards.
Use consumption history for reporting and optimization.
Capability flags (isSteerable, liveDataSupported) describe what the asset can do; they are not a live health heartbeat.
Correlate with Vehicle state at the same address when building charging workflows.
Expect asynchronous update timing between charger and vehicle domains.