Land Registry data. UPRN-keyed. One API key.
The HM Land Registry API gives you sold prices and title data — but in inconsistent formats, with strict rate limits, and no UPRN keying. Homedata serves the same HMLR data through a consistent REST API with UPRN keys, 250ms median latency, and 19 additional datasets behind the same authentication header.
Free tier — 100 calls/month, no credit card required. Land Registry sold prices included from Starter plan (£49/month).
The problem with integrating HMLR directly
HM Land Registry provides genuinely useful public data — the Price Paid dataset covers every property sale in England and Wales going back to 1995. But integrating it directly into a product is awkward:
- → No UPRN keying. HMLR responses use address strings. To join Land Registry data to EPC, flood risk, or council tax records, you need fuzzy address matching — a significant engineering overhead.
- → Inconsistent JSON schemas. Different HMLR endpoints return different response structures. The Price Paid API, title register API, and linked data endpoints all have separate schemas and authentication models.
- → Rate limits at scale. HMLR's API endpoints have strict rate limits that make bulk property workflows impractical without queuing infrastructure.
- → Four separate APIs. Even basic property enrichment requires HMLR (prices + titles), MHCLG (EPC), Environment Agency (flood risk), and OS (address/UPRN). Four registration processes, four API keys, four schemas to maintain.
Homedata normalises all of this into a single REST API. One key, one schema, UPRN-keyed joins across every dataset.
HMLR API vs Homedata
| HMLR API | Homedata | |
|---|---|---|
| Sold prices | ✓ England & Wales | ✓ England & Wales, UPRN-keyed |
| Title records | ✓ (paid — official copies) | ✓ tenure, owner, title number |
| UPRN-keyed responses | No — address-keyed only | ✓ Every endpoint |
| Consistent JSON schema | Partial — varies by endpoint | ✓ Same envelope across all endpoints |
| EPC ratings | No — separate MHCLG API | ✓ 29M certificates, same UPRN key |
| Flood risk | No — separate EA API | ✓ NAFRA2, river + surface water |
| Planning applications | No | ✓ 20M applications, 417 LPAs |
| Address / UPRN lookup | No — separate OS API | ✓ 36M addresses, typeahead search |
| Rate limits | Strict per-endpoint quotas | 250ms median latency, call-weight billing |
| Free tier | Price Paid bulk download (free, monthly batch) | 100 API calls/month, real-time |
| Self-serve signup | Registration per dataset | One registration — all 19 endpoints |
| Code examples | Limited — community docs | cURL, Python, JavaScript for every endpoint |
| Price comparables (spatial) | No | ✓ PostGIS 0.5mi radius, bedroom-matched |
Why developers use Homedata for Land Registry data
One API for all property data
Instead of integrating with HMLR for sold prices, MHCLG for EPC, Environment Agency for flood risk, and OS for address lookup — Homedata normalises all these datasets behind a single API key. One authentication header, consistent JSON, and UPRN-keyed joins across every dataset.
UPRN-keyed joins, no address matching
HMLR responses use address strings — joining a sold price record to an EPC or flood risk record requires fuzzy address matching, which breaks on minor formatting differences. Homedata normalises everything to UPRN. Every data point for a property shares the same identifier: no joins to debug, no mismatches to handle.
Real-time, per-property queries
HMLR's Price Paid dataset is a monthly bulk download — not suitable for real-time per-property lookups in a product flow. Homedata's sold prices endpoint is a real-time REST API: query any UPRN and get back the full transaction history in under 300ms. Address find costs 2 calls, sold prices 1 call.
Transparent, predictable billing
HMLR's official copy and title register API charges per transaction. Homedata uses flat monthly plans — know your maximum cost before you write a line of code. See pricing →
Land Registry sold prices in 2 lines
One API key. One endpoint. Full transaction history per property.
curl "https://api.homedata.co.uk/api/property_sales/?uprn=100023336956" \
-H "Authorization: Api-Key YOUR_API_KEY"
# Response:
{
"uprn": 100023336956,
"sales": [
{
"price": 585000,
"date": "2022-03-15",
"transaction_type": "Standard",
"tenure": "Freehold",
"new_build": false,
"source": "HMLR Price Paid"
}
]
}
import requests
BASE = "https://api.homedata.co.uk"
HEADERS = {"Authorization": "Api-Key YOUR_KEY"}
uprn = 100023336956
# Step 1: sold prices from HMLR (1 call)
sales = requests.get(f"{BASE}/api/property_sales/",
params={"uprn": uprn}, headers=HEADERS).json()
# Step 2: EPC from MHCLG (1 call — same key, same UPRN)
epc = requests.get(f"{BASE}/api/epc-checker/{uprn}/",
headers=HEADERS).json()
# Step 3: flood risk (1 call)
flood = requests.get(f"{BASE}/api/risks/flood/",
params={"uprn": uprn}, headers=HEADERS).json()
# With raw HMLR, this would require 3 separate APIs, 3 keys,
# and address-matching to join them. Here: 3 calls, 1 key, 1 UPRN.
Where HMLR is genuinely better
Honest comparison:
Bulk data downloads are free
HMLR's Price Paid bulk dataset is a free monthly download covering every sale since 1995 — useful for analytics, ML training, and offline processing. Homedata is a real-time API billed per call. For batch analytics on the full dataset, HMLR's bulk download is the right tool.
Official Legal Documents
For legally certified title register official copies (e.g. for conveyancing), you need HMLR directly — Homedata provides title data for developer use cases but does not issue official copies with HMLR certification.
Pricing
Flat monthly plans — sold prices, EPC, flood risk, and 16 more endpoints all included.
- ✓ 100 calls/month
- ✓ Address lookup
- ✓ No credit card
- ✓ 2,000 calls/month
- ✓ Sold prices + EPC + flood
- ✓ Title data
- ✓ 10,000 calls/month
- ✓ All 19 endpoints
- ✓ Priority support
Land Registry data. One API key.
Sold prices, title data, EPC, flood risk — all UPRN-keyed, all in one API. Free tier, no sales call.
Compare Homedata with other providers
Sprift Alternative
PDF property reports vs raw API access
PropertyData Alternative
Transparent pricing from £49/mo vs £1,300/mo
Homedata vs StreetData
Flat monthly pricing vs per-property charges
Homedata vs Realyse
Self-serve API vs enterprise dashboards
getAddress Alternative
Address lookup + full property data
Searchland Alternative
Property search + data enrichment API
UK Property Data API
29M properties, 15+ data categories, free tier