Who has owned the property before?
Registered changes of ownership for a property, newest first: date, type, consideration and who bought and sold, the same basis a sales valuation starts from.
Nøkkelen virker i dag på Leietaker-API og dagens Data API; Placepoint API godtar samme nøkkel når det lanseres.
Prøv med et ekte bygg: Oslo S, Jernbanetorget 1
- Trial key with GitHub in under a minute
- One GET call
- Norway and Sweden
- Land registration data
- Newest first
ℹ️ The endpoint responds once Placepoint API has launched. The contract below is final; the Tenant API already responds.
From matrikkelnummer to registered sales
The transaction list shows how ownership of a property has developed over time. Banks use it to verify history before lending, agents for price documentation, and analysts to follow a portfolio of properties over several years.
The transaction type decides how the consideration should be read: only a real sale gives a reliable price indication, while inheritance, estate settlement and sectioning are transfers or administrative changes without a market price. Buyer and seller come as a company or a person; a person's name requires the owners.read scope, otherwise only the year of birth is returned when it is known, the same limit the owner lookup uses.
Transaction type decides the price
kindseparates a real sale from inheritance, estate settlement and sectioning, so you do not use an administrative transfer as a market price.Buyer and seller with organisation number
Companies come with organisation number and name directly; a person requiresowners.readfor the name, otherwise only the year of birth.Paginated for long histories
A property with a long history comes in several pages;nextPageTokenin the response fetches the next page.
Fields that actually say something
One GET call with the matrikkelnummer gives the transaction list below, newest first.
/properties/{country}/{cadastreId}/transactionscurl -X GET "https://data.placepoint.no/properties/NO/0301-207-76-0-0/transactions" \
-H "Authorization: Bearer $TOKEN"
svar · 200
{
"items": [
{
"id": "txn_8f3a1c",
"registeredAt": "2022-03-14T00:00:00Z",
"kind": "SALE",
"price": {
"amount": "12500000.00",
"currency": "NOK"
},
"share": {
"numerator": 1,
"denominator": 1
},
"buyers": [
{
"kind": "ORGANIZATION",
"organization": {
"organizationIdentifier": {
"scheme": "0192",
"id": "987654321"
},
"name": "Eufemia Eiendom AS",
"country": "NO"
},
"share": {
"numerator": 1,
"denominator": 1
},
"registeredAt": "2022-03-14T00:00:00Z"
}
],
"sellers": [
{
"kind": "PERSON",
"person": {
"birthYear": 1965
},
"share": {
"numerator": 1,
"denominator": 1
},
"registeredAt": "2022-03-14T00:00:00Z"
}
],
"source": "KARTVERKET_TINGLYSING"
}
],
"nextPageToken": "eyJvZmZzZXQiOjF9"
}
Three steps to your first response
Log in with GitHub
One click, under a minute, no payment card. The key comes back to this page.Call the endpoint
Replace$TOKENin the curl above. The call needs a country code and a matrikkelnummer; usenextPageTokento fetch more pages.Use the response
Filter onkindto separate real sales from inheritance and estate settlement before you use the consideration for anything.
Data and sources
Norwegian transactions come from Kartverket's Tinglysing (land registration), updated continuously. Swedish transactions come from Lantmäteriet via Combify.
See also
Questions and answers
How fresh is the data?
What do you cover?
kind field separates a real sale from inheritance, estate settlement and sectioning.Does it work in Sweden?
What about privacy?
owners.read scope for the name, otherwise only the year of birth when it is known, the same limit as the owner lookup.