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.

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. Unit: items. Through this API: default 25, maximum 100.
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=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.

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. Unit: items. Through this API: default 25, maximum 100.

Result

Source: Norwegian public correspondence journals. Retrieved 2026-11-19T12:40:21Z in 0.357 seconds.

total_hits:
5
returned:
5
capped:
no
total_capped:
no
documents:

5 results

  1. entity_name:
    Bane NOR SF
    entity_id:
    bane-nor
    case_title:
    Fullmakter for innhenting av opplysninger fra Skatteetaten
    case_serial_number:
    2018/5318
    document_id:
    2018/5318-4894
    document_type:
    Inngående brev
    document_title:
    SIEMENS MOBILITY LIMITED - 926830287 - Fullmakt for innhenting av opplysninger fra Skatteetaten
    document_date:
    2026-03-25
    recorded_date:
    2026-04-15
    from:

    1 results

    1. SIEMENS MOBILITY LIMITED
    to:

    No results.

    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/bane-nor/2018/5318
    files:

    No results.

  2. entity_name:
    Bane NOR SF
    entity_id:
    bane-nor
    case_title:
    Rammeavtale - VT1 sporfeltreleer Siemens
    case_serial_number:
    2021/9756
    document_id:
    2021/9756-3
    document_type:
    Inngående brev
    document_title:
    Tilbud - Avskjermet
    document_date:
    2023-06-26
    recorded_date:
    2023-06-26
    from:

    1 results

    1. Siemens Mobility Limited
    to:

    No results.

    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/bane-nor/2021/9756
    files:

    No results.

  3. entity_name:
    Statens jernbanetilsyn
    entity_id:
    statens-jernbanetilsyn
    case_title:
    Siemens Mobility GmbH - Temporary Authorisation for commercial test operation with software release E32.02
    case_serial_number:
    2022/1244
    document_id:
    2022/1244-18
    document_type:
    Utgående brev
    document_title:
    Time-limited authorisation to place in service vehicle type Vectron X4 for commercial traffic with ETCS and ATC2-STM on class B infrastructure
    document_date:
    2022-11-16
    recorded_date:
    2022-11-17
    from:

    1 results

    1. Tillatelser
    to:

    1 results

    1. Siemens Mobility GmbH
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      SIEMENS MOBILITY GMBH
      orgnummer:
      not reported by source
    case_url:
    https://norske-postlister.no/sak/statens-jernbanetilsyn/2022/1244
    files:

    No results.

  4. entity_name:
    Statens jernbanetilsyn
    entity_id:
    statens-jernbanetilsyn
    case_title:
    Siemens AS - Godkjenning av X4 lokomotiver i Norge
    case_serial_number:
    2019/162
    document_id:
    2019/162-25
    document_type:
    Inngående brev
    document_title:
    Application for time limited authorisation
    document_date:
    2021-08-20
    recorded_date:
    2021-08-20
    from:

    1 results

    1. Siemens Mobility GmbH
    to:

    No results.

    from_org:

    1 results

    1. navn:
      SIEMENS MOBILITY GMBH
      orgnummer:
      not reported by source
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/statens-jernbanetilsyn/2019/162
    files:

    No results.

  5. entity_name:
    Direktoratet for strålevern og atomsikkerhet
    entity_id:
    statens-stralevern
    case_title:
    Avtaler om tjenesteleveranser mellom Statens strålevern og Norsk Helsenett SF
    case_serial_number:
    2017/107
    document_id:
    2017/107-6
    document_type:
    Utgående brev
    document_title:
    Overføring av avtale til Norsk Helsenett SF
    document_date:
    2017-03-23
    recorded_date:
    2017-04-25
    from:

    No results.

    to:

    1 results

    1. Atea AS UNINETT AS Siemens Financial Services AB NUF Fenestrae B.V. Flexera Software Limited Xerox AS Tieto Norge AS Telïa Norge AS Telenor Norge AS TDC AS TCM AS Outpost 24 Link Mobility AS Ice Norge AS Every Norge AS Crayon AS Core Services AS Clue Norge AS
    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/statens-stralevern/2017/107
    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

  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.