Allemannsdata
Manual search

search

Search Norwegian public mail journals (postlister).

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).
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": "..."}
}
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).

Result

Source: Norwegian public correspondence journals. Retrieved 2026-08-02T17:43:27Z in 0.295 seconds.

total_hits:
1
returned:
1
capped:
no
documents:

1 results

  1. entity_name:
    Digitaliseringsdirektoratet
    entity_id:
    difi
    case_title:
    ISA² (Interoperability Solutions for European Public Administrations) - Koordinering på nasjonalt nivå
    case_serial_number:
    2016/361
    document_id:
    2016/361-15
    document_type:
    Utgående brev
    document_title:
    Forslag til ISA² Work Programme 2020
    document_date:
    2019-06-19
    recorded_date:
    2019-06-27
    from:

    No results.

    to:

    13 results

    1. Brønnøysundregistrene
    2. Skatteetaten
    3. Skatteetaten
    4. Brønnøysundregistrene
    5. Brønnøysundregistrene
    6. Brønnøysundregistrene
    7. Brønnøysundregistrene
    8. Kommunal- og moderniseringsdepartementet
    9. Brønnøysundregistrene
    10. Stiftelsen Lovdata
    11. Arbeids- og velferdsdirektoratet
    12. Statens kartverk
    13. Bergen kommune
    from_org:

    No results.

    to_org:

    13 results

    1. navn:
      brønnøysundregistrene
      orgnummer:
      974760673
    2. navn:
      SKATTEETATEN
      orgnummer:
      974761076
    3. navn:
      SKATTEETATEN
      orgnummer:
      974761076
    4. navn:
      brønnøysundregistrene
      orgnummer:
      974760673
    5. navn:
      brønnøysundregistrene
      orgnummer:
      974760673
    6. navn:
      brønnøysundregistrene
      orgnummer:
      974760673
    7. navn:
      brønnøysundregistrene
      orgnummer:
      974760673
    8. navn:
      KOMMUNAL- OG MODERNISERINGSDEPARTEMENTET
      orgnummer:
      972417858
    9. navn:
      brønnøysundregistrene
      orgnummer:
      974760673
    10. navn:
      STIFTELSEN LOVDATA
      orgnummer:
      not reported by source
    11. navn:
      arbeids- og velferdsdirektoratet
      orgnummer:
      889640782
    12. navn:
      STATENS KARTVERK
      orgnummer:
      971040238
    13. navn:
      BERGEN KOMMUNE
      orgnummer:
      964338531
    case_url:
    https://norske-postlister.no/sak/difi/2016/361
    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

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.