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-21T00:11:20Z in 0.279 seconds.

total_hits:
4
returned:
4
capped:
no
total_capped:
no
documents:

4 results

  1. entity_name:
    Oppdal kommune
    entity_id:
    5021-oppdal-kommune
    case_title:
    293/46 - Ferdigattest
    case_serial_number:
    2025/11143
    document_id:
    2025/11143-3
    document_type:
    Utgående brev
    document_title:
    293/79 - Ferdigattest for oppføring av fritidsbolig
    document_date:
    2025-11-14
    recorded_date:
    2025-11-21
    from:

    1 results

    1. Sentralt postmottak
    to:

    1 results

    1. HOEL & SØNNER AS
    from_org:

    No results.

    to_org:

    3 results

    1. navn:
      HOEL & SØNNER AS
      orgnummer:
      983858481
    2. navn:
      OPPDALSLAFT AS
      orgnummer:
      898535452
    3. navn:
      THOMAS NESSET MIDELFART
      orgnummer:
      997940881
    case_url:
    https://norske-postlister.no/sak/5021-oppdal-kommune/2025/11143
    files:

    1 results

    1. title:
      <i class="far fa-file-pdf"></i> 293/79 - Ferdigattest for oppf&oslash;ring av fritidsbolig
      url:
      https://prod01.elementscloud.no/publikum/Documents/ShowDocument/c8013432-9247-4c1d-89fc-e5fc61581933/66499/132638
  2. entity_name:
    Trondheim kommune
    entity_id:
    5001-trondheim-kommune
    case_title:
    not reported by source
    case_serial_number:
    2022/5392
    document_id:
    2022/5392-1
    document_type:
    Utgående brev
    document_title:
    Avtale - Ledergruppeutvikling - Bang & Midelfart
    document_date:
    2022-03-01
    recorded_date:
    2022-03-01
    from:

    No results.

    to:

    1 results

    1. THOMAS NESSET MIDELFART AS
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      THOMAS NESSET MIDELFART AS
      orgnummer:
      911587300
    case_url:
    https://norske-postlister.no/sak/5001-trondheim-kommune/2022/5392
    files:

    No results.

  3. entity_name:
    Trondheim kommune
    entity_id:
    5001-trondheim-kommune
    case_title:
    not reported by source
    case_serial_number:
    2022/5392
    document_id:
    2022/5392-2
    document_type:
    Utgående brev
    document_title:
    Avtale - Ledergruppeutvikling - Bang & Midelfart
    document_date:
    2022-03-01
    recorded_date:
    2022-03-01
    from:

    No results.

    to:

    1 results

    1. THOMAS NESSET MIDELFART AS
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      THOMAS NESSET MIDELFART AS
      orgnummer:
      911587300
    case_url:
    https://norske-postlister.no/sak/5001-trondheim-kommune/2022/5392
    files:

    No results.

  4. entity_name:
    Tolletaten
    entity_id:
    tolletaten
    case_title:
    Rammeavtale - Effektive ledergrupper
    case_serial_number:
    2018/30147
    document_id:
    2018/30147-7
    document_type:
    Utgående brev
    document_title:
    Prolongering av rammeavtale - Effektive ledergrupper
    document_date:
    2020-04-07
    recorded_date:
    2020-04-14
    from:

    No results.

    to:

    1 results

    1. Thomas Nesset Midelfart AS
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      THOMAS NESSET MIDELFART AS
      orgnummer:
      911587300
    case_url:
    https://norske-postlister.no/sak/tolletaten/2018/30147
    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.