Fire and burglary exposure indices for the address, with every factor shown

fire_and_burglary_indicators10 fields4 of these fields open in the demo

Source: Approach, composed from Matrikkel, SEFRAK, NVDB, BRREG, SSB, Politiloggen and KOSTRA fields
Geography: The address point
Reported stale after: 30 days
Access: Requires an API key granted this section
Contract version: 1
In packages: hazard_screen, models

Available with: trial key (open fields) · bought bundle or agreed plan (all fields) · Pricing

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.

Two 0-100 indices, higher is more exposed, each the sum of documented factor points (fire_factors, burglary_factors) over the inputs listed; a factor whose input is missing contributes 0, never a mid-scale default. They rank addresses against each other and are NOT probabilities: no open register holds fire or burglary outcomes per address to calibrate against (DSB and SSB publish per kommune, the police per district). fire_coverage and burglary_coverage are the share (0-1) of the 8 factors on each side that had a real observation rather than a missing input contributing 0 — a low-coverage index is thin evidence, not a low-exposure address. municipal_scope_inputs names the inputs keys (inside `inputs`) that are kommune-wide KOSTRA/SSB rates rather than this address's own history. method names the weighting version; a fitted model replaces it when a partner supplies claim outcomes.
inputs.theft_burglary_90d_5km counts Politiloggen theft and burglary messages whose named settlement, grunnkrets/bydel neighbourhood or postal area has its centre within 5 km of the address. Politiloggen gives no incident position; kommune-centroid-only messages are excluded. A neighbourhood centre is approximate and does not establish that the incident occurred within 5 km. inputs.police_log_match_share is the fraction of the kommune's own theft/burglary messages in the same 90 days matched by those same settlement, neighbourhood or postal methods. A zero count beside low matching coverage is missing placement evidence, not proof that no incidents occurred.

Fields

6 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” return values to anonymous callers; the rest require a key.

Field	Type	Role	Demo
fire_index	integer \| null	value	open
fire_factors	object \| null	value	—
fire_coverage	number \| null	value	—
burglary_index	integer \| null	value	open
burglary_factors	object \| null	value	—
burglary_coverage	number \| null	value	—
municipal_scope_inputs	array<string> \| null	context	—
inputs	object \| null	context	—
method	string \| null	context	open
computed_at	string \| null	context	open

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 --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=fire_and_burglary_indicators'

# paginated, one section at a time
curl --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/fire_and_burglary_indicators?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.