Municipal services and cached planning labels
Legacy section: kommune-level figures copied per address, such as property tax rate in promille, residents and number of businesses. Kept for existing integrations; verify fees with the kommune.
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
- unverified
- Declared redistribution
- Not established
- Catalogue basis
- Unverified
API warnings
The API returns these notes in warnings.
- Deprecated: kept for existing integrations. This is a per-address copy of kommune-level figures made by a collector that is not scheduled; the fee columns were blanked on 9 Sep 2026 after a mismatch with KOSTRA and are refilled only when someone runs it. Use municipal_fees (SSB 12842, annual water, sewage, waste and chimney-sweeping fees by kommune and year), population (head count), and local_businesses (registered businesses around the address) instead. There is no replacement yet for eiendomsskatt_promille.
- Cached values; verify current fees with the municipality. The plan labels this section once carried (reguleringsplan, kommuneplanens arealformål, hearings) were never filled by the enrichment; the plan_regulations section reads them live from the national plan base.
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. 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 |
|---|---|---|---|
| municipality_code | string | null | context | open |
| eiendomsskatt_promille | number | null | value | open |
| total_kommunale_avgifter_nok | number | null (NOK) | value | open |
| vann_avgift_nok | number | null (NOK) | value | open |
| avlop_avgift_nok | number | null (NOK) | value | open |
| renovasjon_avgift_nok | number | null (NOK) | value | open |
| innbyggere | integer | null | value | open |
| antall_virksomheter | integer | null | value | open |
| enriched_at | string | null | context | open |
| updated_at | string | null | context | open |
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=municipality_services'
# 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/municipality_services?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.