Every building on a Danish property, in one call

Request

One call on the BFE number

The same request in four languages. The typed @grundfast/sdk retries transient upstream failures for you.

import { GrundfastClient } from '@grundfast/sdk';

const gf = new GrundfastClient({ apiKey: process.env.GRUNDFAST_API_KEY! });
const property = await gf.ejendom(5651067); // Solbakkevej 70, Silkeborg

for (const b of property.bygninger) {
  console.log(b.bygningsnummer, b.anvendelse?.tekst, b.opfoerelsesaar, b.om_tilbygningsaar);
}

{
  "type": "ejendom",
  "bfe_nummer": 5651067,
  "kommunekode": "0740",
  "antal_bygninger": 3,
  "bygninger": [
    {
      "bygningsnummer": 1,
      "anvendelse": { "kode": "120", "tekst": "Fritliggende enfamiliehus" },
      "opfoerelsesaar": 1958,
      "om_tilbygningsaar": null,
      "antal_etager": 1,
      "areal": {
        "bebygget_m2": 116,
        "samlet_bygningsareal_m2": 116,
        "samlet_boligareal_m2": 95
      },
      "materialer": {
        "ydervaeg": { "kode": "1", "tekst": "Mursten" },
        "tag": { "kode": "5", "tekst": "Tegl" }
      },
      "varme": {
        "installation": { "kode": "1", "tekst": "Fjernvarme/blokvarme" }
      },
      "fredning": {
        "fredet": false,
        "status_tekst": "ingen_registrering",
        "bevaringsvaerdi": null,
        "kilde": "fbb"
      },
      "geometri": {
        "type": "Point",
        "coordinates": [9.532961, 56.1578452],
        "epsg25832": [533103.83, 6223775.44]
      },
      "enheder": [
        {
          "anvendelse": { "kode": "120", "tekst": "Fritliggende enfamiliehus" },
          "areal": { "samlet_m2": 95 },
          "antal_vaerelser": 4
        }
      ]
    }
  ]
}

What you get

What the register knows, in a shape you can use

Datafordeler serves BBR as separate entities with numeric codes. One lookup here assembles the property and resolves it — and says plainly where the source has no answer.

• Codes resolved, code kept

  Use, wall, roof and heating arrive as { kode, tekst } from BBR’s code lists: the text for people, the code for your logic.

• The whole property at once

  Every building on the BFE with its units, joined across BBR’s entities, and an index pointing at the main building.

• Rebuild year, not just build year

  BBR field 209 — the latest major rebuild or extension. It matters for an asbestos or energy screening, where the build year alone says too little.

• Heritage status joined

  Listed status and SAVE value from the heritage register, matched on the building’s ID because BBR does not carry them.

Response

Fields in the answer

Field names are BBR’s own Danish terms, glossed here; every one is described in the English API reference.

Endpoints

BBR, five ways

Same key, same billing. Parameters and every field are in the API reference.

GET/v1/bbr/ejendom/:bfe

The property’s buildingsEvery building and unit, codes resolved, heritage status joined, parcels and valuation alongside.

GET/v1/bbr/ejendom/:bfe/geojson

The same, as GeoJSONA FeatureCollection with one feature per building, ready for a map.

POST/v1/bbr/ejendom:batch

Many properties per callPro and upUp to 50 BFE numbers per request on Pro (100 on Scale, 150 on Enterprise), one call per distinct BFE.

GET/v1/bbr/ejendom/:bfe?asOf=

As it stood on a dateScale and upThe property as the register recorded it on an earlier date; /historik gives the sequence of changes.

GET/v1/kodeliste/:navn

The code listsBBR’s official code lists as code → text, e.g. bygningsanvendelse. No key needed.

Beyond BBR

The same BFE opens the rest of the property

BBR is the buildings. The parcels underneath are in the cadastre API, and the public valuation, terrain, soil classification, protection lines and zoning are all keyed on the same number — see the property data API.

FAQ

Questions about the BBR data