Public case-journal entries naming the cadastral unit
Public eInnsyn journal entries with case type, document type, date and source link. A match requires the title to identify the property by cadastral numbers and the municipality to be identifiable.
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
API warnings
The API returns these notes in warnings.
- Coverage depends on each kommune and agency publishing its post journal to eInnsyn, and on the entry's title naming the gnr/bnr; many titles omit that identifier, so those entries cannot match the address. Entries from the last 24 months, newest first, at most 50. Matching is on gnr/bnr within the kommune; feste and section numbers are not matched.
- matter_type is parsed from the journal title into a fixed vocabulary (tinglysing, riving, deling, dispensasjon, regulering, nabovarsel, rammetillatelse, igangsetting, ferdigattest, tilbygg, other) and can be wrong; open url for the entry itself. No title, party or other free text is stored or served. municipality_source says how the kommune was found (knr or kommune name in the title, the journal unit's own kommune, or an unambiguous bare name).
Provider-contract fields
3 of 13 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 |
|---|---|---|
| journalpost_id | string | null | context |
| journal_date | string | null | value |
| matter_type | string | null | value |
| document_type | string | null | value |
| municipality_code | string | null | context |
| gnr | integer | null | context |
| bnr | integer | null | context |
| fnr | integer | null | context |
| snr | integer | null | context |
| url | string | null | context |
| municipality_source | string | null | context |
| published_at | 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=case_journal'
# 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/case_journal?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.