search_address
Search Norwegian addresses by free text.
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=0For 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.
| Parameter | Requirement | JSON type | Description |
|---|---|---|---|
text | optional | union | Address query, e.g. "Karl Johans gate 1" or "Storgata". |
kommunenummer | optional | union | Optional 4-digit municipality code to restrict the search (e.g. "0301" for Oslo, "4601" for Bergen). |
limit | optional | integer | Max hits to return, 1 to 100 (default 20). Unit: items. Through this API: default 25, maximum 100. |
query | optional | union | Alias for `text` (use one or the other). |
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/geonorge/search_address?text={text}&kommunenummer={kommunenummer}&limit=25&query={query}&offset=0Replace 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.
Result
- total_count:
- 23
- addresses:
23 results
- address:
- Kroken 11
- postnummer:
- 1466
- poststed:
- STRØMMEN
- kommunenummer:
- 3205
- kommunenavn:
- LILLESTRØM
- lat:
- 59.956234
- lon:
- 11.0219154
- epsg:
- EPSG:4326
- address:
- Kroken 11
- postnummer:
- 7860
- poststed:
- SKAGE I NAMDALEN
- kommunenummer:
- 5047
- kommunenavn:
- OVERHALLA
- lat:
- 64.459315
- lon:
- 11.7714609
- epsg:
- EPSG:4326
- address:
- Kroken 11
- postnummer:
- 3632
- poststed:
- UVDAL
- kommunenummer:
- 3338
- kommunenavn:
- NORE OG UVDAL
- lat:
- 60.3268934
- lon:
- 8.5093627
- epsg:
- EPSG:4326
- address:
- Kroken 11
- postnummer:
- 2609
- poststed:
- LILLEHAMMER
- kommunenummer:
- 3405
- kommunenavn:
- LILLEHAMMER
- lat:
- 61.1106597
- lon:
- 10.4674055
- epsg:
- EPSG:4326
- address:
- Kroken 11A
- postnummer:
- 2386
- poststed:
- BRUMUNDDAL
- kommunenummer:
- 3411
- kommunenavn:
- RINGSAKER
- lat:
- 60.890436
- lon:
- 10.945772
- epsg:
- EPSG:4326
- address:
- Kroken 11B
- postnummer:
- 2386
- poststed:
- BRUMUNDDAL
- kommunenummer:
- 3411
- kommunenavn:
- RINGSAKER
- lat:
- 60.8902431
- lon:
- 10.9462542
- epsg:
- EPSG:4326
- address:
- Kroken 52
- postnummer:
- 5713
- poststed:
- VOSSESTRAND
- kommunenummer:
- 4621
- kommunenavn:
- VOSS
- lat:
- 60.7792318
- lon:
- 6.4890085
- epsg:
- EPSG:4326
- address:
- Nystøyl Kroken 11
- postnummer:
- 4755
- poststed:
- HOVDEN I SETESDAL
- kommunenummer:
- 4222
- kommunenavn:
- BYKLE
- lat:
- 59.5712011
- lon:
- 7.3599009
- epsg:
- EPSG:4326
Show all fields in HTML
- total_count:
- 23
- addresses:
23 results
- address:
- Kroken 11
- postnummer:
- 1466
- poststed:
- STRØMMEN
- kommunenummer:
- 3205
- kommunenavn:
- LILLESTRØM
- lat:
- 59.956234
- lon:
- 11.0219154
- epsg:
- EPSG:4326
- address:
- Kroken 11
- postnummer:
- 7860
- poststed:
- SKAGE I NAMDALEN
- kommunenummer:
- 5047
- kommunenavn:
- OVERHALLA
- lat:
- 64.459315
- lon:
- 11.7714609
- epsg:
- EPSG:4326
- address:
- Kroken 11
- postnummer:
- 3632
- poststed:
- UVDAL
- kommunenummer:
- 3338
- kommunenavn:
- NORE OG UVDAL
- lat:
- 60.3268934
- lon:
- 8.5093627
- epsg:
- EPSG:4326
- address:
- Kroken 11
- postnummer:
- 2609
- poststed:
- LILLEHAMMER
- kommunenummer:
- 3405
- kommunenavn:
- LILLEHAMMER
- lat:
- 61.1106597
- lon:
- 10.4674055
- epsg:
- EPSG:4326
- address:
- Kroken 11A
- postnummer:
- 2386
- poststed:
- BRUMUNDDAL
- kommunenummer:
- 3411
- kommunenavn:
- RINGSAKER
- lat:
- 60.890436
- lon:
- 10.945772
- epsg:
- EPSG:4326
- address:
- Kroken 11B
- postnummer:
- 2386
- poststed:
- BRUMUNDDAL
- kommunenummer:
- 3411
- kommunenavn:
- RINGSAKER
- lat:
- 60.8902431
- lon:
- 10.9462542
- epsg:
- EPSG:4326
- address:
- Kroken 52
- postnummer:
- 5713
- poststed:
- VOSSESTRAND
- kommunenummer:
- 4621
- kommunenavn:
- VOSS
- lat:
- 60.7792318
- lon:
- 6.4890085
- epsg:
- EPSG:4326
- address:
- Nystøyl Kroken 11
- postnummer:
- 4755
- poststed:
- HOVDEN I SETESDAL
- kommunenummer:
- 4222
- kommunenavn:
- BYKLE
- lat:
- 59.5712011
- lon:
- 7.3599009
- epsg:
- EPSG:4326
Will you use the result in generated code?
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
- 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
- If the result has coordinates, open the place page to combine this lookup with the other point-based services.
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.