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 25; 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=25&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=25&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. Through this API: default 25, maximum 100.
`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=25&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=25&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=25&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. Through this API: default 25, maximum 100.

Result

Source: Norwegian public correspondence journals. Retrieved 2026-11-02T21:07:34Z in 0.354 seconds.

total_hits:

returned:

capped:

total_capped:

documents:

4 results

entity_name:
Sykehuset Innlandet HF
entity_id:
helse-sykehuset-innlandet-hf
case_title:
200334 Rammeavtale på levering av kirurgisk bruddmateriell - Swemac Orthopaedics AB
case_serial_number:
2018/1672
document_id:
2018/1672-1
document_type:
Inngående brev
document_title:
Nye regionale avtaler på kirurgisk bruddmateriell
document_date:
2018-04-26
recorded_date:
2018-05-02
from:
1 results
1. Sykehusinnkjøp HF
to:
No results.
from_org:
1 results
1. navn:
  SYKEHUSINNKJØP HF
  orgnummer:
  916879067
to_org:
No results.
case_url:
https://norske-postlister.no/sak/helse-sykehuset-innlandet-hf/2018/1672
files:
No results.
entity_name:
Helse Bergen HF
entity_id:
helse-bergen
case_title:
Anskaffelse - Traumaprodukter til Helse Vest
case_serial_number:
2015/9818
document_id:
2015/9818-8
document_type:
Utgående brev
document_title:
Avlysning av konkurranse produktgruppe 2.5
document_date:
2015-08-31
recorded_date:
2015-09-03
from:
1 results
1. Helse Bergen HF
to:
6 results
1. Smith & Nephew AS
2. Biomet Norge AS
3. Depuy Synthes AS, Divisjon av Janssen-Cilag
4. SCP Orthopedics AS
5. Stryker Norge NUF
6. Swemac Orthopaedics AB
from_org:
1 results
1. navn:
  HELSE BERGEN HF
  orgnummer:
  983974724
to_org:
3 results
1. navn:
  SMITH & NEPHEW AS
  orgnummer:
  not reported by source
2. navn:
  BIOMET NORGE AS
  orgnummer:
  974345684
3. navn:
  SCP ORTHOPEDICS AS
  orgnummer:
  963795572
case_url:
https://norske-postlister.no/sak/helse-bergen/2015/9818
files:
No results.
entity_name:
Universitetssykehuset Nord-Norge HF
entity_id:
helse-unn
case_title:
Anskaffelse 01-13 - Osteosyntesemateriell
case_serial_number:
2013/2522
document_id:
2013/2522-4
document_type:
Utgående brev
document_title:
VEDR KONKURRANSE PÅ OSTEOSYNTESEMATERIELL, (SAK NR 01/13), OPPRETTHOLDELSE AVDISKVALIFISERING
document_date:
2013-06-26
recorded_date:
2013-06-27
from:
1 results
1. Universitetssykehuset Nord-Norge HF
to:
1 results
1. Swemac Orthopaedics AB
from_org:
1 results
1. navn:
  UNIVERSITETSSYKEHUSET NORD-NORGE HF
  orgnummer:
  983974899
to_org:
No results.
case_url:
https://norske-postlister.no/sak/helse-unn/2013/2522
files:
No results.
entity_name:
Universitetssykehuset Nord-Norge HF
entity_id:
helse-unn
case_title:
Anskaffelse 01-13 - Osteosyntesemateriell
case_serial_number:
2013/2522
document_id:
2013/2522-3
document_type:
Inngående brev
document_title:
Klage på vedtak, dat 130513 (mottatt i Mercell 18.6.13)
document_date:
2013-06-13
recorded_date:
2013-06-19
from:
1 results
1. Swemac Orthopaedics AB
to:
1 results
1. Universitetssykehuset Nord-Norge HF
from_org:
No results.
to_org:
1 results
1. navn:
  UNIVERSITETSSYKEHUSET NORD-NORGE HF
  orgnummer:
  983974899
case_url:
https://norske-postlister.no/sak/helse-unn/2013/2522
files:
No results.

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.