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-27T08:38:43Z in 0.575 seconds.

total_hits:
2
returned:
2
capped:
no
documents:

2 results

  1. entity_name:
    Direktoratet for e-helse
    entity_id:
    dir-ehelse
    case_title:
    PKT - Prosjekt kodeverk - Delprosjekt prosedyrekodeverk for patologi (PKPAT)
    case_serial_number:
    2017/637
    document_id:
    2017/637-14
    document_type:
    Utgående brev
    document_title:
    Informasjon om nye koder for aktivitetsregistrering i patologilaboratorier (9-månedersvarsel)
    document_date:
    2019-03-07
    recorded_date:
    2019-03-08
    from:

    No results.

    to:

    9 results

    1. Helse Vest RHF
    2. Helse Midt-Norge RHF
    3. Helse Sør-Øst RHF
    4. Helse Nord RHF
    5. Dr Fürst medisinsk laboratorium AS
    6. Tieto Norway AS
    7. Alphasoft GmbH
    8. Software Point Norway
    9. Alphasoft GmbH
    from_org:

    No results.

    to_org:

    7 results

    1. navn:
      HELSE VEST RHF
      orgnummer:
      983658725
    2. navn:
      HELSE MIDT-NORGE RHF
      orgnummer:
      983658776
    3. navn:
      HELSE SØR-ØST RHF
      orgnummer:
      991324968
    4. navn:
      HELSE NORD RHF
      orgnummer:
      883658752
    5. navn:
      DR FURST MEDISINSK LABORATORIUM AS
      orgnummer:
      not reported by source
    6. navn:
      TIETO NORWAY AS
      orgnummer:
      821530792
    7. navn:
      SOFTWARE POINT NORWAY
      orgnummer:
      999178650
    case_url:
    https://norske-postlister.no/sak/dir-ehelse/2017/637
    files:

    No results.

  2. entity_name:
    Oslo universitetssykehus HF
    entity_id:
    helse-oslo-universitetssykehus-hf
    case_title:
    Alphasoft databehandleravtale IKT systemer OUS/KLM/MBK
    case_serial_number:
    2018/21848
    document_id:
    2018/21848-1
    document_type:
    Inngående brev
    document_title:
    OUS Account - Remote access agreement - XXXX-NAME-XXXX
    document_date:
    not reported by source
    recorded_date:
    2018-11-12
    from:

    1 results

    1. Alphasoft GMBH
    to:

    No results.

    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/helse-oslo-universitetssykehus-hf/2018/21848
    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.