Placepoint API overview
One REST API over property data for Norway and Sweden: cadastres, buildings, owners, tenants, transactions, companies and areas. The cadastre number is the key that ties them together, so an address lookup leads to the property, the buildings on it, the companies registered there, and what it last sold for. The same data serves the map, the map layers and the property panel in Placepoint Fusion.
Requests go to data.placepoint.no. Responses are JSON, authentication is OAuth2 client credentials, and every list endpoint pages and filters the same way.
Where to go next
| Read this | For |
|---|---|
| API guide | Authentication, identifiers, pagination and filtering, errors, rate limits, the sandbox, the lifecycle policy and the changelog. |
| Endpoint reference | Every operation with its parameters, request body and response schema, generated from the OpenAPI contract. |
| Product pages (Norwegian) | What each group of endpoints answers, the fields worth knowing about, and a GitHub sign-in that returns a trial key to the page you are on. |
What may change
The contract grows additively: new fields and new endpoints arrive without notice, and a value set that grows is declared as such so a client with a closed parser does not break on a new value. Breaking changes never land in place; they get a new major version and a deprecation window. The rules are written out under What may change without a new major version, and every version bump is listed in the changelog.
Access
A trial key from GitHub sign-in answers today against the Leietaker-API and the Data API, and it is the same key the Placepoint API accepts at launch. Production credentials and coverage for the whole country are agreed with us: placepoint.no/selskap/kontakt.