Skip to content

← All sections

Current NVE and MET hazard warnings for the municipality

Current NVE and MET hazard warnings (flood, landslide, avalanche, weather) valid now for regions that include the address's kommune, with danger level, validity period and advice.

hazard_warnings10 fields10 of these fields open in the demo
Source
Varsom.no / MetAlerts
Geography
Municipality
Reported stale after
2 hours
Access
Requires an API key granted this section
Contract version
1
In packages
safety, prevention_context, hazard_screen, fire_and_damage

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
22 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 22 Nov 2026
Newest record
22 Nov 2026

Measured 22 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.

Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing

Source terms and reuse

These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.

Declared licence or terms
unverified
Declared redistribution
Not established
Catalogue basis
Unverified

API warnings

The API returns these notes in warnings.

  • Regional warnings (flood, landslide, avalanche, weather) whose validity interval includes now for regions that include this municipality. Future, expired and unknown-validity warnings are excluded from this current section; retained history is not an active warning. No result means no matching active warning in our latest fetch, not safe conditions or confirmation that the source is current.

Provider-contract fields

2 of 10 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” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.

FieldTypeRoleDemo
warning_idstring | nullcontextopen
warning_typestring | nullvalueopen
region_namestring | nullcontextopen
danger_levelinteger | nullvalueopen
danger_level_namestring | nullcontextopen
valid_fromstring | nullcontextopen
valid_tostring | nullcontextopen
main_textstring | nullcontextopen
advice_textstring | nullcontextopen
updated_atstring | nullcontextopen

Fetch this section

Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.

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/285717643?include=hazard_warnings'

# paginated, one section at a time
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/285717643/sections/hazard_warnings?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.