One API for Norwegian property and company data.
Placepoint API puts property, buildings, companies, ownership and transactions behind a single authenticated surface — already joined on the cadastral key. It replaces the patchwork your integration is stitched from today: Placepoint 1.0, Newsec Maps and PropCloud.
Sign in with GitHub and the free tier issues a token immediately — 35 calls a day, no card, no contract.
# 1. ask what exists — no token needed curl "https://data.placepoint.no/discovery" { "products": [ { "id": "property", "status": "live", "required_scope": "property:read", "openapi_url": "/specs/property/openapi.json", "ai_context_url": "/specs/property/ai-context.md" }, … 10 more ] } # 2. call it curl -H "Authorization: Bearer $TOKEN" \ "https://data.placepoint.no/property/cadastres/0301-3-616-0-0" { "data": { "nma": "0301-3-616-0-0", "address": "Karenslyst Allé 14, 0278 Oslo", "municipality": "Oslo", "buildings": 3 }, "meta": { "page": 1, "pageSize": 25, "total": 1 } } # same envelope on all 192 endpoints # x-call-weight: 1 ← what the call cost you
Three APIs became one.
The value isn't another data feed — it's that the joins are already made, the contract is the same everywhere, and one token opens all of it.
One surface, not three
Property, valuation, listings and risk from PropCloud; cadastre panels, energy attests and ownership trees from our core; tenant, landlord and person data from the Newsec connector — all behind one host, one token, one error format.
Already joined
The cadastral number is the key everywhere. Go from an address to the property, its buildings, the companies registered on it, who owns those companies and what the property last sold for — without maintaining the mapping yourself.
Built for agents too
GET /discovery tells a machine what exists, and every product ships
an ai-context.md next to its OpenAPI spec — the data model, the
patterns and the gotchas in prose. The MCP server sits on the same surface.
Eleven products. One token.
Scopes are granted per product, so you pay for what you integrate. Ask
/discovery at runtime and it answers with exactly the products your
token can reach.
Key to first response in under ten minutes.
Three steps, in this order — no procurement gate in front of the first call.
Sign in with GitHub
/auth/github/start redirects, verifies you and mints a JWT valid for
14 days. The free tier gives you 35 calls a day against the open endpoints and
a set of demo properties — enough to build against before anyone signs anything.
Ask what exists
GET /discovery returns the product catalogue, the scope each one
needs and links to its OpenAPI spec and AI context file. Your client — or your
agent — can plan the integration from that one response.
Call it
Every route answers { data, meta }, paginates with
?page&pageSize and reports what the call cost in the
x-call-weight header. Errors carry a stable code, a message and a
request id. Rate limits answer 429 with Retry-After.
Public registers, kept current — plus the parts nobody publishes.
Official registers are ingested on a schedule and reconciled against each other, so a company that moved last week points at the right building this week. On top of that sit the joins and derived layers we build ourselves.
Pick the plan. We'll quote the price.
Base scopes — property, company, listings and search — are included in every paid plan. Specialist scopes come as add-ons, so a valuation integration doesn't subsidise someone else's person lookups. What you pay depends on which scopes you switch on, the call volume you expect and how long you commit for; tell us those three and you get a written quote back.
- 35 calls per day
- Open endpoints + demo properties
- 14-day token, renewable
- No DPA, no card, no contract
- All base scopes
- 120 requests per minute
- No daily call cap
- Add-on scopes on request
- Support via your account manager
- All base scopes
- 120 requests per minute
- Onboarding session with engineering
- Add-on scopes on request
- Everything in Standalone
- Person data (five endpoints, DPA-gated)
- Raised page-size and volume limits
- Signed DPA and agreed uptime target
- Named contact and roadmap input
| Scope | What it opens | Comes with |
|---|---|---|
valuation:read | AVM estimates, price history, comparables | Any paid plan |
risk:read | Per-property risk assessment, landslide exposure | Any paid plan |
person:read | Person profile, phone lookup, roles, linked properties | Signed DPA required |
| AI agent licence | Agent and MCP use, with the higher call volume that implies | Any paid plan |
| Bulk export | Scheduled full-dataset delivery instead of per-call reads | Standalone and up |
| Free | Add-on | Standalone | Enterprise | |
|---|---|---|---|---|
| Daily call cap | 35 | None | None | None |
| Rate limit | 120 / min | 120 / min | 120 / min | Negotiated |
| Open endpoints | Yes | Yes | Yes | Yes |
| Commercial property & company data | Demo properties | Yes | Yes | Yes |
| Person data | — | Add-on + DPA | Add-on + DPA | Included |
| Page size ceiling | 50 | 50 | 50 | 100 |
| Swedish data | — | Beta access | Beta access | Beta access |
| Uptime target in contract | — | — | On request | Yes |
Paid plans run as annual agreements. Which scopes you enable, the call volume you expect and how long you commit for all move the number, and longer commitments and annual prepayment move it down. Send those three through the contact form and you get a written quote back — build against the free tier while you wait.
Questions we get before the first call.
What exactly does this replace?
Three integration surfaces: the Placepoint 1.0 customer API, Newsec Maps and direct PropCloud access. If you hold one of those integrations today, the Placepoint API is where it moves — same data, one contract, one auth mechanism. Talk to us before you build against a legacy endpoint; we will tell you what its replacement is called.
How fast can I actually get started?
Sign in with GitHub and you have a working token in about two minutes. The free tier allows 35 calls a day against the open endpoints and a set of demo properties — enough to write and test your integration before anyone talks about a contract.
How is it authenticated?
A signed JWT in the Authorization: Bearer header, carrying the
scopes your plan includes. One mechanism for every endpoint — no API keys in
query strings, no per-backend credentials, no separate login for the Newsec or
PropCloud parts.
What happens when I hit a rate limit?
You get 429 Too Many Requests with a Retry-After header
telling you how long to wait — never a silent denial. The default is 120 requests
per minute per token. Responses also carry usage headers as you approach a limit,
so a well-behaved client can throttle itself before it trips one.
Do you expose data about people?
Five endpoints sit behind the person scope — person profile, phone
lookup, roles and the properties linked to a person — classified as the most
sensitive tier. It requires a signed data-processing agreement and is not part
of any self-serve plan. Corporate ownership trees are not person data:
they come from the company registers under company:read and
property:read. Ultimate-beneficial-owner resolution is not part of
the API today. Endpoints that do not need personal data never return it.
Is this Norway only?
No. Swedish properties, parcels, buildings and organisations are in beta on the same surface, with the same response shapes and the same token — 4.3 million Swedish properties and 9 million building footprints today. If you operate in both markets you write the integration once.
Can an AI agent use this without hand-holding?
That is a design goal, not an afterthought. /discovery describes the
whole catalogue in one unauthenticated response, each product ships a written
ai-context.md alongside its OpenAPI spec, and an MCP server exposes
the same data to agent runtimes directly.
How fresh is the data?
Company and property registers are ingested on a nightly schedule; the shareholder register follows the annual filing cycle; listings and valuations come through as the upstream sources publish them. Every record carries its own timestamps, so you can see the age of what you got rather than trust a blanket claim.
What are the usage limits on bulk extraction?
Paid plans are not row-capped. Trial and free tokens are, because the surface is open enough that we would otherwise be handing out the register. If a legitimate workload needs volume, the answer is a bulk-export add-on rather than paginating around a limit.
The docs call it something else — is that the same API?
Yes. Placepoint API is the product name. The developer portal
still titles it Data API, and the OpenAPI spec and
/discovery still report Placepoint Unified API, while that
rename works its way through. Same host, same token, same endpoints —
https://data.placepoint.no is the base URL in every case, and
nothing in your integration changes.
Who do I talk to about a contract?
Contact us for commercial terms, pricing and data-processing agreements. support@placepoint.no for technical questions about endpoints, scopes and onboarding.
Start with the free tier. Decide after it works.
No demo required to see the data — the catalogue is public and the first token is two minutes away.