Tinglysning property records

A property ID (BFE number) normally identifies one record in Tinglysning. Some properties, however, have separate records for the main property and for one or more shares. Use the property-records endpoint when you need complete coverage:

GET /dk/data/third-party/v1/tinglysning/property-records/{propertyId}

The endpoint always returns an array. It is not paginated because the records form the complete, finite set associated with one property ID rather than an open collection:

For the usual case, the array contains one record. That record has exactly the same property payload as the deprecated property lookup.
When Tinglysning associates several records with the property ID, the array contains one item per record.
If Tinglysning has no records for the property ID, the endpoint returns HTTP 404.

[
  {
    "id": "6fce341e-9a4c-4c4a-a05e-261dfe679ba8",
    "propertyId": 2073044
  },
  {
    "id": "9b723869-77d0-4909-87fe-bcc2dbb18890",
    "propertyId": 2073044
  },
  {
    "id": "e3bc3bd8-5830-40ef-b7ba-edc10dc989e0",
    "propertyId": 2073044
  }
]

The example includes all three records but abbreviates the fields on each record. See the DK Data API reference for the complete response schema, authentication requirements, and error responses.

Migrating from the property lookup

GET /dk/data/third-party/v1/tinglysning/properties/{propertyId} is deprecated. Replace it with the property-records route and process every item in the returned array. Code that previously consumed a single property object should read the first item only if the business process intentionally ignores additional Tinglysning records.

This lookup change does not alter DataHub source streams or the documents delivered through them.

Migrating from the property lookup​

Migrating from the property lookup