Permitted, started and completed buildings within 250 m and 500 m of the address

nearby_building_permits10 fields10 of these fields open in the demo

Source: Kartverket Matrikkelen bygningspunkt (CC BY 4.0)
Geography: Around the address
Reported stale after: 30 days
Access: Requires an API key granted this section
Contract version: 1

Available with: trial key (open fields) · bought bundle or agreed plan (all fields) · 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.

National: every kommune the bygningspunkt layer holds (GET /coverage, source nearby_building_permits); null where it holds nothing for the kommune (buildings_covered). A building keeps its status until the next one is registered, so an old rammetillatelse or igangsettingstillatelse can be a project that stalled rather than one actively under way, and status_changed_at is Kartverket's last record update, not a dated rammetillatelse/igangsettingstillatelse/ferdigattest — that history is not held anywhere in this database (see the file header for why). Five statuses are served: RA rammetillatelse, IG igangsettingstillatelse, MB midlertidig brukstillatelse, FA ferdigattest, TB tatt i bruk; others exist in the source and are not served because this codebase has no reviewed meaning for them. The list is nearest first, at most 100 buildings; the counts cover every building in the ring.
No applicant, tiltakshaver or other person is served or held by this table. bygningsnummer and bygningstype_kode/bygningstype_name identify the building and its use, not a person.

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

Field	Type	Role	Demo
municipality_code	string \| null	context	open
buildings_covered	boolean \| null	context	open
permits_within_250m	integer \| null	value	open
permits_within_500m	integer \| null	value	open
approved_within_500m	integer \| null	value	open
started_within_500m	integer \| null	value	open
completed_within_500m	integer \| null	value	open
permits	array<object> \| null	value	open
permits_listed	integer \| null	value	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 --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=nearby_building_permits'

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