Registered businesses around the address
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.
- Active enheter in the Enhetsregister whose business address matched an address point (about 84 % of them; c/o and post-box addresses do not). Counted by NACE division at the registered address, which for a chain is the shop and for a holding company an office; employees are the registered headcount. Nearest grocery is NACE 47.11, pharmacy 47.73, eatery 56.10/56.30, gym 93.13, within 5 km, straight-line.
- Where nearest_*_source is osm the name and position come from OpenStreetMap (© OpenStreetMap contributors, ODbL 1.0, share-alike): they need that attribution, and the OpenStreetMap-sourced fields cannot be folded into a dataset passed on under other terms. Where it is brreg the figure is from Enhetsregisteret.
Fields
22 of 28 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 |
|---|---|---|---|
| companies_500m | integer | null (count) | value | open |
| employees_500m | integer | null (count) | value | open |
| shops_500m | integer | null (count) | value | open |
| eateries_500m | integer | null (count) | value | open |
| health_500m | integer | null (count) | value | open |
| education_500m | integer | null (count) | value | open |
| personal_services_500m | integer | null (count) | value | open |
| companies_1000m | integer | null (count) | value | open |
| employees_1000m | integer | null (count) | value | open |
| shops_1000m | integer | null (count) | value | open |
| eateries_1000m | integer | null (count) | value | open |
| health_1000m | integer | null (count) | value | open |
| education_1000m | integer | null (count) | value | open |
| nearest_grocery_name | string | null | value | open |
| nearest_grocery_kind | string | null | context | — |
| nearest_grocery_source | string | null | context | open |
| nearest_grocery_distance_m | number | null (m) | value | open |
| nearest_pharmacy_name | string | null | value | open |
| nearest_pharmacy_source | string | null | context | open |
| nearest_pharmacy_distance_m | number | null (m) | value | open |
| nearest_eatery_name | string | null | value | open |
| nearest_eatery_kind | string | null | value | open |
| nearest_eatery_source | string | null | context | open |
| nearest_eatery_distance_m | number | null (m) | value | open |
| nearest_gym_name | string | null | value | open |
| nearest_gym_source | string | null | context | open |
| nearest_gym_distance_m | number | null (m) | value | open |
| updated_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=local_businesses' # 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/local_businesses?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.