Smart Meters
Smart meter endpoints expose meter registry data, electricity and gas readings, interval aggregates, and delivery/return forecasts for an address.
Base path: /api/v2/addresses/:address_uuid/smart-meters
Permission: READ_SMARTMETER_DATA
What we provide
| Method | Path | Purpose |
|---|---|---|
GET | / | List smart meters for the address |
GET | /:smart_meter_uuid | Get one smart meter |
GET | /:smart_meter_uuid/energy/electricity | Electricity readings over a time range |
GET | /:smart_meter_uuid/energy/electricity/latest | Latest electricity reading |
GET | /:smart_meter_uuid/energy/gas | Gas readings over a time range |
GET | /:smart_meter_uuid/energy/gas/latest | Latest gas reading |
GET | /:smart_meter_uuid/interval/electricity | Electricity interval aggregation |
GET | /:smart_meter_uuid/interval/gas | Gas interval aggregation |
GET | /:smart_meter_uuid/delivery-forecast | Delivery forecast |
GET | /:smart_meter_uuid/return-forecast | Return forecast |
EAN lookup (no address in path)
| Method | Path | Purpose |
|---|---|---|
GET | /api/v2/smart-meters/electricity/ean?ean=... | Resolve electricity EAN |
GET | /api/v2/smart-meters/gas/ean?ean=... | Resolve gas EAN |
Registry fields
Typical smart meter identity payload includes:
- Meter UUID (
identifier) - Address UUID
- Meter type
- Electricity and gas meter numbers
- Electricity and gas EANs (nullable when unknown)
- Created / updated timestamps
Readings and intervals
- Historical electricity and gas energy endpoints accept date-range filters.
- Latest endpoints are for current-snapshot workflows.
- Interval endpoints return aggregated series suitable for charts and reconciliation jobs.
- Forecast timestamps are expressed with Europe/Amsterdam offset semantics as documented on those operations.
Guidance
- Discover meters per address, then pull readings by meter UUID.
- Prefer incremental sync windows over large catch-up ranges.
- Treat delayed or backfilled metering data as normal in energy systems.
- Use EAN lookup for identity resolution workflows; still enforce your own access checks in downstream systems.
- Separate operational monitoring pipelines from billing-grade reconciliation pipelines.
Updated about 7 hours ago
Did this page help you?