Energy
Energy endpoints provide address-level P4 aggregates for electricity and gas at fixed resolutions. Use these when you need normalized premise-level series rather than device-specific meter detail.
Base path: /api/v2/addresses/:address_uuid
Permission: READ_ENERGY_DATA
What we provide
| Method | Path | Purpose |
|---|---|---|
GET | /electricity/p4/15min | Electricity P4 at 15-minute resolution |
GET | /electricity/p4/1day | Electricity P4 at daily resolution |
GET | /electricity/p4/1month | Electricity P4 at monthly resolution |
GET | /gas/p4/15min | Gas P4 at 15-minute resolution |
GET | /gas/p4/1day | Gas P4 at daily resolution |
GET | /gas/p4/1month | Gas P4 at monthly resolution |
Query parameters include date-range filters; see OpenAPI for the exact P4ReadingQuery shape per route.
When to use Energy vs Smart meters
| Need | Prefer |
|---|---|
| Address-level standardized P4 reporting | Energy |
| Meter identity, EANs, raw/latest meter points, meter forecasts | Smart meters |
| Device production (solar) or EV charge consumption | Device-specific domains |
Guidance
- Choose the coarsest resolution that still answers the business question.
- Keep date windows narrow for interactive dashboards; widen only in batch jobs.
- Persist timezone handling explicitly in your analytics layer.
- Combine with group address discovery when building portfolio reports.
Updated about 7 hours ago
Did this page help you?