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-09-23T14:41:47Z in 0.255 seconds.

total_hits:
7
returned:
7
capped:
no
documents:

7 results

  1. entity_name:
    Nasjonal kommunikasjonsmyndighet
    entity_id:
    nasjonal-kommunikasjonsmyndighet
    case_title:
    Valdres Teledata AS - ENA
    case_serial_number:
    2015/4861
    document_id:
    2015/4861-2
    document_type:
    Utgående brev
    document_title:
    ENA - innvilget autorisasjon - 6023
    document_date:
    2015-10-09
    recorded_date:
    2015-10-09
    from:

    No results.

    to:

    1 results

    1. Valdres TeleData AS
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      VALDRES TELEDATA AS
      orgnummer:
      982812976
    case_url:
    https://norske-postlister.no/sak/nasjonal-kommunikasjonsmyndighet/2015/4861
    files:

    No results.

  2. entity_name:
    Nasjonal kommunikasjonsmyndighet
    entity_id:
    nasjonal-kommunikasjonsmyndighet
    case_title:
    Valdres Teledata AS - ENA
    case_serial_number:
    2015/4861
    document_id:
    2015/4861-1
    document_type:
    Inngående brev
    document_title:
    ENA - søknad om autorisasjon - XXXX-NAME-XXXX
    document_date:
    2015-09-03
    recorded_date:
    2015-09-03
    from:

    1 results

    1. Valdres TeleData AS
    to:

    No results.

    from_org:

    1 results

    1. navn:
      VALDRES TELEDATA AS
      orgnummer:
      982812976
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/nasjonal-kommunikasjonsmyndighet/2015/4861
    files:

    No results.

  3. entity_name:
    Nasjonal kommunikasjonsmyndighet
    entity_id:
    nasjonal-kommunikasjonsmyndighet
    case_title:
    Valdres TeleData AS - TIA
    case_serial_number:
    2013/2514
    document_id:
    2013/2514-1
    document_type:
    Utgående brev
    document_title:
    TIA - videreføring av autorisasjon - 6023
    document_date:
    2013-05-04
    recorded_date:
    2013-05-14
    from:

    No results.

    to:

    1 results

    1. Valdres TeleData AS
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      VALDRES TELEDATA AS
      orgnummer:
      982812976
    case_url:
    https://norske-postlister.no/sak/nasjonal-kommunikasjonsmyndighet/2013/2514
    files:

    No results.

  4. entity_name:
    Sør-Aurdal kommune
    entity_id:
    0540-sor-aurdal-kommune
    case_title:
    Trådløse aksesspunkt Tingvoll
    case_serial_number:
    2012/292
    document_id:
    2012/1785-100000002012001785
    document_type:
    Utgående brev
    document_title:
    Vedr. montering av trådløse aksesspunkt på Tingvoll
    document_date:
    2012-03-02
    recorded_date:
    2012-03-02
    from:

    No results.

    to:

    1 results

    1. Valdres Teledata
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      VALDRES TELEDATA AS
      orgnummer:
      982812976
    case_url:
    https://norske-postlister.no/sak/0540-sor-aurdal-kommune/2012/1785
    files:

    No results.

  5. entity_name:
    Nord-Aurdal kommune
    entity_id:
    0542-nord-aurdal-kommune
    case_title:
    Telefoniløsning til Valdreskommunene
    case_serial_number:
    2011/2007
    document_id:
    2011/11168-100000002011011168
    document_type:
    Inngående brev
    document_title:
    Valdres Teledata - Protokoll for anskaffelse
    document_date:
    2011-10-12
    recorded_date:
    2011-11-24
    from:

    1 results

    1. Valdres Teledata AS
    to:

    No results.

    from_org:

    1 results

    1. navn:
      VALDRES TELEDATA AS
      orgnummer:
      982812976
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/0542-nord-aurdal-kommune/2011/11168
    files:

    No results.

  6. entity_name:
    Sør-Aurdal kommune
    entity_id:
    0540-sor-aurdal-kommune
    case_title:
    Telefonitjenester
    case_serial_number:
    2010/134
    document_id:
    2010/4678-100000002010004678
    document_type:
    Inngående brev
    document_title:
    Tilbud på ny telefonsentral
    document_date:
    2010-07-07
    recorded_date:
    2010-07-07
    from:

    1 results

    1. Valdres Teledata
    to:

    No results.

    from_org:

    1 results

    1. navn:
      VALDRES TELEDATA AS
      orgnummer:
      982812976
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/0540-sor-aurdal-kommune/2010/4678
    files:

    No results.

  7. entity_name:
    Sør-Aurdal kommune
    entity_id:
    0540-sor-aurdal-kommune
    case_title:
    Telefonitjenester
    case_serial_number:
    2010/134
    document_id:
    2010/4714-100000002010004714
    document_type:
    Utgående brev
    document_title:
    Vedr. tilbud på ny telefonsentral
    document_date:
    2010-07-07
    recorded_date:
    2010-07-07
    from:

    No results.

    to:

    1 results

    1. Valdres Teledata
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      VALDRES TELEDATA AS
      orgnummer:
      982812976
    case_url:
    https://norske-postlister.no/sak/0540-sor-aurdal-kommune/2010/4714
    files:

    No results.

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