Plan rules at the address: zoning purpose and utilisation, hensynssoner, kommuneplan
Legacy section: the plan rules at the address point from DiBK's national plan base: zoning purpose, utilisation, height, hensynssoner and the kommuneplan, with the plan identity and status. It carries what the plan map says, not the written provisions, and is kept for existing integrations.
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
Attribution and note
Shown from the contract in its original language.
DiBK NAP plan register (Norge digitalt): reuse terms for customers not confirmed. Pending legal review.
API warnings
The API returns these notes in warnings.
- Deprecated: use the planning section, which carries this section's records together with the other plan sections' and a coverage block saying, per part, whether the kommune is covered. Kept for existing integrations; stops answering on 15 Apr 2027 (the Sunset header carries the date).
- Legacy scalar plan fields select one source report for compatibility, not the governing plan. Read reported_plan_candidates for every plan-area report returned by the bounded point query; omitted source features, unknown identities and partial source failures remain gaps.
- Read live from DiBK's national plan base at the address point, so it carries what the kommune has published to NAP. A kommune outside NAP (Oslo publishes to its own register, not to NAP) is answered from the municipal plan register we ingest instead, and source_system says which answered; where we have neither, no match is not the same as no plan. The plan text (bestemmelser) is not in NAP: utilisation, heights and hensynssoner here are what the plan map carries, and the written provisions can add to or override them.
- Which rules apply, not whether the building meets them: no open register records compliance, and an existing building is judged by the permit it was built under.
Provider-contract fields
8 of 28 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 |
|---|---|---|---|
| zoning_plan_id | string | null | context | — |
| zoning_plan_name | string | null | value | open |
| zoning_plan_type_name | string | null | context | open |
| zoning_plan_status_name | string | null | context | open |
| zoning_in_force_date | string | null | context | open |
| zoning_purpose_code | string | null | context | open |
| zoning_purpose_name | string | null | value | open |
| zoning_utilisation_type | string | null | context | — |
| zoning_utilisation_type_name | string | null | context | open |
| zoning_plan_field | string | null | context | open |
| zoning_utilisation_value | number | null | value | open |
| zoning_utilisation_text | string | null | context | open |
| zoning_max_height_m | number | null (m) | context | open |
| zoning_hensynssoner | array<object> | value | open |
| zoning_provisions | array<object> | context | open |
| kommuneplan_id | string | null | context | — |
| kommuneplan_name | string | null | value | open |
| kommuneplan_in_force_date | string | null | context | open |
| kommuneplan_purpose_code | string | null | context | open |
| kommuneplan_purpose_name | string | null | value | open |
| kommuneplan_arealbruksstatus | string | null | context | open |
| kommuneplan_hensynssoner | array<object> | value | open |
| kommuneplan_provisions | array<object> | context | open |
| reported_plan_candidates | array<object> | context | — |
| source_system | string | context | open |
| updated_at | string | null | context | open |
| retrieved_at | date-time | context | — |
| utilization | object (percent) | 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=plan_regulations'
# 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/plan_regulations?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.