His Majesty's Land Registry (HMLR) is the government body responsible for registering ownership of land and property in England and Wales. Its digital programme has progressively opened access to title and transaction data through APIs, bulk downloads, and linked data services. For UK PropTech businesses, HMLR data is the most authoritative source of property ownership, transaction history, and boundary information available in the market.
Softomate Solutions is a London-based software development agency specialising in property technology integrations, including HMLR API connectivity, EPC register queries, price paid data feeds, and open property data analytics. Our API integration team has connected HMLR data services to estate agency CRMs, investment analysis platforms, and property valuation tools across the UK.
HMLR operates several distinct data services, each with different access methods, licencing conditions, and update frequencies. Understanding the difference is essential before planning an integration.
The Price Paid dataset records every residential property transaction registered in England and Wales since January 1995. It covers the sale price, property type, address, tenure (freehold or leasehold), and whether the transaction was standard, additional, or a new build. The dataset is updated monthly and available as a free bulk download or via a SPARQL endpoint. More than 25 million transaction records are in the dataset. This is the primary data source for automated valuation models (AVMs), comparable sales tools, and market analysis dashboards.
The UK House Price Index (UK HPI) is produced jointly by HMLR and the Office for National Statistics. It provides average house price and price change data at national, regional, local authority, and ward level, updated monthly with approximately an eight-week lag. An open API provides query access by area and time period. The UK HPI is the reference dataset for market trend reporting and the index that most automated property valuation tools use for area-level pricing signals.
The title register for a registered property contains the ownership details, charges (mortgages, restrictions), easements, and covenants affecting the property. The title plan shows the general boundary of the registered land. Individual title documents are available through the HMLR portal for a small fee, and the Search of the Index Map (SIM) service confirms whether a parcel of land is registered and, if so, under which title number. A business planning to automate title searches at volume should explore HMLR's Business e-services and the Business Gateway API.
The National Polygon Service (NPS) provides polygon boundary data for registered properties in England and Wales, including the unique title number, the polygon geometry, and the estate interest type. Access requires a data licence from HMLR and payment of an annual fee based on usage tier. NPS data enables mapping applications to display property boundaries, associate title numbers with geographic features, and identify unregistered land gaps. It is the data source behind most property boundary visualisation tools in the UK market.
HMLR data is available under the Open Government Licence for most datasets, which permits commercial use including redistribution in derived products. Applications must comply with the licence terms, which require attribution and prohibit claiming the data as your own original work. The National Polygon Service is an exception - it requires a separate commercial licence and carries restrictions on redistribution.
Price paid data is the foundation of any UK automated valuation model. Combining transaction history with property characteristics - size, type, condition, EPC rating - allows a model to estimate the current market value of a given property based on recent comparable sales. HMLR price paid data, combined with EPC register data (which includes floor area measurements), gives a reasonable basis for a pounds-per-square-foot AVM without purchasing expensive commercial data licences. Professional AVM providers supplement this with additional data sources including listing prices, rental yields, and local authority planning records.
Portfolio landlords and property investors use HMLR price paid data to track the capital performance of their holdings over time, identify comparable sales for refinancing valuations, and screen potential acquisitions against market transaction evidence. A portfolio analytics tool built on HMLR data gives investors a live view of their portfolio value against a market-evidenced benchmark, without relying on estate agent valuations that may carry a commercial interest.
HMLR title register queries can confirm whether a property's title has been updated following a transaction, providing independent evidence of completion. This data can be used to build chain progression monitoring tools that give estate agents and solicitors a real-time view of where each transaction in a chain stands without relying on phone calls to counterparties. Our real estate software team has built chain dashboards using HMLR completion data as the authoritative confirmation source.
Development companies and land promoters use HMLR data to identify unregistered land parcels (where registration has never occurred), long-duration ownership (properties that have not changed hands in 20 or more years), and off-market opportunities in target development zones. Combining HMLR ownership data with planning portal records, aerial imagery, and Local Plan designations creates a prospecting tool that surfaces development opportunities before they reach the open market.
HMLR provides its bulk data as CSV downloads and its query services through a combination of REST APIs and SPARQL endpoints. The technical approach depends on whether you need bulk data for batch processing or real-time queries for live applications.
For price paid data and UK HPI, the simplest integration is a scheduled bulk download into a local database. HMLR publishes monthly updates; a pipeline that downloads the monthly delta, validates the records, and upserts into a Postgres or MySQL database keeps your local copy current with minimal complexity. The full price paid dataset is approximately 4GB compressed and 25GB uncompressed; a partial load strategy based on postcode district keeps the footprint manageable for most applications.
For live title register queries, use HMLR Business e-services or the Business Gateway API. These services are designed for conveyancers, solicitors, and property professionals who need authoritative real-time data. Access requires registration with HMLR and agreement to their business terms. Our API development team manages HMLR Business Gateway integrations including authentication, error handling, retry logic, and rate limit management.
HMLR publishes some datasets as linked data using the W3C standards. The SPARQL endpoint allows complex queries across the price paid data that combine multiple filter criteria in a single request. This approach is powerful for analytics queries but requires familiarity with the RDF data model. For most PropTech applications, a local Postgres copy of the bulk data with well-indexed postcode and UPRN columns is faster and simpler than SPARQL queries against the live endpoint.
HMLR data is authoritative but not complete in all dimensions. Understanding the limitations is essential for applications that depend on it.
Price paid data covers registered residential transactions only. Commercial property, lease assignments, transfers at undervalue, and transactions between connected parties may not appear. Scotland is covered by Registers of Scotland (not HMLR); Northern Ireland by Land and Property Services (NI). HMLR price paid data also carries a registration lag of four to twelve weeks, meaning very recent sales are absent.
Title register data reflects the register at the point of query. If a transaction is in progress but not yet completed, the register will show the previous owner. The National Polygon Service, while comprehensive, is not fully aligned with Ordnance Survey MasterMap boundaries in all areas; discrepancies require manual review in boundary-sensitive applications.
Commercial property data providers including Landmark Information Group, TwentyCi, and CACI supplement HMLR open data with proprietary datasets covering listing prices, rental yields, planning applications, flood risk, ground conditions, and demographic data. These commercial layers are valuable for sophisticated AVM and risk assessment applications but carry significant licensing costs.
For most UK PropTech startups and scale-ups, HMLR open data plus EPC register data provides a viable foundation for an MVP. As the product matures and commercial requirements justify the cost, commercial data layers can be added incrementally. The key is to architect the integration layer cleanly from the start so that additional data sources can be incorporated without restructuring the core application.
A well-designed HMLR integration architecture separates three concerns: data acquisition, data storage, and data serving. The acquisition layer handles downloading bulk datasets on schedule and querying real-time APIs on demand. The storage layer maintains a clean, indexed local copy of the data that your application queries without hitting HMLR's infrastructure directly. The serving layer exposes the data to your application logic through well-defined internal APIs.
This separation matters for several practical reasons. HMLR APIs have rate limits and occasional downtime; a local copy ensures your application remains functional when the upstream service is unavailable. It also allows you to enrich the raw HMLR data with your own derived fields - computed price-per-square-metre figures, postal geography hierarchy, index-adjusted historical prices - without modifying the original records. When HMLR releases a new data format or schema update, only the acquisition layer needs to change; the storage and serving layers remain stable.
Our API development and integration team designs HMLR data pipelines with this architecture as standard, using scheduled jobs for bulk data synchronisation, retry logic and circuit breakers for real-time API calls, and versioned internal APIs so that application features do not break when data pipeline updates are deployed.
Several new open property data initiatives are expanding what UK PropTech businesses can build without commercial data licences. The Geospatial Commission's National Underground Asset Register (NUAR) is making subsurface infrastructure data accessible for the first time, relevant for developers and utilities-adjacent PropTech. The Levelling Up and Regeneration Act 2023 includes provisions for standardising planning data across local authorities, which will eventually make planning application data queryable through consistent APIs rather than authority-by-authority scraping.
The Open Standards Board has been working on a national address dataset that reduces reliance on Ordnance Survey's licensed AddressBase product for basic address lookup. PropTech businesses that monitor these developments and build data layer flexibility into their architecture can incorporate new open datasets as they become available, progressively reducing dependency on commercial data licences as public data coverage improves.
The Centre for Digital Built Britain's Digital Twin programme and Connected Places Catapult initiatives are producing open standards and datasets for the built environment that will increasingly intersect with property technology. Businesses building the next generation of PropTech products should track these initiatives alongside the more established HMLR and EPC data programmes.
Property data often includes personal information: names and addresses of property owners, tenant details, valuation reports that identify individuals. UK GDPR applies wherever personal data is processed, including within PropTech applications that consume HMLR or other open datasets that contain personally identifiable information.
The practical requirements are: a lawful basis for processing each category of personal data, a privacy notice that accurately describes how data is used, a mechanism for responding to subject access requests, and appropriate technical and organisational security measures. For PropTech businesses handling financial data or operating in the mortgage or insurance sector, FCA registration requirements may also apply.
Data residency is also a consideration. UK-headquartered PropTech businesses should ensure that personal data is stored on UK or EEA infrastructure, or that appropriate transfer mechanisms are in place for any data processed by non-UK cloud providers. This is a standard compliance requirement but one that is worth addressing in the architecture rather than retrofitting after a data residency question is raised by a client or regulator.
Yes. HMLR price paid data is published under the Open Government Licence version 3.0, which permits commercial use including building products and services on top of the data. You must provide attribution - typically a statement that the data is reproduced from HM Land Registry information licensed under the Open Government Licence - and you cannot imply that HMLR endorses your product. The National Polygon Service is licensed separately and is not available free of charge for commercial applications.
HMLR publishes monthly updates to the price paid dataset, typically in the first week of each calendar month covering transactions registered in the previous month. There is a registration lag of four to twelve weeks between a property sale completing and the transaction appearing in the price paid data. This means the dataset is not suitable for applications that require knowledge of very recent sales in real time; it is well-suited to trend analysis, valuation modelling, and historical comparables.
His Majesty's Land Registry (HMLR) is the government body that maintains the title register for England and Wales. It provides data access through several mechanisms: a public portal for individual title searches, a Business Gateway API for professional and commercial users needing programmatic access, bulk data downloads through the Use Land and Property Data portal, and linked data services via a SPARQL endpoint. The appropriate access method depends on your volume, real-time requirements, and whether you are a regulated professional or a data business.
Yes. HMLR price paid data is the primary input for most UK automated valuation models. Combining it with EPC register data (which includes floor area measurements), property type classifications, and local market trends allows a model to estimate property values based on comparable transaction evidence. Professional AVM tools supplement HMLR data with listing price histories, rental yield data, and local authority planning records to improve accuracy. Any valuation tool should clearly communicate that results are automated estimates, not professional valuations, and should not be presented as equivalent to a RICS Red Book appraisal.
No. Scotland's land register is maintained by Registers of Scotland (RoS), which provides its own Safeguard API and price paid data under Scottish open data licences. Northern Ireland's land registry is administered by Land and Property Services (LPS) as part of the Department of Finance. PropTech businesses operating UK-wide need to handle three separate data sources and three different data structures for ownership and transaction records. England and Wales share HMLR; Scotland uses RoS; Northern Ireland uses LPS.
More from the blog
Let us help
Talk to our London-based team about how we can build the AI software, automation, or bespoke development tailored to your needs.
Softomate Solutions Limited
Deen Dayal Yadav
Online
