Skip to content

← All sections

Official address and cadastral identifiers

Official address register record for the address: address type, cadastral and property unit, grunnkrets, electoral district, settlement name, the address point in UTM33 and WGS84, and an elevation with its stated source.

address_details14 fields6 of these fields open in the demo+ 7 open values outside the contract
Source
Kartverket address register
Geography
The address point
Reported stale after
7 days
Access
Requires an API key granted this section
Contract version
1
In packages
construction, core, home_profile, home_and_value

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
22 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured

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
Creative Commons Attribution 4.0
Declared redistribution
Allowed with attribution
Catalogue basis
Publisher terms
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

© Kartverket address register, CC BY 4.0

Where are the address fields in JSON?

Street, house number, postal area and coordinates are in address at the top of the authenticated profile response, for example address.street_name. The public demo also presents this open address identity as address_details. With full field policy, sections.address_details.records instead has a separate contract for cadastral identifiers and coordinates; do not expect all street and postal fields there.

imported_at is local import time, not proof of upstream freshness. Missing or null values do not mean the information is verified. Access and field policy still apply to each section.

API warnings

The API returns these notes in warnings.

  • Elevation uses the stated source. easting_utm33 and northing_utm33 are EPSG:25833 metres and authoritative; lat and lon are the same point in WGS84 degrees, derived from them and rounded to 6 decimals.
Public demo fields

The demo uses a separate public projection. This table describes it, not the full provider contract. A key or package does not itself grant additional fields.

FieldTypeRole
address_idstring | nullcontext
county_codestring | nullvalue
easting_utm33number | null (m)value
house_numberinteger | nullvalue
imported_atstring | nullcontext
latnumber | null (degrees)context
letterstring | nullcontext
lonnumber | null (degrees)context
municipality_codestring | nullvalue
northing_utm33number | null (m)value
postal_areastring | nullvalue
postal_codestring | nullvalue
street_namestring | nullvalue

Provider-contract fields

7 of 14 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.

FieldTypeRoleDemo
address_idstring | nullcontextopen
address_typestring | nullvalue—
cadastral_unitstring | nullvalue—
property_unitstring | nullvalue—
grunnkrets_idstring | nullvalue—
electoral_districtstring | nullvalue—
settlement_namestring | nullvalue—
easting_utm33number | null (m)contextopen
northing_utm33number | null (m)contextopen
latnumber | null (degrees)contextopen
lonnumber | null (degrees)contextopen
elevation_mnumber | null (m)value—
elevation_sourcestring | nullcontext—
imported_atstring | nullcontextopen

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=address_details'

# 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/address_details?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.