Prop Tech Package · Pay as you go
UK property data API for PropTech.
One API. 29 million properties. Address lookup, EPC, comparables, risk, listings, planning, schools: everything your product needs. No data brokering, no procurement nightmare, no multi-month enterprise sales process. Sign up and start building in 10 minutes.
Pay as you go: 100 tokens = £1. First top-up matched 100%. Top up more when you're ready to ship. 16 API endpoints 29M UK properties covered 36M UK addresses
What you get
What PropTech teams build with it
The data layer for whatever you're building.
Property portals Enrich every listing with EPC ratings, flood risk, school proximity, and price history. Stand out from the big portals by showing buyers data they can't find on Rightmove. Built on our live listings + property characteristics endpoints.
Automated valuation models Comparables within 0.5 miles (spatial), 30 years of England and Wales sold price history, listing event trails, and property characteristics: all the inputs your AVM needs. Combine with price trends and deprivation for neighbourhood adjustments.
Conveyancing platforms Pre-populate searches with EPC data, environmental risk (flood, radon, landfill, coal mining), planning history, and Land Registry titles. Cut manual data gathering from days to seconds. Reduces PII data entry, speeds completions.
Mortgage & lending tech EPC energy ratings for green mortgage eligibility screening, flood risk for standard conditions, council tax band for affordability, and sold price data for LTV verification. All via UPRN: the single key that joins every dataset.
InsurTech & underwriting
Flood risk (river, surface water, coastal, groundwater), radon, subsidence, property age, construction type, and floor area: every input your pricing model needs. Replace expensive data bundles with API calls that cost pence per property.
Landlord & letting platforms
EPC compliance tracking for the 2028 mandate, rental listing events for market benchmarking, comparables for yield calculations, and risk data for insurance. Build a compliance dashboard that landlords actually need.
The full API surface
Everything available in one place. Most endpoints are 1 token weight: predictable costs at any scale.
| Endpoint | Description | Tokens | Access |
|---|---|---|---|
| Address lookup | |||
| /address/find/ | Typeahead address search: 36M UK addresses → UPRN | 2 | Included |
| /property/{uprn}/address/ | Full address + property enrichment (beds, EPC, council tax, sold price) | 5 | Included |
| EPC & Energy | |||
| /epc-checker/{uprn}/ | Energy score and potential score (1–100), floor area, construction age | 1 | Included |
| Property data | |||
| /properties/{uprn}/ | Property characteristics: beds, baths, type, tenure, floor area | 1 | Included |
| /council_tax_band/ | Council tax band by postcode | 3 | Included |
| Market data | |||
| /property_sales/ | HMLR sold prices by UPRN | 5 | Included |
| /price_trends/ | Median sold prices and growth by postcode/district | 1 | Included |
| Environmental risk | |||
| /risks/{risk_type}/?uprn= | Flood, radon, noise, landfill, coal, air quality, invasive plants | 1 each | Included |
| Area data | |||
| /deprivation/ | IMD deprivation scores across 10 domains | 1 | Included |
| /postcode_profile/ | Area demographics, tenure mix, property type distribution | 1 | Included |
| Local amenities | |||
| /schools/nearby | Schools within radius: phase, type, Ofsted, pupil numbers | 1 | Included |
| Valuation | |||
| /comparables/{uprn}/ | Nearest sold + listed comparables, distance-ranked. Arranged per customer rather than sold self-serve; the same evidence is included in the complete property profile. | Enterprise | On request |
| Agent data | |||
| /agent_stats/ | Agent performance: listings, time to sell, price accuracy | 1 | Included |
| Market data | |||
| /price_distribution/ | Price distribution bands for any postcode in England and Wales | 1 | Included |
| Valuation | |||
| /property_avm/ | Automated valuation estimate with confidence band | 10 | Included |
Worked example
Property enrichment in parallel
Most PropTech apps need multiple data points per property: EPC, risk, characteristics, price history. Use Promise.all in JavaScript or asyncio in Python to fire them in parallel. Total response time is the slowest call, not the sum.
What this returns
8 tokens per property. A £250 top-up (25,000 tokens) = 3,125 full property enrichments.
- • Property: beds, type, floor area, tenure
- • EPC: score and potential score (1–100)
- • Flood risk: river, sea and surface water bands
- • Price history: last 5 HMLR transactions
const enrich = async (uprn, key) => {
const base = 'https://api.homedata.co.uk'
const headers = { 'Authorization': `Api-Key ${key}` }
const [property, epc, flood, prices] = await Promise.all([
fetch(`${base}/properties/${uprn}/`, { headers }).then(r => r.json()),
fetch(`${base}/epc-checker/${uprn}/`, { headers }).then(r => r.json()),
fetch(`${base}/risks/flood/?uprn=${uprn}`, { headers }).then(r => r.json()),
fetch(`${base}/property_sales/?uprn=${uprn}`, { headers }).then(r => r.json()),
])
return {
beds: property.bedrooms,
type: property.property_type,
floor_area_m2: property.epc_floor_area,
epc_score: epc.current_energy_efficiency,
flood_risk: flood.results[0]?.label ?? null,
last_sold_at: prices.results[0]?.sold_let_date ?? null,
last_sold_price: prices.results[0]?.sold_let_price ?? null,
}
}
// Usage
const data = await enrich('100023045721', 'your_api_key')
console.log(data)
// { beds: 3, type: 'House', floor_area_m2: 88, epc_score: 84,
// flood_risk: null, last_sold_at: '2019-06-14', last_sold_price: 310000 }
// Both tabs return this same shape. flood_risk is null when no flood polygon
// covers the property: the usual answer, never an absent key.
import asyncio, httpx
async def enrich(uprn: str, key: str) -> dict:
base = "https://api.homedata.co.uk"
headers = {"Authorization": f"Api-Key {key}"}
async with httpx.AsyncClient() as client:
property_, epc, flood, prices = await asyncio.gather(
client.get(f"{base}/properties/{uprn}/", headers=headers),
client.get(f"{base}/epc-checker/{uprn}/", headers=headers),
client.get(f"{base}/risks/flood/?uprn={uprn}", headers=headers),
client.get(f"{base}/property_sales/?uprn={uprn}", headers=headers),
)
p = property_.json()
sale = next(iter(prices.json()["results"]), None)
return {
"beds": p["bedrooms"],
"type": p["property_type"],
"floor_area_m2": p["epc_floor_area"],
"epc_score": epc.json()["current_energy_efficiency"],
"flood_risk": next((r["label"] for r in flood.json()["results"]), None),
"last_sold_at": sale["sold_let_date"] if sale else None,
"last_sold_price": sale["sold_let_price"] if sale else None,
}
# Usage
data = asyncio.run(enrich("100023045721", "your_api_key"))
Most PropTech apps need multiple data points per property: EPC, risk, characteristics, price history. Use in JavaScript or asyncio in Python to fire them in parallel. Total response time is the slowest call, not the sum.
One contract. One integration. One invoice.
Most PropTech teams that need EPC + address + risk + prices end up stitching together 4–6 separate data providers. That's 6 contracts, 6 pricing models, 6 integration points, 6 points of failure.
Without Homedata: typical PropTech data stack
Address lookup
getAddress, Ideal Postcodes, Loqate · £20–£100/month
EPC data
MHCLG Open Data API (rate limited, unreliable) · Free but flaky
Environmental risk
Groundsure, Landmark, SearchFlow · £250+ /month
Sold prices
HMLR Price Paid (no UPRN join, manual work) · Free but raw
Comparables
PropertyData, Nimbus (locked plans) · £200+/month
Schools
Ofsted / DfE APIs (no enrichment, no distance calc) · Free but complex
Total: £600–£1,500+/month
Plus: 6 contracts, 6 integration points, data consistency issues between providers.
With Homedata: single API, all the data
Address lookup
36M addresses, UPRN-linked, instant
EPC data
Direct from DLUHC, reliable, over 23 million certificates held
Environmental risk
Flood, radon, noise, landfill, air quality, coal
Sold prices
HMLR with UPRN join, no raw data wrangling
Comparables
0.5mi radius, distance-ranked
Schools
DfE GIAS, 27K schools, distance calculated
Pay as you go: 100 tokens = £1
One contract, one integration, one invoice. First top-up matched 100%: start building today.
What you get
Up and running in 10 minutes
From zero to first API call. No OAuth, no webhook setup, no enterprise onboarding call.
Your first call: EPC for any UPRN in England and Wales:
curl -H "Authorization: Api-Key YOUR_API_KEY" \ "https://api.homedata.co.uk/epc-checker/100023045721/" Customer story
Sign up free
Create an account at homedata.co.uk. Your API key is provisioned instantly, no waiting, no sales call.
Read the docs
Interactive API reference at docs.homedata.co.uk. Try any endpoint directly from the browser with Scalar. Every endpoint has Python, JS, and cURL examples.
Ship your feature
One Authorization header. REST JSON responses. Most developers ship their first feature in the same afternoon. A monthly subscription earns bonus tokens when you go to production.
Pricing
Pricing for PropTech teams
Pay as you go, or add tokens monthly and earn bonus tokens. Predictable token costs. No per-endpoint pricing surprises.
Pay as you go
100 tokens = £1Every endpoint · First top-up matched 100%
- Prototyping: your first top-up is matched 100%
Monthly
£50 a month5,500 tokens a month
+10% bonus tokens · Every endpoint
- Early-stage product, MVP, internal tools
Monthly
£250 a month30,000 tokens a month
+20% bonus tokens · Every endpoint
- Production apps, growing user base
Monthly
£500 a month67,500 tokens a month
+35% bonus tokens · Every endpoint
- Scale-up, high-volume enrichment
What property data does Homedata provide for PropTech companies?
Homedata provides 45+ REST API endpoints covering: address lookup (36M addresses), UPRN property data (29M properties), EPC energy ratings, comparable sold prices, live listing events, environmental risk (flood, radon, noise, landfill), planning applications, council tax, schools, IMD deprivation, and price trends. Single API key, one integration, no managing multiple data provider contracts.
How quickly can a PropTech company integrate the Homedata API?
Most PropTech developers are making their first API call within 10 minutes of signing up. Authentication is a single Authorization header (Api-Key YOUR_KEY). No OAuth flows, no webhook setup required to get started. Interactive docs at docs.homedata.co.uk with Scalar: try every endpoint directly from the browser.
Does Homedata offer volume pricing for PropTech companies?
Yes. Pay-as-you-go tokens (100 = £1) support production PropTech workloads, and a monthly subscription earns up to 75% bonus tokens. For very high volume or white-label use cases, contact us to discuss custom arrangements. One-off top-ups add exactly what you pay: useful for bulk enrichment projects.
Can I use the Homedata API in a commercial product?
Yes. Paid plans include commercial use. You can use Homedata data in customer-facing products, dashboards, reports, and applications. Attribution is not required on the data itself: your product, your brand. See the terms of service for full details.
What is the SLA and uptime for the Homedata API?
Homedata does not currently offer a formal SLA. Live service status is published at homedata.co.uk/status. The API is hosted on DigitalOcean UK infrastructure with spatial queries for comparables and address lookup. For Scale and enterprise customers we can discuss dedicated SLA arrangements.
What authentication does the API use?
API-key authentication. Include Authorization: Api-Key YOUR_API_KEY as a header on every request. Your API key is available in the dashboard immediately after signup. No OAuth flows, no session management required.
What format do API responses use?
JSON. All endpoints return consistent JSON with snake_case keys. Error responses use standard HTTP status codes (400, 401, 403, 404, 429, 500) with a detail field explaining the issue. No XML, no SOAP, no surprises.
Are there rate limits?
Every account carries the same rate-limit configuration; rate limits are about request pace, not tokens, and a 429 costs nothing. Heavy batch jobs may be throttled: contact us for burst needs or scheduled batch processing windows.
Can I use the API from a browser (CORS)?
CORS is not enabled on the production API: it's designed for server-to-server use to protect your API key. Build a server-side proxy that forwards requests to the Homedata API, then expose that to your frontend. This is the correct pattern for any API key-authenticated service.
Is there a test/sandbox environment?
The pay-as-you-go pricing (100 tokens = £1) functions as your development environment: it's the same API with the same data as production. No separate sandbox needed. Use test UPRNs like 100023045721 (a real Leeds property) for development.
Do you support webhooks or streaming?
Not currently: the API is request-response REST. For real-time listing event monitoring or price change alerts, you'd poll the relevant endpoints on a schedule. Webhooks are on the roadmap for Growth+ plans.
Related
More resources for developers
Getting Started
5-minute quickstart guide. From zero to first API call.
API Reference
Every endpoint, parameter, response schema, and error code.
Our Data
Coverage, data sources, and refresh frequencies for every dataset.
Pricing
Pay as you go, bonus tokens with a monthly subscription, and token weights for every endpoint.
Other packs
Start building today.
Pay as you go, 100 tokens = £1, first top-up matched. Get your key and test with real data.