search

Search Norwegian public mail journals (postlister).

Signature: search(query: string, optional, default '*'; entity_id: string, optional, default None; date_from: string, optional, default None; date_to: string, optional, default None; limit: integer, items, optional, default 20; offset: integer, items, optional, default 0)

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

Open this validated HTML GET URL

https://allemannsdata.com/wiki/kilder/postlister/search/?query=%2A&entity_id={entity_id}&date_from={date_from}&date_to={date_to}&limit=20&offset=0

Replace {query}, {entity_id}, {date_from}, {date_to}, {limit} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/postlister/search?query=%2A&entity_id={entity_id}&date_from={date_from}&date_to={date_to}&limit=20&offset=0. Open this exact request as JSON.

Parameter	Requirement	JSON type	Description
`query`	optional	string	Lucene query-string over all fields. A bare word searches everything (e.g. "Equinor", "byggesak"). Field-scoped and range queries work too, e.g. `document_title:skole`, `document_type:"Inngående brev"`, `document_from_org.orgnummer:923609016`. Default "*" matches everything (combine with filters).
`entity_id`	optional	union	Restrict to one authority, e.g. "2012-alta-kommune". Read it off `entity_id` in earlier results.
`date_from`	optional	union	Document-date lower bound, ISO "YYYY-MM-DD" (inclusive).
`date_to`	optional	union	Document-date upper bound, ISO "YYYY-MM-DD" (inclusive).
`limit`	optional	integer	Max documents to return, 1 to 100 (default 20). Unit: items.
`offset`	optional	integer	Number of list items to skip; default 0.

Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/postlister/search?query=%2A&entity_id={entity_id}&date_from={date_from}&date_to={date_to}&limit=20&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/postlister/search?query=%2A&entity_id={entity_id}&date_from={date_from}&date_to={date_to}&limit=20&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/postlister/search?query=%2A&entity_id={entity_id}&date_from={date_from}&date_to={date_to}&limit=20&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "postlister",
  "operation": "search",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}

Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

query Type: string. Lucene query-string over all fields. A bare word searches everything (e.g. "Equinor", "byggesak"). Field-scoped and range queries work too, e.g. `document_title:skole`, `document_type:"Inngående brev"`, `document_from_org.orgnummer:923609016`. Default "*" matches everything (combine with filters).

entity_id Type: string. Restrict to one authority, e.g. "2012-alta-kommune". Read it off `entity_id` in earlier results.

date_from Type: string. Document-date lower bound, ISO "YYYY-MM-DD" (inclusive).

date_to Type: string. Document-date upper bound, ISO "YYYY-MM-DD" (inclusive).

limit Type: integer. Max documents to return, 1 to 100 (default 20). Unit: items.

Result

Source: Norwegian public correspondence journals. Retrieved 2026-09-27T06:38:29Z in 0.386 seconds.

total_hits:

returned:

capped:

documents:

8 results

entity_name:
Vestland fylkeskommune
entity_id:
vestland-fylkeskommune
case_title:
Falloddsmålinger Vestland 2025
case_serial_number:
2025/38754
document_id:
2025/38754-18
document_type:
Internt notat uten oppfølging
document_title:
Tilbud Safe Controll Road AS
document_date:
2025-06-18
recorded_date:
2025-06-19
from:
No results.
to:
No results.
from_org:
No results.
to_org:
No results.
case_url:
https://norske-postlister.no/sak/vestland-fylkeskommune/2025/38754
files:
10 results
1. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
2. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
3. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
4. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
5. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
6. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
7. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
8. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
9. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
10. title:
 Dokumentet er ikke tilgjengelig
 url:
 not reported by source
entity_name:
Roan kommune
entity_id:
5019-roan-kommune
case_title:
Asfaltering av kommunale veier 2019
case_serial_number:
2019/133
document_id:
2019/133-7
document_type:
Inngående brev
document_title:
Rapport - Bæreevnemåling med Fallodd
document_date:
2019-06-04
recorded_date:
2019-06-04
from:
1 results
1. Safe Controll Road AS
to:
No results.
from_org:
No results.
to_org:
No results.
case_url:
https://norske-postlister.no/sak/5019-roan-kommune/2019/133
files:
No results.
entity_name:
Nærøy kommune
entity_id:
5051-naeroy-kommune
case_title:
Vedlikehold av kommunale veger
case_serial_number:
2008/1379
document_id:
2008/1379-29
document_type:
Inngående brev
document_title:
Safe Controll Road As - bæreevnemåling av veger 2017
document_date:
2017-05-21
recorded_date:
2017-05-22
from:
1 results
1. Safe Control Road AS
to:
No results.
from_org:
1 results
1. navn:
  SAFE CONTROL ROAD AS
  orgnummer:
  918900551
to_org:
No results.
case_url:
https://norske-postlister.no/sak/5051-naeroy-kommune/2008/1379
files:
No results.
entity_name:
Ålesund kommune
entity_id:
1504-alesund-kommune
case_title:
Anskaffelse - Datainnhenting og rådgivningstjenester - Kommunalteknisk, 2026
case_serial_number:
2025/11622
document_id:
2025/11622-20260042113
document_type:
Utgående brev
document_title:
Tildelingsbeslutning
document_date:
not reported by source
recorded_date:
2026-05-06
from:
No results.
to:
8 results
1. AFRY NORWAY AS
2. Asplan Viak AS
3. Field Geospatial AS
4. HRP AS
5. Multiconsult Norge AS
6. Oppmålingstjenester as
7. Safe Controll Road AS
8. Sweco Asset MAnagement Technologies AS
from_org:
No results.
to_org:
3 results
1. navn:
 ASPLAN VIAK AS
 orgnummer:
 910209205
2. navn:
 HRP AS
 orgnummer:
 818056222
3. navn:
 MULTICONSULT NORGE AS
 orgnummer:
 918836519
case_url:
https://norske-postlister.no/sak/1504-alesund-kommune/2025/11622
files:
1 results
1. title:
 1 fil som ikkje er publisert.
 url:
 not reported by source
entity_name:
Ålesund kommune
entity_id:
1504-alesund-kommune
case_title:
Anskaffelse - Datainnhenting og rådgivningstjenester for kommunaltekniske områder 2023
case_serial_number:
2025/16409
document_id:
2025/16409-20250127617
document_type:
Utgående brev
document_title:
Prolongering av avtale
document_date:
not reported by source
recorded_date:
2025-11-06
from:
No results.
to:
1 results
1. Safe Controll Road AS
from_org:
No results.
to_org:
No results.
case_url:
https://norske-postlister.no/sak/1504-alesund-kommune/2025/16409
files:
1 results
1. title:
 1 fil som ikkje er publisert.
 url:
 not reported by source
entity_name:
Heim kommune
entity_id:
5055-heim-kommune
case_title:
ANSKAFFELSE PÅ UTARBEIDELSE AV STATEGISK HOVEDPLAN VEG.
case_serial_number:
2022/2728
document_id:
2022/2728-4
document_type:
Inngående brev
document_title:
Tilbudsbrev Utarbeidelse av strategisk hovedplan veg for Heim kommune
document_date:
not reported by source
recorded_date:
2022-06-29
from:
1 results
1. SAFE CONTROLL ROAD AS
to:
No results.
from_org:
No results.
to_org:
No results.
case_url:
https://norske-postlister.no/sak/5055-heim-kommune/2022/2728
files:
No results.
entity_name:
Heim kommune
entity_id:
5055-heim-kommune
case_title:
ANSKAFFELSE PÅ UTARBEIDELSE AV STATEGISK HOVEDPLAN VEG.
case_serial_number:
2022/2728
document_id:
2022/2728-5
document_type:
Inngående brev
document_title:
Referanseliste hovedplan 2016-2021.
document_date:
not reported by source
recorded_date:
2022-06-29
from:
1 results
1. SAFE CONTROLL ROAD AS
to:
No results.
from_org:
No results.
to_org:
No results.
case_url:
https://norske-postlister.no/sak/5055-heim-kommune/2022/2728
files:
No results.
entity_name:
Heim kommune
entity_id:
5055-heim-kommune
case_title:
ANSKAFFELSE PÅ UTARBEIDELSE AV STATEGISK HOVEDPLAN VEG.
case_serial_number:
2022/2728
document_id:
2022/2728-6
document_type:
Inngående brev
document_title:
Eksempel Hovedplan veg 2020 - 2027 Hemsedal kommune
document_date:
not reported by source
recorded_date:
2022-06-29
from:
1 results
1. SAFE CONTROLL ROAD AS
to:
No results.
from_org:
No results.
to_org:
No results.
case_url:
https://norske-postlister.no/sak/5055-heim-kommune/2022/2728
files:
No results.

limit:

offset:

has_more_results:

truncated:

Will you use the result in generated code?

Open the same result as JSON

Is data missing or incorrect? Send feedback about this result.

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the search lookup

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.

AI agent? Read the complete navigation and programming guide.