A complete API platform for everything in property, buildings and companies in Norway and Sweden
Placepoint API brings property, buildings, companies, ownership and transactions together behind one authenticated surface. One key, one contract and the same data as Placepoint Fusion.
Nøkkelen virker på Placepoint API og på dagens Data API, 35 kall om dagen i 14 dager.
Prøv med et ekte bygg: Tordenskiolds gate 2
- Test in under a minute
- One REST API
- JSON
- Norway and Sweden
- Kartverket and BRREG data
Are you integrating? The technical reference with endpoints, authentication and error codes is in the developer documentation.
- 3.5 millionmatrikkelenhet units in Norway
- 1.1 millionactive companies
- 30 millionownership records
- 4.2 millionfastigheter in Sweden
- 240,000registered changes of ownership a year
Every figure is checked against the source and explained on Placepoint in numbers.
Eleven product areas. One key.
Each box is a set of endpoints with the same key and the same response format. The matrikkel number is the key everywhere: from address to property, on to buildings, owners, the companies based there, and what the property last sold for. You do not maintain the link yourself. The badge on each box says how far the area has come: "Live" is in production, "Beta" responds too, but the contract can still change, and "Coming" is not connected yet. The same data sits behind the map, the map layers and the property panel in Placepoint Fusion.
Addresses and coordinates
LiveFrom address text or a point to the property that covers it, in Norway and Sweden.
Property, buildings and boundaries
LiveThe property by matrikkel number, with buildings, units, housing coops and geometry as GeoJSON.
Owners
LiveRegistered owners recorded on the property, company or person, with share and date.
Tenants
LiveThe companies with a registered business address on the property, with industry and employees.
Transactions and valuation
LiveRegistered changes of ownership, comparable sales nearby and estimated market value with a range.
Zoning and building cases
LiveZoning plans with permitted and built utilisation, building cases and the documents behind them.
Encumbrances and natural hazards
LiveMortgages, easements and restrictions on disposal from Grunnboken, and rated risk of flooding, landslide, quick clay and radon.
Energy and environment
LiveEnergy certificates and environmental certifications such as BREEAM-NOR, per building.
Companies
LiveThe company by organisation number, with roles, shareholders, conglomerate, accounts and the premises it uses.
Areas
ComingStatistics for a municipality, grunnkrets or postcode, and Swedish markanvisningar.
Alerts
ComingSubscribe to changes for a property or a company, delivered as webhooks.
Get an API key and test the API in under a minute
Three steps, in this order. No procurement process before the first call.
Log in with GitHub
One click, under a minute, no payment card. The key comes back to this page and is filled into the examples.
See what is there
GET /.well-known/api-catalogand/openapi.yamlrespond without a key: the whole catalogue, which scope each endpoint requires, and the contract your client can be built from.Call it
All responses are JSON. Lists are paginated with
pageToken, errors come as Problem Details with a stable code and request id, and a limit responds429withRetry-After.
This is what a response looks like. Permitted, built and remaining UFA on the plot, one call. The figure is not in any register. We calculate it from the zoning plan and the buildings that stand there.
/properties/{country}/{cadastreId}/utilizationcurl -X GET "https://data.placepoint.no/properties/NO/0301-209-369-0-0/utilization" \
-H "Authorization: Bearer $TOKEN"
svar · 200
{
"allowedBya": 60,
"allowedBraM2": 9200,
"builtBraM2": 8400,
"remainingBraM2": 800,
"basis": "Regulert i S-5028, felt B13"
}
Public data, continuously updated. And large volumes of data others do not have.
Public registers are collected on a schedule and reconciled against each other, so a company that moved last week points to the right building this week. On top sit the links and the calculated layers we build ourselves: ownership across company and property, tenants per building, utilisation, valuation and comparable sales. The scope is on Placepoint in numbers. Each dataset, where it comes from and how often it is updated, is on Data and sources, with one page per vendor. What the map layers show is what the API delivers.
Norwegian registers and agencies
Kartverket Brønnøysundregistrene (BRREG) Statistisk sentralbyrå (SSB) Norges vassdrags- og energidirektorat (NVE) Norges geologiske undersøkelse (NGU) Miljødirektoratet Enova SF Statens vegvesen Direktoratet for samfunnssikkerhet og beredskap (DSB) Riksantikvaren Artsdatabanken Norsk institutt for bioøkonomi (NIBIO) Landbruksdirektoratet Fiskeridirektoratet Sokkeldirektoratet (Oljedirektoratet) Nasjonal kommunikasjonsmyndighet (Nkom) Utdanningsdirektoratet (Udir) Entur Posten Bring Klima- og miljødepartementet (KLD) Kultur- og likestillingsdepartementet (KUD) Oslo kommune Bergen kommune
Swedish sources
Distributors, certification bodies and our own datasets
Test free, pay for what you need
The base package with property, company and areas is included in all paid plans. Personal data and specialist data come as add-ons, so a valuation integration does not pay for other people's personal lookups. The price depends on which add-ons you turn on, the volume you expect and how long you commit for. Send us those three through the contact form, and you get a written quote back.
Free
Evaluation, prototype or student project.
0 kr
- GitHub login, no payment card
- 35 calls a day
- Open endpoints and demo properties
- Key valid for 14 days, renewable
- No agreement, no data processing agreement
- Most common
API add-on
You already use Placepoint and want the data in your own systems.
On request
- Annual agreement
- The full base package
- 120 calls a minute
- No daily limit
- Add-ons on request
- Support through your account manager
Standalone
You want the API without the Placepoint application.
On request
- Annual agreement
- The full base package
- 120 calls a minute
- Kick-off meeting with our developers
- Add-ons on request
Enterprise
High volume, personal data or the right to redistribute.
Negotiated per agreement
- Everything in Standalone
- Personal data (five endpoints, requires a data processing agreement)
- Higher page size and volume
- Signed data processing agreement and agreed uptime
- A named contact and input to the roadmap
What separates the plans
| Free | API add-on | Standalone | Enterprise | |
|---|---|---|---|---|
| Calls a day | 35 | No limit | No limit | No limit |
| Calls a minute | 120 | 120 | 120 | Negotiated |
| Open endpoints | Yes | Yes | Yes | Yes |
| Property and company data | Demo properties | Yes | Yes | Yes |
| Personal data | No | Add-on, requires a data processing agreement | Add-on, requires a data processing agreement | Included |
| Largest page | 50 | 50 | 50 | 100 |
| Swedish data | No | Beta | Beta | Beta |
| Uptime in the agreement | No | No | On request | Yes |
Paid plans run as annual agreements. A longer commitment and payment in advance bring the price down. Build against the free plan while you wait for the quote.
See also
Placepoint Fusion is the map surface over the same data:
- The map interface
- Map layers
- The property panel
- The building panel
- The company panel
- Search
- Reports
- Datasets
- Projects
- Tags
The same data without code:
Scope and sources:
For developers:
Questions and answers
How quickly can I get started?
Log in with GitHub, and you have a working key in under a minute. The free plan gives you 35 calls a day against the open endpoints and a set of demo properties, enough to write and test the integration before anyone talks about an agreement.
How do I authenticate?
The test key comes from the GitHub login. In production you use OAuth2 client credentials: a client id and secret are exchanged for a token at /auth/token, and the token is sent as Authorization: Bearer on every call. One mechanism for all endpoints, no keys in the URL. The details are in the authentication guide.
What happens when I hit a limit?
You get 429 Too Many Requests with a Retry-After header that tells you how long to wait, never a silent rejection. The default is 120 calls a minute per token. Responses also carry RateLimit-* headers, so a well-behaved client can slow down before it hits the limit.
Do you deliver personal data?
Some fields on owners, buyers and sellers are personal data and require the person:read scope in addition to the scope for the endpoint itself. Without it the field is left out. Personal data is part of the Enterprise plan and requires a signed data processing agreement, see Privacy and data processing. Ownership through companies is not personal data: it comes from the company registers and is included in the base package.
Norway only?
No. Swedish fastigheter, plots, buildings and companies are in beta on the same surface, with the same response format and the same key: 4.2 million fastigheter across all 290 municipalities. If you operate in both markets, you write the integration once.
Can an AI agent use this without help?
Yes, that is a design goal. /.well-known/api-catalog describes the whole catalogue in one call without a key, and the OpenAPI contract sits next to it. Would you rather ask than program? Placepoint AI gives Claude the same data without code, and the Agent does it inside Placepoint Fusion. Ready-made reports and example prompts are on Examples. The API suits cases where the data goes into a system that runs without a person in the conversation.
How fresh is the data?
The property and company registers are collected every night, the shareholder register follows the annual filing, and listings and valuations arrive as the sources publish them. Every record carries its own timestamps, so you see the age of what you got instead of trusting a general claim. The frequency per dataset is on Data and sources.
What about large extracts?
Paid plans have no row limit. Free keys do, because the surface is open enough that we would otherwise be handing out the whole register. If a real workflow needs volume, the answer is an add-on for bulk export, not paginating around a limit.
Where is the technical documentation?
The developer portal is the reference, in English, with parameters, fields and examples per operation. The guide covers what applies across: authentication, identifiers, pagination, errors, webhooks and limits.
What about Customer API, Matching API, Data API and PropCloud?
They are documented under Legacy in the developer portal for integrations that are already running. Talk to us before you build anything new against one of them, and we will tell you what the replacement is called.
Who do I talk to about agreements and pricing?
Contact us for pricing, agreements and data processing agreements. Technical questions about endpoints, scopes and getting started go to support@placepoint.no.