search_address

Search Norwegian addresses by free text.

Signature: search_address(text: string, optional, default None; kommunenummer: string, optional, default None; limit: integer, items, optional, default 20; query: string, optional, default None; 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/geonorge/search_address/?text={text}&kommunenummer={kommunenummer}&limit=20&query={query}&offset=0

Replace {text}, {kommunenummer}, {limit}, {query} 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/geonorge/search_address?text={text}&kommunenummer={kommunenummer}&limit=20&query={query}&offset=0. Open this exact request as JSON.

ParameterRequirementJSON typeDescription
textoptionalunionAddress query, e.g. "Karl Johans gate 1" or "Storgata".
kommunenummeroptionalunionOptional 4-digit municipality code to restrict the search (e.g. "0301" for Oslo, "4601" for Bergen).
limitoptionalintegerMax hits to return, 1 to 100 (default 20). Unit: items.
queryoptionalunionAlias for `text` (use one or the other).
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/geonorge/search_address?text={text}&kommunenummer={kommunenummer}&limit=20&query={query}&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/geonorge/search_address?text={text}&kommunenummer={kommunenummer}&limit=20&query={query}&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/geonorge/search_address?text={text}&kommunenummer={kommunenummer}&limit=20&query={query}&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "geonorge",
  "operation": "search_address",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}

Unknown parameter ignored: postal_code. Valid parameters: text, kommunenummer, limit, query.

Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Type: string. Address query, e.g. "Karl Johans gate 1" or "Storgata".
Type: string. Optional 4-digit municipality code to restrict the search (e.g. "0301" for Oslo, "4601" for Bergen).
Type: integer. Max hits to return, 1 to 100 (default 20). Unit: items.
Type: string. Alias for `text` (use one or the other).

Result

Source: Geonorge. Retrieved 2026-09-12T06:46:29Z in 0.066 seconds.

total_count:
9
addresses:

9 results

  1. address:
    Vangsveien 12
    postnummer:
    8475
    poststed:
    STRAUMSJØEN
    kommunenummer:
    1867
    kommunenavn:
    lat:
    68.746198
    lon:
    14.6857233
    epsg:
    EPSG:4326
  2. address:
    Vangsveien 12
    postnummer:
    4517
    poststed:
    MANDAL
    kommunenummer:
    4205
    kommunenavn:
    LINDESNES
    lat:
    58.0367828
    lon:
    7.4645734
    epsg:
    EPSG:4326
  3. address:
    Vangsveien 12
    postnummer:
    3440
    poststed:
    RØYKEN
    kommunenummer:
    3203
    kommunenavn:
    ASKER
    lat:
    59.7502731
    lon:
    10.4020526
    epsg:
    EPSG:4326
  4. address:
    Vangsveien 12
    postnummer:
    8890
    poststed:
    LEIRFJORD
    kommunenummer:
    1822
    kommunenavn:
    LEIRFJORD
    lat:
    66.0632281
    lon:
    12.9425349
    epsg:
    EPSG:4326
  5. address:
    Vangsveien 12
    postnummer:
    8200
    poststed:
    FAUSKE
    kommunenummer:
    1841
    kommunenavn:
    FAUSKE
    lat:
    67.261548
    lon:
    15.3861748
    epsg:
    EPSG:4326
  6. address:
    Vangsveien 12
    postnummer:
    1470
    poststed:
    LØRENSKOG
    kommunenummer:
    3222
    kommunenavn:
    LØRENSKOG
    lat:
    59.9363635
    lon:
    10.961387
    epsg:
    EPSG:4326
  7. address:
    Vangsveien 12
    postnummer:
    3514
    poststed:
    HØNEFOSS
    kommunenummer:
    3305
    kommunenavn:
    RINGERIKE
    lat:
    60.1762969
    lon:
    10.3272981
    epsg:
    EPSG:4326
  8. address:
    Vangsveien 109
    postnummer:
    2550
    poststed:
    OS I ØSTERDALEN
    kommunenummer:
    3430
    kommunenavn:
    OS
    lat:
    62.5242807
    lon:
    11.2233984
    epsg:
    EPSG:4326
  9. address:
    Vangsveien 3
    postnummer:
    8890
    poststed:
    LEIRFJORD
    kommunenummer:
    1822
    kommunenavn:
    LEIRFJORD
    lat:
    66.0635595
    lon:
    12.9422098
    epsg:
    EPSG:4326
limit:
25
offset:
0
returned:
9
has_more_results:
no
truncated:
no
Show all fields in HTML
total_count:
9
addresses:

9 results

  1. address:
    Vangsveien 12
    postnummer:
    8475
    poststed:
    STRAUMSJØEN
    kommunenummer:
    1867
    kommunenavn:
    lat:
    68.746198
    lon:
    14.6857233
    epsg:
    EPSG:4326
  2. address:
    Vangsveien 12
    postnummer:
    4517
    poststed:
    MANDAL
    kommunenummer:
    4205
    kommunenavn:
    LINDESNES
    lat:
    58.0367828
    lon:
    7.4645734
    epsg:
    EPSG:4326
  3. address:
    Vangsveien 12
    postnummer:
    3440
    poststed:
    RØYKEN
    kommunenummer:
    3203
    kommunenavn:
    ASKER
    lat:
    59.7502731
    lon:
    10.4020526
    epsg:
    EPSG:4326
  4. address:
    Vangsveien 12
    postnummer:
    8890
    poststed:
    LEIRFJORD
    kommunenummer:
    1822
    kommunenavn:
    LEIRFJORD
    lat:
    66.0632281
    lon:
    12.9425349
    epsg:
    EPSG:4326
  5. address:
    Vangsveien 12
    postnummer:
    8200
    poststed:
    FAUSKE
    kommunenummer:
    1841
    kommunenavn:
    FAUSKE
    lat:
    67.261548
    lon:
    15.3861748
    epsg:
    EPSG:4326
  6. address:
    Vangsveien 12
    postnummer:
    1470
    poststed:
    LØRENSKOG
    kommunenummer:
    3222
    kommunenavn:
    LØRENSKOG
    lat:
    59.9363635
    lon:
    10.961387
    epsg:
    EPSG:4326
  7. address:
    Vangsveien 12
    postnummer:
    3514
    poststed:
    HØNEFOSS
    kommunenummer:
    3305
    kommunenavn:
    RINGERIKE
    lat:
    60.1762969
    lon:
    10.3272981
    epsg:
    EPSG:4326
  8. address:
    Vangsveien 109
    postnummer:
    2550
    poststed:
    OS I ØSTERDALEN
    kommunenummer:
    3430
    kommunenavn:
    OS
    lat:
    62.5242807
    lon:
    11.2233984
    epsg:
    EPSG:4326
  9. address:
    Vangsveien 3
    postnummer:
    8890
    poststed:
    LEIRFJORD
    kommunenummer:
    1822
    kommunenavn:
    LEIRFJORD
    lat:
    66.0635595
    lon:
    12.9422098
    epsg:
    EPSG:4326
limit:
25
offset:
0
returned:
9
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_address 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.