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-11T00:42:51Z in 0.188 seconds.

total_hits:
7
returned:
7
capped:
no
documents:

7 results

  1. entity_name:
    Norges forskningsråd
    entity_id:
    norges-forskningsrad
    case_title:
    Prosjekt: Improved hosting of datacentre
    case_serial_number:
    2020/8429
    document_id:
    2020/8429-2
    document_type:
    Utgående brev
    document_title:
    Avslag på søknad
    document_date:
    2020-11-12
    recorded_date:
    2020-11-12
    from:

    No results.

    to:

    1 results

    1. REDQ AS
    from_org:

    No results.

    to_org:

    1 results

    1. navn:
      REDQ AS
      orgnummer:
      812686062
    case_url:
    https://norske-postlister.no/sak/norges-forskningsrad/2020/8429
    files:

    No results.

  2. entity_name:
    Norges forskningsråd
    entity_id:
    norges-forskningsrad
    case_title:
    Prosjekt: Improved hosting of datacentre
    case_serial_number:
    2020/8429
    document_id:
    2020/8429-1
    document_type:
    Inngående brev
    document_title:
    Søknad med søknadsdokumenter
    document_date:
    2020-08-31
    recorded_date:
    2020-08-31
    from:

    1 results

    1. REDQ AS
    to:

    No results.

    from_org:

    1 results

    1. navn:
      REDQ AS
      orgnummer:
      812686062
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/norges-forskningsrad/2020/8429
    files:

    No results.

  3. entity_name:
    Frogn kommune
    entity_id:
    0215-frogn-kommune
    case_title:
    Anskaffelse IKT konsulenttjenester - StorFollo IKT
    case_serial_number:
    20/01449
    document_id:
    2020/1449-25
    document_type:
    Inngående brev
    document_title:
    IKT konsulenttjenester - Tilbud - Avskjermet
    document_date:
    2020-04-27
    recorded_date:
    2020-06-22
    from:

    1 results

    1. RedQ
    to:

    No results.

    from_org:

    1 results

    1. navn:
      REDQ AS
      orgnummer:
      812686062
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/0215-frogn-kommune/2020/1449
    files:

    No results.

  4. entity_name:
    Arbeids- og velferdsdirektoratet (NAV)
    entity_id:
    dir-arbeid-og-velferd
    case_title:
    Digital overføring av dokumentasjon til Trygderetten
    case_serial_number:
    2019/625
    document_id:
    2019/625-114
    document_type:
    Inngående brev
    document_title:
    Trygderetten - NAV - Melding fra RedQ - TRs leverandør
    document_date:
    2019-12-23
    recorded_date:
    2020-01-06
    from:

    1 results

    1. RedQ
    to:

    No results.

    from_org:

    1 results

    1. navn:
      REDQ AS
      orgnummer:
      812686062
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/dir-arbeid-og-velferd/2019/625
    files:

    No results.

  5. entity_name:
    Arbeids- og velferdsdirektoratet (NAV)
    entity_id:
    dir-arbeid-og-velferd
    case_title:
    Digital overføring av dokumentasjon til Trygderetten
    case_serial_number:
    2019/625
    document_id:
    2019/625-53
    document_type:
    Utgående brev
    document_title:
    Svar - E-formidling - driftsmelding
    document_date:
    2019-10-22
    recorded_date:
    2020-01-06
    from:

    No results.

    to:

    4 results

    1. Evry
    2. Trygderetten
    3. RedQ
    4. RedQ
    from_org:

    No results.

    to_org:

    4 results

    1. navn:
      EVRY AS
      orgnummer:
      934382404
    2. navn:
      TRYGDERETTEN
      orgnummer:
      974714671
    3. navn:
      REDQ AS
      orgnummer:
      812686062
    4. navn:
      REDQ AS
      orgnummer:
      812686062
    case_url:
    https://norske-postlister.no/sak/dir-arbeid-og-velferd/2019/625
    files:

    No results.

  6. entity_name:
    Kommunal- og distriktsdepartementet
    entity_id:
    dep-kommunal-og-moderning
    case_title:
    Invitasjoner til politisk ledelse
    case_serial_number:
    2015/122
    document_id:
    2015/122-288
    document_type:
    Inngående brev
    document_title:
    100216 eller 110216 - Invitasjon til seminaret Software 2016
    document_date:
    2015-09-23
    recorded_date:
    2015-09-23
    from:

    1 results

    1. redQ AS
    to:

    No results.

    from_org:

    1 results

    1. navn:
      REDQ AS
      orgnummer:
      812686062
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/dep-kommunal-og-moderning/2015/122
    files:

    No results.

  7. entity_name:
    Kommunal- og distriktsdepartementet
    entity_id:
    dep-kommunal-og-moderning
    case_title:
    Invitasjoner til politisk ledelse
    case_serial_number:
    2015/122
    document_id:
    2015/122-145
    document_type:
    Inngående brev
    document_title:
    Invitasjon til seminaret Software 2016
    document_date:
    2015-05-05
    recorded_date:
    2015-05-05
    from:

    1 results

    1. redQ as
    to:

    No results.

    from_org:

    1 results

    1. navn:
      REDQ AS
      orgnummer:
      812686062
    to_org:

    No results.

    case_url:
    https://norske-postlister.no/sak/dep-kommunal-og-moderning/2015/122
    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.