Electricity use in the municipality (Elhub)
electricity_consumption15 fields15 of these fields open in the demo
What this does not say
Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.
- Kommune totals from Elhub's open data, not this household's consumption: there is no public per-meter data. private_kwh_per_metering_point_12m is the kommune's private (household) kWh over the last twelve published months divided by the mean number of private metering points; one household can have several meters, a cabin kommune's private meters include cabins, and the figure reflects climate, heating mix and dwelling size together. Elhub publishes with about two weeks' lag and revises recent months.
- Months are calendar months in Norwegian time. Annual fields are null unless that consumer group has twelve consecutive full months with all expected hours (including daylight-saving changes). *_complete_months reports complete months per group; months_covered counts stored months across groups and does not prove annual coverage. Monthly ratios are null for incomplete months. The Norway comparison requires complete private periods for every municipality represented in the stored window; an entirely absent municipality cannot be detected from this source snapshot. fetched_at is the oldest contributing import time. period_end is the latest stored month.
Fields
6 of 15 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” return values to anonymous callers; the rest require a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| municipality_code | string | null | context | open |
| period_start | date | null | context | open |
| period_end | date | null | context | open |
| months_covered | integer | null | context | open |
| private_complete_months | integer | null | context | open |
| business_complete_months | integer | null | context | open |
| industry_complete_months | integer | null | context | open |
| private_kwh_12m | number | null (kWh) | value | open |
| private_metering_points | number | null | value | open |
| private_kwh_per_metering_point_12m | number | null | value | open |
| norway_private_kwh_per_metering_point_12m | number | null | context | open |
| business_kwh_12m | number | null (kWh) | value | open |
| industry_kwh_12m | number | null (kWh) | value | open |
| private_monthly_kwh_per_metering_point | array<object> | null | value | open |
| fetched_at | timestamp | null | context | open |
Fetch this section
curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643?include=electricity_consumption" # paginated, one section at a time curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643/sections/electricity_consumption?limit=25"
Try it now
This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.