Electricity price zone (elspot)

power_price_zone7 fields7 of these fields open in the demo

Source: NVE Elspotområder
Geography: Around the address
Reported stale after: 400 days
Access: Requires an API key granted this section
Contract version: 1
In packages: planning_restrictions

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

The source polygons are generalised land outlines, so a coastal or island address can lie just outside every polygon. The nearest area is returned so such an address still gets its zone; contains_address false means the point was not strictly inside it.
Straight-line EPSG:25833 distances from the address point to the feature; not travel distance. Source features are imported as published, with their own accuracy and update cadence; updated_at is our import time.

Fields

2 of 7 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” return values to anonymous callers; the rest require a key.

Field	Type	Role	Demo
feature_id	string \| null	context	open
label	string \| null	context	open
municipality_code	string \| null	context	open
updated_at	string \| null	context	open
price_zone	string \| null	context	open
straight_line_distance_m	integer \| null (m)	value	open
contains_address	boolean \| null	value	open

Fetch this section

curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643?include=power_price_zone"

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643/sections/power_price_zone?limit=25"

Try it now

This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.