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-19T10:33:06Z in 0.104 seconds.

total_count:
9
addresses:

9 results

  1. address:
    Apalveien 2
    postnummer:
    1900
    poststed:
    FETSUND
    kommunenummer:
    3205
    kommunenavn:
    LILLESTRØM
    lat:
    59.9303121
    lon:
    11.1358238
    epsg:
    EPSG:4326
  2. address:
    Apalveien 2
    postnummer:
    1809
    poststed:
    ASKIM
    kommunenummer:
    3118
    kommunenavn:
    INDRE ØSTFOLD
    lat:
    59.5889455
    lon:
    11.1927885
    epsg:
    EPSG:4326
  3. address:
    Apalveien 2
    postnummer:
    4371
    poststed:
    EGERSUND
    kommunenummer:
    1101
    kommunenavn:
    EIGERSUND
    lat:
    58.438127
    lon:
    6.0041186
    epsg:
    EPSG:4326
  4. address:
    Apalveien 2
    postnummer:
    4315
    poststed:
    SANDNES
    kommunenummer:
    1108
    kommunenavn:
    SANDNES
    lat:
    58.8738783
    lon:
    5.7389551
    epsg:
    EPSG:4326
  5. address:
    Apalveien 2
    postnummer:
    0371
    poststed:
    OSLO
    kommunenummer:
    0301
    kommunenavn:
    OSLO
    lat:
    59.9335097
    lon:
    10.7107856
    epsg:
    EPSG:4326
  6. address:
    Apalveien 2
    postnummer:
    3413
    poststed:
    LIER
    kommunenummer:
    3312
    kommunenavn:
    LIER
    lat:
    59.751619
    lon:
    10.2328733
    epsg:
    EPSG:4326
  7. address:
    Apalveien 2
    postnummer:
    3514
    poststed:
    HØNEFOSS
    kommunenummer:
    3305
    kommunenavn:
    RINGERIKE
    lat:
    60.1684981
    lon:
    10.3408602
    epsg:
    EPSG:4326
  8. address:
    Apalveien 2
    postnummer:
    3360
    poststed:
    GEITHUS
    kommunenummer:
    3316
    kommunenavn:
    MODUM
    lat:
    59.9134051
    lon:
    9.9543812
    epsg:
    EPSG:4326
  9. address:
    Apalveien 13
    postnummer:
    4315
    poststed:
    SANDNES
    kommunenummer:
    1108
    kommunenavn:
    SANDNES
    lat:
    58.8742326
    lon:
    5.7387482
    epsg:
    EPSG:4326
Show all fields in HTML
total_count:
9
addresses:

9 results

  1. address:
    Apalveien 2
    postnummer:
    1900
    poststed:
    FETSUND
    kommunenummer:
    3205
    kommunenavn:
    LILLESTRØM
    lat:
    59.9303121
    lon:
    11.1358238
    epsg:
    EPSG:4326
  2. address:
    Apalveien 2
    postnummer:
    1809
    poststed:
    ASKIM
    kommunenummer:
    3118
    kommunenavn:
    INDRE ØSTFOLD
    lat:
    59.5889455
    lon:
    11.1927885
    epsg:
    EPSG:4326
  3. address:
    Apalveien 2
    postnummer:
    4371
    poststed:
    EGERSUND
    kommunenummer:
    1101
    kommunenavn:
    EIGERSUND
    lat:
    58.438127
    lon:
    6.0041186
    epsg:
    EPSG:4326
  4. address:
    Apalveien 2
    postnummer:
    4315
    poststed:
    SANDNES
    kommunenummer:
    1108
    kommunenavn:
    SANDNES
    lat:
    58.8738783
    lon:
    5.7389551
    epsg:
    EPSG:4326
  5. address:
    Apalveien 2
    postnummer:
    0371
    poststed:
    OSLO
    kommunenummer:
    0301
    kommunenavn:
    OSLO
    lat:
    59.9335097
    lon:
    10.7107856
    epsg:
    EPSG:4326
  6. address:
    Apalveien 2
    postnummer:
    3413
    poststed:
    LIER
    kommunenummer:
    3312
    kommunenavn:
    LIER
    lat:
    59.751619
    lon:
    10.2328733
    epsg:
    EPSG:4326
  7. address:
    Apalveien 2
    postnummer:
    3514
    poststed:
    HØNEFOSS
    kommunenummer:
    3305
    kommunenavn:
    RINGERIKE
    lat:
    60.1684981
    lon:
    10.3408602
    epsg:
    EPSG:4326
  8. address:
    Apalveien 2
    postnummer:
    3360
    poststed:
    GEITHUS
    kommunenummer:
    3316
    kommunenavn:
    MODUM
    lat:
    59.9134051
    lon:
    9.9543812
    epsg:
    EPSG:4326
  9. address:
    Apalveien 13
    postnummer:
    4315
    poststed:
    SANDNES
    kommunenummer:
    1108
    kommunenavn:
    SANDNES
    lat:
    58.8742326
    lon:
    5.7387482
    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.