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-19T23:35:51Z in 0.094 seconds.

total_count:
9
addresses:

9 results

  1. address:
    Lyngveien 2B
    postnummer:
    1356
    poststed:
    BEKKESTUA
    kommunenummer:
    3201
    kommunenavn:
    BÆRUM
    lat:
    59.9092925
    lon:
    10.5737319
    epsg:
    EPSG:4326
  2. address:
    Lyngveien 2B
    postnummer:
    8430
    poststed:
    MYRE
    kommunenummer:
    1868
    kommunenavn:
    ØKSNES
    lat:
    68.9109298
    lon:
    15.0880815
    epsg:
    EPSG:4326
  3. address:
    Lyngveien 2B
    postnummer:
    1433
    poststed:
    ÅS
    kommunenummer:
    3218
    kommunenavn:
    ÅS
    lat:
    59.6658308
    lon:
    10.7873211
    epsg:
    EPSG:4326
  4. address:
    Lyngveien 2B
    postnummer:
    4025
    poststed:
    STAVANGER
    kommunenummer:
    1103
    kommunenavn:
    STAVANGER
    lat:
    58.9764815
    lon:
    5.7074286
    epsg:
    EPSG:4326
  5. address:
    Lyngveien 2B
    postnummer:
    5101
    poststed:
    EIDSVÅGNESET
    kommunenummer:
    4601
    kommunenavn:
    BERGEN
    lat:
    60.4441971
    lon:
    5.281825
    epsg:
    EPSG:4326
  6. address:
    Lyngveien 2B
    postnummer:
    4630
    poststed:
    KRISTIANSAND S
    kommunenummer:
    4204
    kommunenavn:
    KRISTIANSAND
    lat:
    58.1688447
    lon:
    7.9915581
    epsg:
    EPSG:4326
  7. address:
    Lyngveien 2B
    postnummer:
    3470
    poststed:
    SLEMMESTAD
    kommunenummer:
    3203
    kommunenavn:
    ASKER
    lat:
    59.773194
    lon:
    10.4878551
    epsg:
    EPSG:4326
  8. address:
    Lyngveien 2B
    postnummer:
    4950
    poststed:
    RISØR
    kommunenummer:
    4201
    kommunenavn:
    RISØR
    lat:
    58.7172441
    lon:
    9.2323793
    epsg:
    EPSG:4326
  9. address:
    Lyngveien 2B
    postnummer:
    3615
    poststed:
    KONGSBERG
    kommunenummer:
    3303
    kommunenavn:
    KONGSBERG
    lat:
    59.6305065
    lon:
    9.6429365
    epsg:
    EPSG:4326
Show all fields in HTML
total_count:
9
addresses:

9 results

  1. address:
    Lyngveien 2B
    postnummer:
    1356
    poststed:
    BEKKESTUA
    kommunenummer:
    3201
    kommunenavn:
    BÆRUM
    lat:
    59.9092925
    lon:
    10.5737319
    epsg:
    EPSG:4326
  2. address:
    Lyngveien 2B
    postnummer:
    8430
    poststed:
    MYRE
    kommunenummer:
    1868
    kommunenavn:
    ØKSNES
    lat:
    68.9109298
    lon:
    15.0880815
    epsg:
    EPSG:4326
  3. address:
    Lyngveien 2B
    postnummer:
    1433
    poststed:
    ÅS
    kommunenummer:
    3218
    kommunenavn:
    ÅS
    lat:
    59.6658308
    lon:
    10.7873211
    epsg:
    EPSG:4326
  4. address:
    Lyngveien 2B
    postnummer:
    4025
    poststed:
    STAVANGER
    kommunenummer:
    1103
    kommunenavn:
    STAVANGER
    lat:
    58.9764815
    lon:
    5.7074286
    epsg:
    EPSG:4326
  5. address:
    Lyngveien 2B
    postnummer:
    5101
    poststed:
    EIDSVÅGNESET
    kommunenummer:
    4601
    kommunenavn:
    BERGEN
    lat:
    60.4441971
    lon:
    5.281825
    epsg:
    EPSG:4326
  6. address:
    Lyngveien 2B
    postnummer:
    4630
    poststed:
    KRISTIANSAND S
    kommunenummer:
    4204
    kommunenavn:
    KRISTIANSAND
    lat:
    58.1688447
    lon:
    7.9915581
    epsg:
    EPSG:4326
  7. address:
    Lyngveien 2B
    postnummer:
    3470
    poststed:
    SLEMMESTAD
    kommunenummer:
    3203
    kommunenavn:
    ASKER
    lat:
    59.773194
    lon:
    10.4878551
    epsg:
    EPSG:4326
  8. address:
    Lyngveien 2B
    postnummer:
    4950
    poststed:
    RISØR
    kommunenummer:
    4201
    kommunenavn:
    RISØR
    lat:
    58.7172441
    lon:
    9.2323793
    epsg:
    EPSG:4326
  9. address:
    Lyngveien 2B
    postnummer:
    3615
    poststed:
    KONGSBERG
    kommunenummer:
    3303
    kommunenavn:
    KONGSBERG
    lat:
    59.6305065
    lon:
    9.6429365
    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.