Sensor proximity

traffic_sensor_links3 fields3 of these fields open in the demo

Source: Approach geometric matching
Geography: The address point
Reported stale after: 30 days
Access: Requires an API key granted this section
Contract version: 1

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.

Straight-line EPSG:25833 distances to traffic sensors within 5 km. No driving distance and no road-relevance guarantee.
This is the identity-and-distance list; the sensors' own observations are in the traffic section, computed from the same match.

Fields

2 of 3 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
sensor_id	string \| null	context	open
sensor_name	string \| null	value	open
straight_line_distance_m	integer \| null (m)	value	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=traffic_sensor_links'

# 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/traffic_sensor_links?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.