Building cache coverage and source reconciliation
Whether the building and dwelling records held for the address match what the latest address snapshot says should exist, with counts of what is missing.
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: a separate agreement, switched on per account · Ask about an agreement
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
- Kartverket Matrikkel
- Declared redistribution
- Agreement terms apply
- Catalogue basis
- Separate agreement
Attribution and note
Shown from the contract in its original language.
Served under a separate agreement; its terms decide what may be shown or passed on.
API warnings
The API returns these notes in warnings.
- cache_only means source completeness is unverified. snapshot_consistent means all IDs from the last address snapshot exist in the cache, not that the source is current. Missing building records never prove the address has no building. Legacy counts describe historic address links, not necessarily the current snapshot.
Provider-contract fields
7 of 10 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 |
|---|---|---|
| fetched_at | string | null | context |
| building_ids | array<string> | null | context |
| dwelling_ids | array<string> | null | context |
| coverage_status | string | null | value |
| expected_building_count | integer | null | value |
| expected_dwelling_count | integer | null | value |
| missing_building_count | integer | null | value |
| missing_dwelling_count | integer | null | value |
| legacy_dwelling_count | integer | null | value |
| legacy_missing_building_count | integer | null | value |
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=building_source_status'
# 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/building_source_status?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.