Zoning plans covering the address point

zoning_plan16 fields15 of these fields open in the demo

Source: Municipal planregister ingest, DiBK national plan base (NAP) live at the point
Geography: The address point
Reported stale after: 90 days
Access: Requires an API key granted this section
Contract version: 1
In packages: planning_restrictions

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.

Point-in-polygon lookup against ingested plan geometries (currently Oslo), with a live lookup in DiBK's national plan base (NAP) at the point everywhere else. No match never means the address is unregulated: a kommune that has not published to NAP answers nothing. Verify the legally binding plan and provisions via plan_register_url/provisions_url.
Overlapping plans, including kommunedelplaner and different vertical levels, can all apply to the same point; plan_status can be empty in the source register.
Where no ingested polygon covers the point, the plan is read live from DiBK's national plan base (NAP) WMS at the address point and marked source_system dibk-nap-wms; NAP carries what the kommune has published to it, so a kommune outside NAP still answers no match.

Fields

6 of 16 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” return values to anonymous callers; the rest require a key.

Field	Type	Role	Demo
plan_id	string \| null	context	open
national_plan_id	string \| null	context	open
municipality_code	string \| null	context	open
plan_name	string \| null	value	open
plan_name_short	string \| null	context	open
plan_type	string \| null	value	open
plan_type_name	string \| null	context	open
plan_status	string \| null	value	open
adopted_date	string \| null	value	open
in_force_date	string \| null	value	open
vertical_level	integer \| null	context	open
provisions_code	string \| null	context	—
provisions_url	string \| null	value	open
plan_register_url	string \| null	context	open
source_system	string \| null	context	open
updated_at	string \| null	context	open

Fetch this section

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

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643/sections/zoning_plan?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.