Allemannsdata Wiki
Manual search

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.

ParameterRequirementJSON typeDescription
queryoptionalstringLucene 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_idoptionalunionRestrict to one authority, e.g. "2012-alta-kommune". Read it off `entity_id` in earlier results.
date_fromoptionalunionDocument-date lower bound, ISO "YYYY-MM-DD" (inclusive).
date_tooptionalunionDocument-date upper bound, ISO "YYYY-MM-DD" (inclusive).
limitoptionalintegerMax documents to return, 1 to 100 (default 20). Unit: items.
offsetoptionalintegerNumber 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.

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).
Type: string. Restrict to one authority, e.g. "2012-alta-kommune". Read it off `entity_id` in earlier results.
Type: string. Document-date lower bound, ISO "YYYY-MM-DD" (inclusive).
Type: string. Document-date upper bound, ISO "YYYY-MM-DD" (inclusive).
Type: integer. Max documents to return, 1 to 100 (default 20). Unit: items.

Result

Source: Norwegian public correspondence journals. Retrieved 2026-10-27T10:55:11Z in 0.447 seconds.

total_hits:
5
returned:
5
capped:
no
documents:

5 results

  1. entity_name:
    Folkehelseinstituttet
    entity_id:
    folkehelseinstituttet
    case_title:
    Koronavirus (Covid-19) og henvendelser fra bedrifter og foreninger - 2. halvår 2020 - Samlesak
    case_serial_number:
    2020/12511
    document_id:
    2020/12511-665
    document_type:
    Utgående brev
    document_title:
    Svar - En fråga om karantänsregler vid inresa till Norge från Sverige
    document_date:
    2020-09-01
    recorded_date:
    2020-09-15
    from:

    No results.

    to:

    1 results

    1. Swedavia AB
    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/folkehelseinstituttet/2020/12511
    files:

    No results.

  2. entity_name:
    Folkehelseinstituttet
    entity_id:
    folkehelseinstituttet
    case_title:
    Koronavirus (Covid-19) og henvendelser fra bedrifter og foreninger - 2. halvår 2020 - Samlesak
    case_serial_number:
    2020/12511
    document_id:
    2020/12511-617
    document_type:
    Inngående brev
    document_title:
    En fråga om karantänsregler vid inresa till Norge från Sverige
    document_date:
    2020-08-28
    recorded_date:
    2020-08-28
    from:

    1 results

    1. Swedavia AB
    to:

    No results.

    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/folkehelseinstituttet/2020/12511
    files:

    No results.

  3. entity_name:
    Riksrevisjonen
    entity_id:
    riksrevisjonen
    case_title:
    Undersøkelse av lønnsomhet og kostnadseffektivitet i Avinor AS
    case_serial_number:
    2017/01119
    document_id:
    2017/1119-54
    document_type:
    Inngående brev
    document_title:
    Svar vedrørende Swedavia AB
    document_date:
    2017-12-15
    recorded_date:
    2017-12-18
    from:

    1 results

    1. RIKSREVISJONEN SVERIGE
    to:

    No results.

    from_org:

    1 results

    1. navn:
      not reported by source
      orgnummer:
      999670016
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/riksrevisjonen/2017/1119
    files:

    No results.

  4. entity_name:
    Riksrevisjonen
    entity_id:
    riksrevisjonen
    case_title:
    Undersøkelse av lønnsomhet og kostnadseffektivitet i Avinor AS
    case_serial_number:
    2017/01119
    document_id:
    2017/1119-39
    document_type:
    Utgående brev
    document_title:
    Epost til svenske Riksrevisjonen om Swedavia AB
    document_date:
    2017-11-23
    recorded_date:
    2017-11-29
    from:

    No results.

    to:

    1 results

    1. RIKSREVISJONEN SVERIGE
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      not reported by source
      orgnummer:
      999670016
    case_url:
    https://norske-postlister.no/sak/riksrevisjonen/2017/1119
    files:

    No results.

  5. entity_name:
    Samferdselsdepartementet
    entity_id:
    dep-samferdsel
    case_title:
    Benchmarking av Avinor - hovudprosjekt
    case_serial_number:
    2010/2013
    document_id:
    2010/2013-40
    document_type:
    Inngående brev
    document_title:
    Svar på forespørsel om medvirkning til benchmarking-studie
    document_date:
    2011-11-14
    recorded_date:
    2011-11-22
    from:

    1 results

    1. Swedavia AB
    to:

    No results.

    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/dep-samferdsel/2010/2013
    files:

    No results.

limit:
25
offset:
0
has_more_results:
no
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

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. 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.