Placepoint API guide

The Placepoint API is a REST API for property, company and area data in Norway and Sweden: matrikkelnummer and fastighetsbeteckning lookups, owners, tenants, transactions, building permits, valuations, zoning and more, plus webhooks for change events. It uses OAuth2 client credentials, JSON bodies, cursor pagination and RFC 9457 error responses throughout.

Base URL and contact

The API is served from https://data.placepoint.no; api.placepoint.no becomes the host once the PropCloud APIs behind it are shut down.

Contact: support@placepoint.no.

This guide covers the parts that apply across the whole API. For request and response shapes, parameters and examples on a specific operation, use the operation pages listed under Every operation.

In this guide

• Quickstart: a token, a property lookup, tenants, and a webhook subscription in under 10 minutes.
• Authentication: the client-credentials grant, scopes, and getting a trial key.
• Identifiers: matrikkelnummer, fastighetsbeteckning, organization schemes and address encoding.
• Pagination and filtering: pageSize, pageToken, and which operations page.
• Errors: the Problem Details body and the response types the spec uses.
• Webhooks: CloudEvents payloads, signature verification, subscriptions.
• Rate limits and quotas: rate-limit headers, the daily call cap, idempotency.
• Sandbox: the demo properties a trial key can reach, until there is a separate sandbox host.
• API lifecycle: what may change without notice, what counts as breaking, and the deprecation and sunset timeline.
• Changelog: every change to the contract, newest first, with the version it shipped in.

Every operation

Generated from the spec; each row links its reference page for parameters, fields and examples.

Method	Path	Scopes
GET	/.well-known/api-catalog	public
GET	/openapi.yaml	public
GET	/addresses/{country}/{address}	properties.read
GET	/coordinates/{country}/{lat}/{lon}	properties.read
GET	/properties/{country}/{cadastreId}	properties.read
GET	/properties/{country}/{cadastreId}/sections	properties.read
GET	/properties/{country}/{cadastreId}/buildings	properties.read
GET	/properties/{country}/{cadastreId}/units	properties.read
POST	/properties/{country}/lookups	properties.read
GET	/properties/{country}/{cadastreId}/owners	properties.read
GET	/properties/{country}/{cadastreId}/tenants	properties.read
GET	/properties/{country}/{cadastreId}/transactions	properties.read
GET	/properties/{country}/{cadastreId}/comparable-transactions	properties.read
GET	/properties/{country}/{cadastreId}/valuations	properties.read
GET	/properties/{country}/{cadastreId}/energy-certificates	properties.read
GET	/properties/{country}/{cadastreId}/certifications	properties.read
GET	/properties/{country}/{cadastreId}/zoning-plans	properties.read
GET	/properties/{country}/{cadastreId}/utilization	properties.read
GET	/properties/{country}/{cadastreId}/building-permits	properties.read
GET	/properties/{country}/{cadastreId}/encumbrances	properties.read
GET	/properties/{country}/{cadastreId}/risks	properties.read
GET	/properties/{country}/{cadastreId}/housing-cooperative	properties.read
GET	/properties/{country}/{cadastreId}/documents	properties.read
GET	/properties/{country}/{cadastreId}/boundary	properties.read
GET	/properties/{country}/{cadastreId}/buildings/{buildingNumber}/footprint	properties.read
GET	/companies/{scheme}/{id}	companies.read
GET	/companies/{scheme}/{id}/properties	companies.read
GET	/companies/{scheme}/{id}/employees	companies.read
GET	/companies/{scheme}/{id}/roles	companies.read
GET	/companies/{scheme}/{id}/shareholders	companies.read
GET	/companies/{scheme}/{id}/group-structure	companies.read
GET	/companies/{scheme}/{id}/financial-statements	companies.read
GET	/companies/{scheme}/{id}/premises	companies.read
GET	/companies/{scheme}/{id}/documents	companies.read
GET	/areas/{country}/{areaId}/statistics	areas.read
GET	/areas/{country}/{areaId}/land-allocations	areas.read
GET	/subscriptions	subscriptions.write
POST	/subscriptions	subscriptions.write
DELETE	/subscriptions/{subscriptionId}	subscriptions.write
POST	/auth/token	public
GET	/auth/me	token only

Some fields on owners, buyers and sellers are personal data and require the owners.read scope on top of the scope for the operation itself; without it, the field is omitted.

What may change without a new major version

The contract grows. Write clients that tolerate growth, and a new field or a new classification value never breaks them:

• New response fields appear. Ignore what you don't read; don't reject a response because it carries a property you don't know.
• Classification values grow. Document.kind, Certification.scheme and the webhook event types are marked x-extensible-enum in the spec: the documented values are the ones we serve today, and more follow as new registers and schemes are connected. Map an unknown value to your own fallback rather than failing the parse.
• Request enums stay closed. A value we accept today keeps working; that is the half of the contract you can hard-code against.

What will not happen inside a major version: a field removed or renamed, a type changed, a required request parameter added, or an endpoint withdrawn. info.version in the spec is semver, and every change is listed in the release notes.