Building applications on the same cadastral unit
Building cases from municipal archives and eInnsyn, matched to the address by municipality and cadastral unit numbers. Each record includes case type, measure type, status, dates and the basis for the status.
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: 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
Check coverage
The coverage report lists municipalities with stored cases and the dates spanned by the data. Filter by municipality code, such as 4601 for Bergen. See Bergen coverage (JSON)
When the section returns not_found, the imported sources contained no match for the municipality and parcel numbers. Check the municipal archive for older cases or a full record. Matches cover the whole parcel, including properties shared by several addresses or units.
Interpret the status and date
portal_reported_unverifiedcarries the status shown by the municipal portal at collection. Withportal_reportedthe registration date comes from the portal.title_direction_inferencemeans the status was inferred from the journal title and whether the document was incoming or outgoing. Withearliest_observed_publicationthe registration date is the earliest journal activity we observed. Use source_url to find the decision or completion certificate.
Example eInnsyn record
Abbreviated excerpt from sections.building_applications with a fictional case and parcel. The categories point to outline permission and an extension. Check the decision before relying on approved.
{
"status": "available",
"records": [
{
"municipality_code": "4601",
"gnr": 12,
"bnr": 34,
"saksnummer": "2026/12345",
"case_type": "rammetillatelse",
"measure_type": "tilbygg_pabygg",
"source_archive": "einnsyn_kommune",
"status": "approved",
"status_basis": "title_direction_inference",
"registrert_dato": "2026-08-11",
"registered_date_basis": "earliest_observed_publication"
}
]
}API warnings
The API returns these notes in warnings.
- Coverage varies by municipality, archive and date. GET /api/v1/addresses/coverage?source=building_applications reports municipalities with stored records. A not_found status means the imported sources contained no match for the municipality and gnr/bnr. Check the municipal archive for a fuller case history. eInnsyn cases are kept for 12 months after their last recorded activity. Matching ignores feste and section numbers. Oslo eInnsyn records come from that separate journal feed; the retired, unlicensed direct PBE saksinnsyn scrape is excluded.
- No applicant, tiltakshaver, ansvarlig søker or other person is served, and no case title or free-text address: case_type (the procedural step) and measure_type (what is built or changed) are a fixed vocabulary read from the title, the same as building_cases_nearby, and can be wrong or other.
- Municipal archive status reflects the portal at import time. eInnsyn status is inferred from journal titles and document direction, not a verified approval, completion or current legal effect; verify the current case via source_url. For eInnsyn, registrert_dato is the earliest observed publication/activity date, not a decision date.
- status_basis is portal_reported_unverified for municipal archives or title_direction_inference for eInnsyn. registered_date_basis is portal_reported or earliest_observed_publication respectively. These describe evidence interpretation, not independent verification, completeness or current legal effect; missing dates/status stay unknown.
Provider-contract fields
7 of 18 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 |
|---|---|---|
| municipality_code | string | null | context |
| saksnummer | string | null | value |
| case_type | string | null | value |
| measure_type | string | null | value |
| sakstype | string | null | value |
| tiltakstype | string | null | value |
| status | string | null | value |
| gnr | integer | null | context |
| bnr | integer | null | context |
| fnr | integer | null | context |
| snr | integer | null | context |
| registrert_dato | string | null | value |
| oppdatert_dato | string | null | context |
| source_url | string | null | context |
| source_archive | string | null | context |
| status_basis | string | null | context |
| registered_date_basis | string | null | context |
| updated_at | string | null | 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=building_applications'
# 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/building_applications?limit=25'Run the examples with an API key that has access to building cases.