Where to start
The API guide and reference is the technical contract: authentication, identifiers, pagination and filtering, errors, rate limits, the lifecycle policy, and a generated reference page per operation.
The Placepoint API product pages (Norwegian) explain what each group of endpoints answers, with example responses and a GitHub sign-in that returns a trial key to the page you are on.
APIs
The REST APIs use OAuth2 client credentials authentication and return JSON responses. The MCP server runs on the Model Context Protocol instead.
Properties, companies and areas for Norway and Sweden over one REST API: one spec, one token, stable public identifiers.
MCPConnect Claude to Placepoint data through the Model Context Protocol and ask for property analysis in plain language, with no client code to write. Claude looks up and combines cadastre, company and area data across sources, and returns text, tables, maps or reports. Work that normally takes days of manual assembly runs in minutes.
Legacy APIs (Customer, Matching, Embed, Data API, PropCloud) remain documented in the sidebar for existing integrators.
How it works
Get a trial key
Sign in with GitHub on any docs.placepoint.no/api page for a trial key in under a minute. It works today against the Leietaker-API and the Data API, and the Placepoint API accepts the same key at launch. Production credentials come from Placepoint.
Request a token
POST /auth/token with the client-credentials grant.
Call the API
Include the Bearer token in the Authorization header of every API request.