Grunnbok register-unit metadata
Cached production register-unit identifiers and cadastral references for the address. Access requires current customer-specific Grunnbok source review; this section does not return owner names or documents.
Status right now
Measured 29 Oct 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.
Available with: approved pilot customer and named section access
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
- unverified
- Declared redistribution
- Not established
- Catalogue basis
- Unverified
Attribution and note
Shown from the contract in its original language.
No public redistribution licence is asserted. Each customer needs current source-specific formal approval for the exact use.
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.
- Requires current source-specific formal review and a matching source-aware serving selection; a section grant alone cannot enable this projection.
- Only production-environment cached register-unit identifiers are returned. Owner/party data, rights, encumbrances, raw documents and personal JSON are excluded.
- Address linkage and cache coverage are incomplete. An absent row does not establish absence of an owner, property or legal right. last_fetched_at is collection time, not a legal effective date.
- Property identifiers may identify people indirectly; this projection is conservatively personal and does not establish a non-personal exception.
Provider-contract fields
1 of 9 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| address_id | string | null | context |
| environment | string | null | context |
| registerenhet_id | string | null | value |
| kommunenr | string | null | context |
| gardsnr | integer | null | context |
| bruksnr | integer | null | context |
| festenr | integer | null | context |
| seksjonsnr | integer | null | context |
| last_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=grunnbok_metadata'
# 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/grunnbok_metadata?limit=25'Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.