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.

Parameter	Requirement	JSON type	Description
`query`	optional	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).
`entity_id`	optional	union	Restrict to one authority, e.g. "2012-alta-kommune". Read it off `entity_id` in earlier results.
`date_from`	optional	union	Document-date lower bound, ISO "YYYY-MM-DD" (inclusive).
`date_to`	optional	union	Document-date upper bound, ISO "YYYY-MM-DD" (inclusive).
`limit`	optional	integer	Max documents to return, 1 to 100 (default 20). Unit: items. Through this API: default 25, maximum 100.
`offset`	optional	integer	Number 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.

query 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).

entity_id Type: string. Restrict to one authority, e.g. "2012-alta-kommune". Read it off `entity_id` in earlier results.

date_from Type: string. Document-date lower bound, ISO "YYYY-MM-DD" (inclusive).

date_to Type: string. Document-date upper bound, ISO "YYYY-MM-DD" (inclusive).

limit Type: integer. Max documents to return, 1 to 100 (default 20). Unit: items. Through this API: default 25, maximum 100.

Result

Source: Norwegian public correspondence journals. Retrieved 2026-11-02T18:12:30Z in 0.193 seconds.

total_hits:

returned:

capped:

total_capped:

documents:

7 results

entity_name:
Lotteri- og stiftelsestilsynet
entity_id:
lotteri--og-stiftelsestilsynet
case_title:
Anbod - Pengespelregisteret - 2023
case_serial_number:
2023/2281
document_id:
2023/2281-11
document_type:
Utgående brev
document_title:
Tildeling har blitt utført i konkurranse 344244:1 Anskaffelse av utviklingskapasitet saksbehandlingssystem
document_date:
2023-11-03
recorded_date:
2023-11-15
from:
No results.
to:
5 results
1. SOPRA STERIA AS
2. KPMG AS
3. FLUIDO NORWAY AS
4. Xebia Poland
5. CAPGEMINI NORGE AS
from_org:
No results.
to_org:
4 results
1. navn:
 SOPRA STERIA AS
 orgnummer:
 910909088
2. navn:
 KPMG AS
 orgnummer:
 935174627
3. navn:
 FLUIDO NORWAY AS
 orgnummer:
 915491766
4. navn:
 CAPGEMINI NORGE AS
 orgnummer:
 943574537
case_url:
https://norske-postlister.no/sak/lotteri--og-stiftelsestilsynet/2023/2281
files:
2 results
1. title:
 tildeling_kunngjøring_melding
 url:
 https://einnsyn.no/api/v2/fil?iri=http://data.einnsyn.no/noark4/236cf53e-cba6-47ce-b581-7852eea369b1
2. title:
 Kunngjøring pengespillregister
 url:
 https://einnsyn.no/api/v2/fil?iri=http://data.einnsyn.no/noark4/f0977765-583b-45a0-b2f1-3d6bf077fa63
entity_name:
Lotteri- og stiftelsestilsynet
entity_id:
lotteri--og-stiftelsestilsynet
case_title:
Anbod - Pengespelregisteret - 2023
case_serial_number:
2023/2281
document_id:
2023/2281-9
document_type:
Inngående brev
document_title:
Tilbud fra FLUIDO NORWAY AS
document_date:
2023-10-23
recorded_date:
2023-11-09
from:
1 results
1. FLUIDO NORWAY AS
to:
No results.
from_org:
1 results
1. navn:
  FLUIDO NORWAY AS
  orgnummer:
  915491766
to_org:
No results.
case_url:
https://norske-postlister.no/sak/lotteri--og-stiftelsestilsynet/2023/2281
files:
No results.
entity_name:
Lotteri- og stiftelsestilsynet
entity_id:
lotteri--og-stiftelsestilsynet
case_title:
Anbod - Pengespelregisteret - 2023
case_serial_number:
2023/2281
document_id:
2023/2281-3
document_type:
Utgående brev
document_title:
Svar om konkurransegrunnlaget
document_date:
2023-10-19
recorded_date:
2023-11-09
from:
No results.
to:
13 results
1. KPMG AS
2. FLUIDO NORWAY AS
3. Rainfall AS
4. Axenon AB
5. Xebia Poland
6. Avo Consulting Norway AS
7. Abb pvt Ltd
8. Knowit AS
9. PRICEWATERHOUSECOOPERS AS
10. CAPGEMINI NORGE AS
11. SOPRA STERIA AS
12. Compose Software AS
13. MIDIAN TECHNOLOGY AS
from_org:
No results.
to_org:
8 results
1. navn:
 KPMG AS
 orgnummer:
 935174627
2. navn:
 FLUIDO NORWAY AS
 orgnummer:
 915491766
3. navn:
 RAINFALL AS
 orgnummer:
 985708452
4. navn:
 AVO CONSULTING NORWAY AS
 orgnummer:
 918664696
5. navn:
 KNOWIT AS
 orgnummer:
 997725646
6. navn:
 PRICEWATERHOUSECOOPERS AS
 orgnummer:
 987009713
7. navn:
 CAPGEMINI NORGE AS
 orgnummer:
 943574537
8. navn:
 SOPRA STERIA AS
 orgnummer:
 910909088
case_url:
https://norske-postlister.no/sak/lotteri--og-stiftelsestilsynet/2023/2281
files:
2 results
1. title:
 Første svar i eu-supply
 url:
 https://einnsyn.no/api/v2/fil?iri=http://data.einnsyn.no/noark4/d29b38c1-7157-487a-88ee-db3657085334
2. title:
 Spørsma?l til konkurransegrunnlaget (2)
 url:
 https://einnsyn.no/api/v2/fil?iri=http://data.einnsyn.no/noark4/e064d982-674a-47bb-9f46-14ba3ea2cfaa
entity_name:
Avinor AS
entity_id:
avinor
case_title:
Avinor AS - K-186921 - Implementeringspartner CRM B2C - Salesforce Marketing Cloud - Fluido Norway AS
case_serial_number:
2017/6163
document_id:
2017/6163-5
document_type:
Inngående brev
document_title:
Avinor AS - K-186921 - Implementeringspartner CRM B2C - Salesforce Marketing Cloud - Fornyelse for perioden 19012023-18012024
document_date:
2022-12-20
recorded_date:
2023-02-27
from:
1 results
1. Fluido Norway AS
to:
No results.
from_org:
1 results
1. navn:
  FLUIDO NORWAY AS
  orgnummer:
  915491766
to_org:
No results.
case_url:
https://norske-postlister.no/sak/avinor/2017/6163
files:
No results.
entity_name:
Avinor AS
entity_id:
avinor
case_title:
Avinor AS - K-186921 - Implementeringspartner CRM B2C - Salesforce Marketing Cloud - Fluido Norway AS
case_serial_number:
2017/6163
document_id:
2017/6163-6
document_type:
Inngående brev
document_title:
Avinor AS - K-186921 - Implementeringspartner CRM B2C - Salesforce Marketing Cloud - Elektronisk signatur av lisensdokument
document_date:
2022-12-20
recorded_date:
2023-02-27
from:
1 results
1. Fluido Norway AS
to:
No results.
from_org:
1 results
1. navn:
  FLUIDO NORWAY AS
  orgnummer:
  915491766
to_org:
No results.
case_url:
https://norske-postlister.no/sak/avinor/2017/6163
files:
No results.
entity_name:
Finanstilsynet
entity_id:
finanstilsynet
case_title:
Annet generelt om eiendomsmegling
case_serial_number:
2017/10870
document_id:
2017/10870-2
document_type:
Utgående brev
document_title:
Arkiveringsplikt
document_date:
2017-11-21
recorded_date:
2017-11-24
from:
No results.
to:
1 results
1. Fluido Norway AS
from_org:
No results.
to_org:
1 results
1. navn:
  FLUIDO NORWAY AS
  orgnummer:
  915491766
case_url:
https://norske-postlister.no/sak/finanstilsynet/2017/10870
files:
No results.
entity_name:
Finanstilsynet
entity_id:
finanstilsynet
case_title:
Annet generelt om eiendomsmegling
case_serial_number:
2017/10870
document_id:
2017/10870-1
document_type:
Inngående brev
document_title:
Spørsmål om rapporteringsplikt
document_date:
2017-11-01
recorded_date:
2017-11-08
from:
1 results
1. Fluido Norway AS
to:
No results.
from_org:
1 results
1. navn:
  FLUIDO NORWAY AS
  orgnummer:
  915491766
to_org:
No results.
case_url:
https://norske-postlister.no/sak/finanstilsynet/2017/10870
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

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
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.