Energy certificates (energimerke) registered at the address
Energy certificates (energimerke) registered at the address, the latest per unit or building: energy grade, heating grade, delivered energy per square metre, issue date and validity. Grades from the pre-2026 and 2026 regimes are not comparable.
Status right now
Measured 22 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.
Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing
Source terms and reuse
These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.
- Declared licence or terms
- Norsk lisens for offentlige data 2.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- Stated in catalogue evidence
Attribution and note
Shown from the contract in its original language.
Inneholder data under norsk lisens for offentlige data (NLOD) tilgjengeliggjort av Enova Energimerkesystemet (data.enova.no) · NLOD
API warnings
The API returns these notes in warnings.
- The latest certificate Enova holds for each unit (bruksenhetsnummer) or building at the address; older certificates for the same unit are superseded. A certificate is valid for ten years from issued_date. No record means none is registered for this address or ours could not be tied to it — never that the building would score badly. Energy labelling has been mandatory at sale and rental since 2010, so owner-occupied homes that never changed hands often have none.
- Grades from the two regimes are NOT comparable: regulation 'pre_2026' is the old scheme (energy_grade on calculated delivered energy, heating_grade as Enova's colour, fossil_share); regulation '2026' is the new scheme (grade on weighted delivered energy in a reference climate, weighted_delivered_energy_kwh_m2, heated_area_m2, certificate_url). Simple registrations are made by the owner with Enova's calculator; Schema/Advanced by an energy adviser or professional system.
- address_match says how Enova's record was tied to this address: street_address (the certificate's own address and postal code), building (its bygningsnummer), or cadastral (its gnr/bnr on a parcel with a single address). Measured 28 Sep 2026 across all 1 859 038 certificates: 96.5 % tie to an address (98.0 % of those still valid, 99 % of those issued since 2023); the rest mostly predate address changes.
- data_updated_at is when the register was last synchronised with Enova (the daily refresh of the current and previous issue month), not when this certificate was issued or last re-read: a certificate older than two months keeps the fetched_at of the walk that loaded it, and the section is stale only when the daily refresh has stopped. Enova can withdraw or correct a certificate; that reaches us when its issue period is next refreshed in full.
Provider-contract fields
7 of 21 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” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| attestnummer | string | null | context | — |
| regulation | string | null | context | open |
| energy_grade | string | null | value | open |
| heating_grade | string | null | value | — |
| building_category | string | null | context | open |
| building_year | integer | null (årstall) | context | open |
| bygningsnummer | integer | null | context | — |
| bruksenhetsnummer | string | null | context | open |
| stated_area_m2 | number | null (m2) | context | — |
| heated_area_m2 | number | null (m2) | context | — |
| delivered_energy_kwh_m2 | number | null (m2) | value | — |
| weighted_delivered_energy_kwh_m2 | number | null (m2) | value | — |
| fossil_share | number | null (andel) | context | — |
| material | string | null | context | — |
| registration_type | string | null | context | — |
| issued_date | string | null | value | open |
| valid_until | string | null | value | open |
| is_valid | boolean | null | value | open |
| certificate_url | string | null | context | — |
| address_match | string | null | context | — |
| fetched_at | string | null | context | — |
Fetch this section
Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
-H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
'https://api.approach.no/api/v1/addresses/285717643?include=energy_certificate'
# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
-H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
'https://api.approach.no/api/v1/addresses/285717643/sections/energy_certificate?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.