HM Land Registry
HM Land Registry is the non-ministerial government department that registers the ownership of land and property in England and Wales, guaranteeing title to more than 26 million registered estates. In a United Kingdom market that has no MLS and no cooperative listing standard — residential listings are controlled by the Rightmove and Zoopla duopoly and reach them through agency CRM software — HMLR is the counterweight, and it sits at the legal foundation of the value chain rather than at the consumer end: it is the authoritative source of who owns what, what it sold for, and where its boundaries are, and every conveyancing transaction in England and Wales terminates at its register. Its API posture is genuinely and unusually good for a registry, but it is split into three tiers that should never be conflated. First, a real open layer: the landregistry.data.gov.uk platform serves a live, anonymous, unauthenticated SPARQL 1.1 endpoint plus a W3C Linked Data API over Price Paid Data and the UK House Price Index, with JSON/CSV/Turtle content negotiation, alongside bulk Price Paid CSVs and INSPIRE index polygons — all under the Open Government Licence v3.0 with no signup, no key and no fee. Second, a self-serve keyed tier: the Use land and property data service issues an API key automatically on account creation and exposes a documented REST API for dataset metadata and signed download URLs, but the datasets behind it require a signed licence per dataset and some are chargeable — the Registered Leases commercial licence is £5,000 a year plus VAT, and the National Polygon Service, which holds the title boundary polygons and the title number to UPRN lookup, is £20,000 a year plus VAT. A state registry selling the spatial extent of the public record back to the public is the finding, and it is recorded here plainly. Third, the Business Gateway: the B2B channel that conveyancers and their case management systems use to submit applications to change the register, order official copies and run priority searches. Its developer pack is fully public on GitHub Pages with eight downloadable OpenAPI 3.0/3.1 contracts and 37 SOAP XSDs, but the production host businessgateway.landregistry.gov.uk will not complete a TLS handshake without an HMLR-issued client certificate, and access requires signing a development licence and holding a business e-services account. There is no RESO Web API certification, no RESO Data Dictionary, no OData $metadata document and no Universal Property Identifier anywhere in HMLR's stack — RESO is a North American NAR construct with no UK adoption, and HMLR's machine-readable contracts are OpenAPI, XSD and W3C linked data instead.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles HM Land Registry the way a machine reads it — 50 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — HM Land Registry scores 56.2/100 (strong), with a separate agent-readiness read of 37/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from HM Land Registry's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hm-land-registry/"
title="HM Land Registry on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hm-land-registry.svg"
alt="HM Land Registry Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/hm-land-registry/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hm-land-registry/"
title="HM Land Registry on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hm-land-registry/card.svg"
alt="HM Land Registry Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile HM Land Registry
Each block below is one kind of artifact we hold for HM Land Registry. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
HM Land Registry Open Data SPARQL API
Live SPARQL 1.1 query endpoint over HM Land Registry's open linked data — Price Paid Data transaction records for every property sale in England and Wales lodged for registratio...
HM Land Registry Price Paid Data Linked Data API
W3C Linked Data API over the Price Paid Data dataset, exposing every property sale in England and Wales sold for value and lodged for registration since 1995. Resources resolve ...
UK House Price Index Linked Data API
W3C Linked Data API over the UK House Price Index, the official house price statistic calculated by the Office for National Statistics from HM Land Registry, Registers of Scotla...
HM Land Registry Application information API
The Application information API API from HM Land Registry — 2 operation(s) for application information api.
HM Land Registry Attach a document API
The Attach a document API from HM Land Registry — 1 operation(s) for attach a document.
HM Land Registry Attach a message API
The Attach a message API from HM Land Registry — 1 operation(s) for attach a message.
HM Land Registry Datasets API
Dataset discovery, metadata and download URL minting.
HM Land Registry Download a document API
The Download a document API API from HM Land Registry — 2 operation(s) for download a document api.
HM Land Registry Draft Titles API
The draft-titles API from HM Land Registry — 1 operation(s) for draft-titles.
HM Land Registry ECD API
The ECD API from HM Land Registry — 1 operation(s) for ecd.
HM Land Registry Notifications API
The Notifications API API from HM Land Registry — 4 operation(s) for notifications api.
HM Land Registry Official Copies API
Document information related to a title.
HM Land Registry Official Search of Whole with Data API
The Official Search of Whole with Data API from HM Land Registry — 1 operation(s) for official search of whole with data.
HM Land Registry Registered Proprietor Names API
Proprietor information related to a title.
HM Land Registry Send a document API
The Send a document API API from HM Land Registry — 3 operation(s) for send a document api.
HM Land Registry Submit an application API
The Submit an application API API from HM Land Registry — 2 operation(s) for submit an application api.
HM Land Registry Title API
Operations relating to titles for land or property.
HM Land Registry Titles API
Operations regarding titles
Scroll within the panel for all 18 ·
Open Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Land Register API
OPEN COLLECTIONHMLR Business Gateway
OPEN COLLECTIONOfficial Copy Document Availability Service
OPEN COLLECTIONHMLR Business Gateway
OPEN COLLECTIONOfficial Copy Document Availability Service
OPEN COLLECTIONOfficial Search of Whole with Data
OPEN COLLECTIONRegistered Proprietor Names Service
OPEN COLLECTIONUse Land and Property Data API
OPEN COLLECTIONScroll within the panel for all 10 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
HM Land Registry Business Gateway Notifications
Event surface of the HM Land Registry Business Gateway. As an application to change the Land Register moves through HMLR processing, HMLR raises notifications about it. Business...
ASYNCAPIJSON Schema 11
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Hm Land Registry Application Cancelled
JSON SCHEMAHm Land Registry Application Completed
JSON SCHEMAHm Land Registry Application Error
JSON SCHEMAHm Land Registry Application Message Failed
JSON SCHEMAHm Land Registry Application Message Success
JSON SCHEMAScroll within the panel for all 11 ·
Examples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for HM Land Registry — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 8
Portal, sign-up, and the first successful call
Scroll within the panel for all 8 ·
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/hm-land-registry · machine-readable index on apis.io
This is an independent, third-party profile of HM Land Registry, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.