Building cache coverage and source reconciliation

building_source_status10 fieldsNot in the demo

Source: Matrikkel ingestion
Geography: The address point
Reported stale after: 30 days
Access: agreement
Contract version: 1
In packages: home_profile

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.

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.

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

curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643?include=building_source_status"

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "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.