Planning at and around the address: plan features, nearby plans and plan rules, with coverage
planning4 fieldsNot in the demo
Available with: bundle or agreed plan, subject to field policy and source grants · Pricing
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.
- Plans are indications to verify with the kommune, never a legal opinion. A part with status not_covered holds no register for the kommune: that is not the same as the address being unregulated.
- Each part keeps its own caveats; read them in the catalogue entries for zoning_plan_features, nearby_zoning_plans and plan_regulations.
Provider-contract fields
3 of 4 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 |
|---|---|---|
| zoning_plan_features | array<object> | null | value |
| nearby_zoning_plans | object | null | value |
| plan_regulations | array<object> | null | value |
| coverage | object | context |
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=planning'
# 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/planning?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.