Skip to content

DOCUMENTATION

Data and models through REST APIs and MCP.

Trial access on request · 100 lookups over 14 days · no payment card required

Request trial access and we open your account with 100 lookups over 14 days. Connect internal systems through REST and AI agents through MCP. Each API has its own reference with parameters, responses and error codes, generated from the contract the API actually serves.

The field lists are not the important part. The caveats are: what a value does not mean. Read an empty section together with source status and coverage; it does not establish absence of hazard.

API version
1.33.0
Sections
248
Fields
3,856
With public demo fields
172
Contents

Getting started

  1. Request access. Request trial access — trial access is opened after a short request. We open your account, the same one as for every Approach service.
  2. Get a trial key under Account → Datakilde: the trial has 100 requests that count as lookups, over 14 days, with the open fields from the demo. The key is shown once: keep it in the APPROACH_API_KEY environment variable on your server, never in browser code or source control.
  3. Make the first call. Search is free and does not count as a lookup. The answer is address candidates; let the user choose, and use the address_id from there.
    curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
      -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
      'https://api.approach.no/api/v1/addresses/search?q=Storgata+1'
  4. Read the coordinates. Every search candidate, and the address object at the top of every address profile (also from /resolve), carries the point in two systems: lat and lon in WGS84 degrees for maps and geocoding, and easting_utm33 and northing_utm33 in metres, EPSG:25833, which are Kartverket's authoritative coordinates. coordinate_system in the response names the UTM system. The address_details section carries the same four fields.
    curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
      -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
      'https://api.approach.no/api/v1/addresses/search?q=Storgata+1' \
      | jq '.candidates[] | {address_id, lat, lon, easting_utm33, northing_utm33}'

Try it without a key

The response below is what the API returned just now — not a sample that was correct once. Every section has the same button on its own page.

Where are the address fields in JSON?

Street, house number, postal area and coordinates are in address at the top of the authenticated profile response, for example address.street_name. The public demo also presents this open address identity as address_details. With full field policy, sections.address_details.records instead has a separate contract for cadastral identifiers and coordinates; do not expect all street and postal fields there.

imported_at is local import time, not proof of upstream freshness. Missing or null values do not mean the information is verified. Access and field policy still apply to each section.

The same call in your language

The same four languages and the same code as the playground on the account page. The key is read from the environment.

curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/search?q=Storgata+1'

Reading the answer

Every section carries its own status and freshness. Branch on them before using a value: available means the section returned records, not_found that the available data yielded no records for the address, unavailable that the section could not be read, and restricted that the key has no grant for it. Check reason and coverage; an empty section is not an absence in the world. Every value explained.

Full answer or a subset

With no choice you get the default package, core. Ask for specific sections with sections=a,b, a package with package=<id>, or everything with package=all. A subset is faster but costs the same single lookup per subject per day. Read the full guide.

Keys and sign-in

Your account session renews automatically during session checks for up to seven days after sign-in. Then sign in again. Signing out ends that session; resetting your password ends all sessions.

API keys are separate from your sign-in and do not refresh automatically. Use Rotate on the account page: you get a new key, and the old one keeps working for 24 hours so you can swap it in. To stop the old key at once, choose that in the same dialog. Sign-out and password changes do not revoke API keys. If a key may have leaked, revoke it immediately.

Keys belong to the person who created them, even when using the company agreement. Before that person leaves or deletes their account, have another administrator create a replacement key, update and test the integration, then revoke the old key.

For an error, include the time, endpoint, HTTP status and Request ID from Usage & logs. Never send API keys or passwords.

Company pilot and new data

Start with one use case and five priority fields. Agree 20–50 test addresses, data access and a suitable allowance with us before building your prototype. The standard trial does not unlock every catalogue field.

Tell us which fields are missing, how often they need updating and how you intend to use them. New sources and improved coverage are prioritised by need, quality and usage rights; the catalogue describes what is available now.

Contact us about a pilot, new data or support

From an AI assistant (MCP)

The hosted MCP server exposes Datakilde tools with the same access and usage limits as an API key. Its endpoint is https://mcp.approach.no/mcp and it requires Authorization: Bearer with a personal Datakilde key. An unauthenticated connector does not provide access.

Claude · personal connector

Claude offers custom remote MCP connectors on Free (one connector), Pro, Max, Team and Enterprise, and documents fixed request headers for API keys. On Team and Enterprise, an owner must first add the connector for the organization. Add the MCP URL https://mcp.approach.no/mcp and an Authorization header with Bearer and your personal Datakilde key. The connection has not been tested end to end yet.

Use only your own personal connector and keep the API key private. Do not put a personal key in a shared Team or Enterprise connector: everyone using it would receive the key’s Datakilde access.

Open Claude Connectors · Open Claude’s official guide to custom MCP connectors

ChatGPT · custom MCP

OpenAI lists custom MCP server connections for ChatGPT Business and Enterprise/Edu on the web. Workspace permissions apply. Datakilde requires a Bearer key but does not yet provide per-user OAuth for MCP, so it cannot be connected safely to ChatGPT. Do not choose “No authentication” or paste or share a personal key.

Read OpenAI’s official setup guide

Use the details below only in MCP clients that securely support a personal Bearer header. ChatGPT cannot use this static key; wait until Datakilde offers OAuth for ChatGPT.

URL: https://mcp.approach.no/mcp
Authorization: Bearer $APPROACH_API_KEY

$APPROACH_API_KEY is a placeholder, not a key. The client replaces it only if it explicitly supports environment variables; otherwise store your personal key in the client’s secure secret store. No npm package has been published yet; the OpenAPI document can be used to generate a regular API client.

Store the key in the client’s secret manager; do not put it in a URL, conversation, screenshot or public code. A generic HTTP client that supports an Authorization header is not by itself a verified Claude integration.

Read-only does not mean free: lookups can count toward subscription quotas and billing. Tool annotations are client hints, not permission or a guarantee of confirmation. Require the assistant to obtain your explicit confirmation before starting or stopping watches; these actions change the account and can affect billing. Check the client’s approval settings before use.

The APIs

A Datakilde key can reach several APIs when both section access and the product plan allow it. Projects has dedicated keys. A key is not a subscription; purchased capacity does not unlock agreement-gated fields.

APIWhat it providesKey and accessMeasured inContract
AddressesAddress and property lookups, 248 sectionsDatakilde key · address sectionslookupOpenAPI
CompaniesCompany lookups by organisation numberSame key · company sectionslookupOpenAPI
Company watchAlerts for companies you watch, by webhookSame key · separate watch subscriptionwatched company per monthOpenAPI
RegionsMunicipal and county dataSame key · region sectionslookupOpenAPI
Series98 open time seriesSame key · separate series allowancestarted 1 000 data pointsOpenAPI
ObservationsTraffic, weather and water level at an address as a time series and profileSame key · the address section the variable belongs topart of the address lookupOpenAPI
Data productsReady answers for an address, a list or a whole areaSame key · address sections and product plancellOpenAPI
SwedenA point in Sweden: municipality, flood maps, wells, protected nature and warningsSame key · Sweden capabilitylookupOpenAPI
ModelsApproach's calculations for an address or a point: noise, natural hazards and moreSame key · models capabilitylookup per modelOpenAPI
ProjectsSourced project proposals in the account workspaceDedicated Projects key · active subscriptionprofile reads · separate monthly allowanceWorkspace

The datasets API (whole tables with incremental sync) has its own access and, for now, only its OpenAPI contract.

Datakilde Projects · account workspace

A sourced slice of Oslobygg KF’s 2027 investment proposal. The workspace requires an active Projects subscription and dedicated Projects keys. Address API keys do not grant access. Its API base is /v1/datakilde/projects/api.

Open the Projects workspace

Authentication

Send the key in the X-API-Key header on every call. Keys are issued per organisation with explicit per-section grants; a package never grants access to a new source. A call without a valid key gets 401 with a WWW-Authenticate header, and a reason field saying why the key was refused.

X-API-Key: $APPROACH_API_KEY

Keep the key on your server. Browser code, mobile apps and source control are where keys leak from. /access shows what your key may read and when access expires.

IP allowlist

A key can be restricted to up to 50 IPv4 or IPv6 addresses and CIDR ranges, when it is created or later under Keys on the account page. The address compared is the one the API sees as the caller (behind our proxy: the address the proxy wrote, never an X-Forwarded-For header the client sent itself). A call from any other address gets 403 ip_not_allowlisted with the address the API saw in client_ip, and is neither counted nor billed. An empty list means no restriction. Changes apply within about 15 seconds. Keys with an IP allowlist cannot be tested in the API tester on the account page.

What counts as a lookup

A lookup is one address (or one company or region) per organisation per calendar day, Oslo time. Fetching an address’s profile, two of its sections and its history on the same day is one lookup. Only successful (2xx) responses count: a failure on our side, a 429 or a 4xx is never counted.

CallCounts?
GET /addresses/{id}, /{id}/sections/{s}, /{id}/historyyes, per address
GET /companies/{id}, /{id}/profile, /{id}/sections/{s}yes, per company
GET /regions/{id}, /{id}/sections/{s}yes, per region
GET /addresses/search, /propertiesno, free
POST /addresses/resolvefree when it only identifies the address (address_details); otherwise one lookup, the same as GET /addresses/{id}
/access, /usage, /catalog, /openapi.jsonno, free
Series, data products, company watchtheir own units, see each API

Trial access on request · 100 lookups over 14 days · no payment card required. Trial lookups cover addresses, companies and regions. In self-service trial and prepaid access, test calls do not spend that allowance but have a daily cap. Contracted business subscriptions may have different test limits and may count test lookups beyond a free monthly allowance after billing starts. Test keys use the same API and data, not a separate test environment. A lookup where more than 20% of the requested sections failed on our side is not counted; X-Request-Billing then says not_billed_partial_failure. A lookup where no requested section returned data is not counted either (not_billed_no_data). Pricing and bundles.

Limits

Each grant has a number of requests per minute (the trial has 60). X-RateLimit-Limit, -Remaining and -Reset are on the responses; past the limit the API answers 429 rate_limit_exceeded with Retry-After in seconds. Wait that long before retrying. A new key does not give a new limit or a new allowance: both belong to the organisation.

When the allowance is spent, the API answers 402 with a code saying why: request_allowance_exhausted, monthly_safety_cap_reached or product_plan_required. X-Request-Budget and X-Request-Budget-Remaining show where you stand. Every error code · Every response header

Pagination

Both section and property endpoints paginate. Send next_cursor as cursor with the same filters. Section cursors bind to an address and section; property cursors bind to a property. Source-checked property pagination also requires matrikkelenhet_id. A cursor used anywhere else gets 400 invalid_cursor.

Status and freshness

HTTP 200 does not confirm that every section succeeded. Each section answers for itself; a failure does not take the rest with it. partial can also be true when returned data are stale or have no usable values, or a supporting calculation is missing. Read section status, freshness, quality and error alongside partial_reasons and failed_sections; an empty failed_sections list does not establish complete coverage.

status

ValueMeaning
availableThe source answered and there is at least one record on this page.
not_foundThe source was queried and returned no records for this address. For spatial layers this only describes the locally loaded dataset and its coverage, not every mapped area or an absence of hazard. Sections that map areas (the district, concession or service area an address lies in) also carry reason, from not_found_reasons, saying what the absence means; they never substitute the nearest area.
restrictedThe calling credential has no grant for this section. No records are returned and none were read.
unavailableThe section could not be read. error says why: source_not_loaded means the table has not been collected yet, source_empty means it was collected and holds no rows anywhere (a warning feed with no active warning is empty, not broken), source_read_access_missing means the API role cannot read it, source_timeout means the query did not finish, source_schema_outdated means a collector has not yet upgraded the table. None of these say anything about the address.

freshness

ValueMeaning
cachedInterpret with freshness_basis. With record basis, the source record timestamp is within the section's maximum age. With collection basis, the last successful producer collection is within that budget; this does not establish the publisher's data age unless source_as_of is available.
liveRetrieved directly from the source for this lookup. This describes retrieval, not the age or completeness of the source records.
staleInterpret with freshness_basis. With record basis, the source record timestamp exceeds the section's maximum age. With collection basis, the last successful producer collection exceeds that budget; this does not establish the publisher's data age. Records are still returned.
unverifiedThe applicable age clock cannot establish age. Consult freshness_basis and quality reasons; a collection clock does not establish the publisher's data age. Not a claim that the data is current.