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 25; 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=25&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=25&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. Unit: items. Through this API: default 25, maximum 100.
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=25&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=25&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=25&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. Unit: items. Through this API: default 25, maximum 100.
Type: string. Alias for `text` (use one or the other).

Result

Source: Geonorge. Retrieved 2026-11-21T05:22:56Z in 0.101 seconds.

total_count:
9
addresses:

9 results

  1. address:
    Kirkeveien 230
    postnummer:
    1383
    poststed:
    ASKER
    kommunenummer:
    3203
    kommunenavn:
    ASKER
    lat:
    59.8337961
    lon:
    10.4287028
    epsg:
    EPSG:4326
  2. address:
    Kirkeveien 230
    postnummer:
    3140
    poststed:
    NØTTERØY
    kommunenummer:
    3911
    kommunenavn:
    FÆRDER
    lat:
    59.2194405
    lon:
    10.4061905
    epsg:
    EPSG:4326
  3. address:
    Kirkeveien 17
    postnummer:
    8312
    poststed:
    HENNINGSVÆR
    kommunenummer:
    1865
    kommunenavn:
    VÅGAN
    lat:
    68.1525006
    lon:
    14.1990687
    epsg:
    EPSG:4326
  4. address:
    Kirkeveien 58
    postnummer:
    8800
    poststed:
    SANDNESSJØEN
    kommunenummer:
    1820
    kommunenavn:
    ALSTAHAUG
    lat:
    66.0179285
    lon:
    12.6048308
    epsg:
    EPSG:4326
  5. address:
    Tromøy kirkevei 230
    postnummer:
    4818
    poststed:
    FÆRVIK
    kommunenummer:
    4203
    kommunenavn:
    ARENDAL
    lat:
    58.4488898
    lon:
    8.8498997
    epsg:
    EPSG:4326
  6. address:
    Gamle Kirkevei 18
    postnummer:
    7068
    poststed:
    TRONDHEIM
    kommunenummer:
    5001
    kommunenavn:
    TRONDHEIM
    lat:
    63.4358436
    lon:
    10.4232104
    epsg:
    EPSG:4326
  7. address:
    Gamle Kirkevei 20
    postnummer:
    7068
    poststed:
    TRONDHEIM
    kommunenummer:
    5001
    kommunenavn:
    TRONDHEIM
    lat:
    63.435914
    lon:
    10.4233542
    epsg:
    EPSG:4326
  8. address:
    Gamle Kirkevei 22
    postnummer:
    7068
    poststed:
    TRONDHEIM
    kommunenummer:
    5001
    kommunenavn:
    TRONDHEIM
    lat:
    63.436084
    lon:
    10.4234027
    epsg:
    EPSG:4326
  9. address:
    Gamle Kirkevei 57
    postnummer:
    1617
    poststed:
    FREDRIKSTAD
    kommunenummer:
    3107
    kommunenavn:
    FREDRIKSTAD
    lat:
    59.2321669
    lon:
    10.9651857
    epsg:
    EPSG:4326
Show all fields in HTML
total_count:
9
addresses:

9 results

  1. address:
    Kirkeveien 230
    postnummer:
    1383
    poststed:
    ASKER
    kommunenummer:
    3203
    kommunenavn:
    ASKER
    lat:
    59.8337961
    lon:
    10.4287028
    epsg:
    EPSG:4326
  2. address:
    Kirkeveien 230
    postnummer:
    3140
    poststed:
    NØTTERØY
    kommunenummer:
    3911
    kommunenavn:
    FÆRDER
    lat:
    59.2194405
    lon:
    10.4061905
    epsg:
    EPSG:4326
  3. address:
    Kirkeveien 17
    postnummer:
    8312
    poststed:
    HENNINGSVÆR
    kommunenummer:
    1865
    kommunenavn:
    VÅGAN
    lat:
    68.1525006
    lon:
    14.1990687
    epsg:
    EPSG:4326
  4. address:
    Kirkeveien 58
    postnummer:
    8800
    poststed:
    SANDNESSJØEN
    kommunenummer:
    1820
    kommunenavn:
    ALSTAHAUG
    lat:
    66.0179285
    lon:
    12.6048308
    epsg:
    EPSG:4326
  5. address:
    Tromøy kirkevei 230
    postnummer:
    4818
    poststed:
    FÆRVIK
    kommunenummer:
    4203
    kommunenavn:
    ARENDAL
    lat:
    58.4488898
    lon:
    8.8498997
    epsg:
    EPSG:4326
  6. address:
    Gamle Kirkevei 18
    postnummer:
    7068
    poststed:
    TRONDHEIM
    kommunenummer:
    5001
    kommunenavn:
    TRONDHEIM
    lat:
    63.4358436
    lon:
    10.4232104
    epsg:
    EPSG:4326
  7. address:
    Gamle Kirkevei 20
    postnummer:
    7068
    poststed:
    TRONDHEIM
    kommunenummer:
    5001
    kommunenavn:
    TRONDHEIM
    lat:
    63.435914
    lon:
    10.4233542
    epsg:
    EPSG:4326
  8. address:
    Gamle Kirkevei 22
    postnummer:
    7068
    poststed:
    TRONDHEIM
    kommunenummer:
    5001
    kommunenavn:
    TRONDHEIM
    lat:
    63.436084
    lon:
    10.4234027
    epsg:
    EPSG:4326
  9. address:
    Gamle Kirkevei 57
    postnummer:
    1617
    poststed:
    FREDRIKSTAD
    kommunenummer:
    3107
    kommunenavn:
    FREDRIKSTAD
    lat:
    59.2321669
    lon:
    10.9651857
    epsg:
    EPSG:4326
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.