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-12T02:25:54Z in 0.172 seconds.

total_hits:
7
returned:
7
capped:
no
documents:

7 results

  1. entity_name:
    Trondheim kommune
    entity_id:
    5001-trondheim-kommune
    case_title:
    not reported by source
    case_serial_number:
    2025/28163
    document_id:
    2025/28163-1
    document_type:
    Inngående brev
    document_title:
    Finalebanen, søknad om bruk til reklameopptak
    document_date:
    2025-09-11
    recorded_date:
    2025-09-15
    from:

    1 results

    1. NONSPACE AS
    to:

    No results.

    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/5001-trondheim-kommune/2025/28163
    files:

    No results.

  2. entity_name:
    Sivilombudet
    entity_id:
    sivilombudsmannen
    case_title:
    Anbud/anskaffelse - drift og videreutvikling av nettsider
    case_serial_number:
    2024/4101
    document_id:
    2024/4101-88
    document_type:
    Utgående brev
    document_title:
    Oppfølging av anskaffelsesprosess - informasjon om valgt leverandør
    document_date:
    2024-11-14
    recorded_date:
    2024-11-14
    from:

    1 results

    1. Sivilombudet
    to:

    1 results

    1. NONSPACE AS
    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/sivilombudsmannen/2024/4101
    files:

    1 results

    1. title:
      <i class="far fa-file"></i> Dokumentet er ikke tilgjengelig
      url:
      not reported by source
  3. entity_name:
    Sivilombudet
    entity_id:
    sivilombudsmannen
    case_title:
    Anbud/anskaffelse - drift og videreutvikling av nettsider
    case_serial_number:
    2024/4101
    document_id:
    2024/4101-63
    document_type:
    Utgående brev
    document_title:
    Svar på tilbud fra Nonspace AS
    document_date:
    2024-11-12
    recorded_date:
    2024-11-12
    from:

    1 results

    1. Sivilombudet
    to:

    1 results

    1. NONSPACE AS
    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/sivilombudsmannen/2024/4101
    files:

    1 results

    1. title:
      <i class="far fa-file"></i> Dokumentet er ikke tilgjengelig
      url:
      not reported by source
  4. entity_name:
    Statens vegvesen
    entity_id:
    statens-vegvesen
    case_title:
    Rammeavtale for kjøp av bistand til utvikling, planlegging og gjennomføring av kampanjer, events og annet utadrettet arbeid for Miljøløftet
    case_serial_number:
    2024/101940
    document_id:
    2024/101940-45
    document_type:
    Utgående brev
    document_title:
    Avvisning av tilbud
    document_date:
    2024-10-04
    recorded_date:
    2024-10-04
    from:

    No results.

    to:

    1 results

    1. NONSPACE AS
    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/statens-vegvesen/2024/101940
    files:

    No results.

  5. entity_name:
    Universitetet i Bergen
    entity_id:
    utdanning-uib
    case_title:
    ANSK-23-0176 Publiseringsløsning for Bjerknessenteret
    case_serial_number:
    2023/16396
    document_id:
    2023/16396-4
    document_type:
    Utgående brev
    document_title:
    ANSK-23-0176 Tildelingsbrev i konkurransen Publiseringsløsning for Bjerknessenteret
    document_date:
    2024-05-22
    recorded_date:
    2024-09-05
    from:

    1 results

    1. Universitetet i Bergen
    to:

    9 results

    1. Nonspace
    2. Everyday
    3. Netlab
    4. Dekode
    5. CoreTrek x
    6. Erke teknologi x
    7. Heisenbug x
    8. Item Consulting x
    9. Seeds Consulting x
    from_org:

    1 results

    1. navn:
      UNIVERSITETET I BERGEN
      orgnummer:
      874789542
    to_org:

    2 results

    1. navn:
      EVERYDAY AS
      orgnummer:
      914840368
    2. navn:
      NETLAB AS
      orgnummer:
      987109696
    case_url:
    https://norske-postlister.no/sak/utdanning-uib/2023/16396
    files:

    No results.

  6. entity_name:
    Trondheim kommune
    entity_id:
    5001-trondheim-kommune
    case_title:
    not reported by source
    case_serial_number:
    2023/19368
    document_id:
    2023/19368-30
    document_type:
    Utgående brev
    document_title:
    Tildelingsvedtak - Nye Trondheim.com
    document_date:
    2023-11-10
    recorded_date:
    2023-11-13
    from:

    No results.

    to:

    1 results

    1. Nonspace Bergen AS
    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/5001-trondheim-kommune/2023/19368
    files:

    No results.

  7. entity_name:
    Trondheim kommune
    entity_id:
    5001-trondheim-kommune
    case_title:
    not reported by source
    case_serial_number:
    2023/19488
    document_id:
    2023/19488-10
    document_type:
    Utgående brev
    document_title:
    Tildelingsvedtak - Videreutvikling Trondheim city brand
    document_date:
    2023-11-01
    recorded_date:
    2023-11-06
    from:

    No results.

    to:

    1 results

    1. Nonspace Bergen AS
    from_org:

    No results.

    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/5001-trondheim-kommune/2023/19488
    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.