Skip to main content
29M UK properties, one API call Get your API key →
PropertyData.co.uk alternative

Transparent call weights.
No credit calculators.

PropertyData's credit system charges 10× the headline rate for UPRN lookups and 50× for building analysis. On Homedata, most endpoints cost 1 token — and even premium endpoints like address retrieve (5 tokens) and the complete property profile (50 tokens) use transparent weights that reflect real infrastructure costs. No credit calculators. You know your costs before you write a line of code.

Pay as you go — 100 tokens = £1, no subscription needed. Address find costs 2 tokens, retrieve costs 5. Transparent weights.

PropertyData's credit system isn't what it looks like

Their plans advertise "2,000 API calls for £28/month." What they don't say on the pricing page: different endpoints cost wildly different amounts. You only discover this by reading every individual endpoint doc page.

PropertyData credit costs by endpoint (verified from their docs)

Endpoint Credits Cost @ £28/mo plan Calls/month on entry plan
/analyse-buildings 50 credits £0.70 per call 40 calls exhausts plan
/postcode-key-stats 30 credits £0.42 per call 66 calls exhausts plan
/address-match-uprn 10 credits £0.14 per lookup 200 lookups then done
/uprn 10 credits £0.14 per lookup 200 lookups then done
/george (AI analysis) 10 credits £0.14 per call 200 tokens then done
/planning-applications 1 credit / 10 results Variable Depends on result count
/uprns (bulk), /freeholds, /national-hmo-register, /sourced-properties 1 credit / 10 results Variable Depends on result count
All other endpoints (~55) 1 credit £0.014 2,000 tokens

PropertyData — entry plan (£28/mo)

Typical property workflow: UPRN lookup → EPC → flood risk → sold prices → valuation

/address-match-uprn 10 credits
/energy-efficiency 1 credit
/flood-risk 1 credit
/sold-prices 1 credit
/valuation-sale 1 credit
Per property 14 credits
Properties per month 142 max

Homedata — flat-rate plan

Same workflow: address lookup → EPC → flood risk → sold prices → comparables

Address find + retrieve 7 tokens (2+5)
EPC check 1 token
Flood risk 1 token
Sold prices 5 tokens
Comparables Arranged per customer
Per property, comparables not included 14 tokens
Properties per month (Growth) 714 on 10k plan, before comparables

These two totals don't cover the same work. PropertyData's fifth step is /valuation-sale at 1 credit; ours is comparables, which we arrange per customer rather than sell at a fixed weight. On the four steps both sides price — address, EPC, flood risk, sold prices — it's 13 credits against 14 tokens.

The point isn't just cost. It's that a developer building a PropertyData-powered product can't predict their monthly bill until they've profiled exactly which endpoints they hit, at what volumes, and on which plan tier. Homedata's answer: transparent call weights published on every endpoint, an X-Call-Weight header in every response. Put that in a spreadsheet and you're done.

How we compare

PropertyData.co.uk Homedata
Pricing model Credit-based — each endpoint costs 1–50 credits Transparent weights — most endpoints 1 token, address 2-5; comparables arranged per customer
Entry price 14-day trial, 500 credits — no permanent free tier Pay as you go — 100 tokens = £1, tokens never expire
Pricing From £28/month (API 2k, 2,000 credits) View pricing →
UPRN lookup cost 10 credits (£0.14 at entry plan) — 200 lookups/month 2 tokens (address find) — transparent weights, no credit calculators
Can you predict monthly cost? Not without profiling which endpoints you use Yes — calls × plan rate, no exceptions
Primary product Web UI data browser + API add-on API-first — no UI subscription required
API auth API key API key (Authorization: Api-Key)
Response format JSON (varies by endpoint) Consistent JSON — same error envelope across all endpoints
UPRN-based lookups Partial — some endpoints postcode-only Yes — every property endpoint is UPRN-precise
Sold prices ✓ ✓
Price trends ✓ ✓
EPC data ✓ ✓
Comparables Basic valuation estimates ✓ — 0.5-mile radius, full property records
Flood risk ✓ (1 credit) ✓ — river, surface, coastal, groundwater (1 token)
Planning applications ✓ (1 credit per 10 results — variable) ✓ — national coverage, 1 flat call
Council tax band ✓ (1 credit) ✓ — from VOA, UPRN-matched (3 tokens)
Deprivation index No ✓ — IMD with decile + percentile
Solar assessment No ✓ — PV potential, savings, payback period
Crime data ✓ (1 credit) ✓ — 14 categories, Police UK sourced (1 token)
Interactive playground No ✓ — in-dashboard, no code needed
Client libraries No Python, JavaScript, PHP copy-paste wrappers
OpenAPI schema No ✓ — Interactive reference at /docs/api-reference
Valuation models ✓ — sale, rent, HMO, commercial (1 credit each) ✓ — sale + rent AVM, time-adjusted comps, confidence-scored
Area analytics ✓ — demand, growth, yields, demographics Partial — price trends, agent stats, deprivation
Full listing-event chain API (Added → Reduced → Withdrawn → Sold STC → Re-listed, UPRN-matched) ✗ Not available ✓ Available via API, queryable over time

Market data. Homedata exposes the full listing-event chain (Added, Reduced, Withdrawn, Sold STC, Re-listed) UPRN-matched and queryable over time via REST. Government feeds cover completions only. Portals don't expose APIs. This is the core of what Homedata sells.

We're honest about gaps. PropertyData has broader area-level analytics and a wider range of valuation models (HMO, commercial, historical) — Homedata's AVM covers sale + rent. If those are your primary use cases, they're worth evaluating. If you're building a developer product and want predictable API costs — or market activity data — Homedata is the better fit.

23 endpoints. Published weights. No surprises.

Every Homedata endpoint has a published call weight — most cost 1 token, premium endpoints like the complete property profile (50 tokens) and address retrieve (5 tokens) are priced to reflect real infrastructure costs. Every response includes an X-Call-Weight header. Know your API cost-of-goods to the penny before you write a line of code.

✓

Transparent call weights

Address find/postcode 2 tokens, retrieve 5 tokens — still far cheaper than PropertyData's 10-credit UPRN lookup

✓

Property Data

60+ fields: bedrooms, type, tenure, EPC, floor area, sales history — 1 token

✓

Price & Market Data

Price trends and price distributions — 1 token each. Live listings are arranged per customer rather than sold self-serve. Comparables — enterprise, scoped per customer (the data is in the complete property profile)

✓

Environmental & Risk

Environmental risks via one endpoint — flood, radon, noise, landfill, coal mining, air quality, invasive plants (7 risk types) — plus deprivation index and crime data. Every risk check costs 1 token.

✓

Location Context

Planning applications — 5 tokens; council tax band — 3 tokens. Solar assessment — 5 tokens (external MCS API)

Every endpoint. Same auth. Same pricing.
# One header. One call counts. Always.
H='Authorization: Api-Key YOUR_KEY'
B='https://api.homedata.co.uk'
U=100023336956

# Address search — 2 tokens
curl -H "$H" "$B/address/find/?q=10+Downing+Street"

# Property record — 1 token
curl -H "$H" "$B/properties/$U/"

# EPC — 1 token
curl -H "$H" "$B/epc/?uprn=$U"

# Flood risk — 1 token
curl -H "$H" "$B/risks/flood/?uprn=$U"

# Comparables — arranged per customer, not self-serve (PostGIS spatial)
curl -H "$H" "$B/comparables/$U/"

# Planning applications — 5 tokens
curl -H "$H" -G \
  --data-urlencode "lat=51.5032" \
  --data-urlencode "lng=-0.1271" \
  "$B/planning/"

Published weights, zero surprises: every endpoint's call weight is documented and returned in the X-Call-Weight response header. Most endpoints cost 1 token — check your X-Credits-Remaining header after every response.

Up and running in 5 minutes

No sales call. No annual contract. Sign up, grab your API key, and make your first call.

  1. 1

    Create a free account

    Sign up at homedata.co.uk/register — name, email, org name. API key provisioned automatically. No credit card.

  2. 2

    Find a UPRN

    Address search is always open. On PropertyData, this costs 10 credits per lookup.

    cURL
    curl "https://api.homedata.co.uk/address/find/?q=10+Downing+Street" \
      -H "Authorization: Api-Key YOUR_API_KEY"
    # → { "suggestions": [{ "uprn": 100023336956, "address": "10 Downing Street..." }] }
  3. 3

    Query any endpoint — same cost, every time

    Python
    import requests
    
    KEY = "your_api_key"
    HEADERS = {"Authorization": f"Api-Key {KEY}"}
    BASE = "https://api.homedata.co.uk"
    uprn = 100023336956
    
    # Property, EPC, flood risk — 1 token each
    prop  = requests.get(f"{BASE}/properties/{uprn}/", headers=HEADERS).json()
    epc   = requests.get(f"{BASE}/epc/", headers=HEADERS, params={"uprn": uprn}).json()
    flood = requests.get(f"{BASE}/risks/flood/", headers=HEADERS, params={"uprn": uprn}).json()
    
    # Comparables — arranged per customer, not self-serve (PostGIS spatial)
    comps = requests.get(f"{BASE}/comparables/{uprn}/", headers=HEADERS).json()
    
    # Total: 3 tokens, before comparables. Budget: known in advance.
    print(f"{prop['full_address']} — EPC: {epc.get('current_energy_efficiency', 'N/A')}")
    print(f"Flood risk: {flood['results'][0]['label']}")
    print(f"Comparables found: {comps['total_results']}")

Comparing both side-by-side?

If you're actively evaluating Homedata alongside PropertyData, our comparison page breaks down billing models, endpoint-by-endpoint costs, and the gaps where PropertyData still leads.

Homedata vs PropertyData — full comparison →

Other alternatives you might be considering

Zoopla API

Zoopla closed their public Property API to most developers. If you were using it for prices or property data, Homedata covers those with self-serve, pay-as-you-go access. Listings are the exception: they are arranged per customer rather than sold self-serve, so listing access is a separate conversation rather than something you can buy with tokens.

Zoopla API alternative →

Ideal Postcodes

Good developer experience for address lookup (PAYG, 2–4.5p per call). No property enrichment — just addresses and UPRNs. Solid if that's all you need; Homedata if you need property, EPC, risk, and price data alongside.

Ideal Postcodes vs Homedata →

getAddress()

Simple postcode lookup API — affected by the October 2025 Royal Mail IP ruling. No property intelligence beyond address and UDPRN. Homedata covers address lookup (find 2 tokens, retrieve 5) alongside full property enrichment.

getAddress() vs Homedata →

Loqate (GBG)

Enterprise address validation platform with no public pricing — requires a demo call, no developer self-serve. Better suited to large enterprise compliance use cases. Homedata has a pay-as-you-go pricing and self-serve signup.

Loqate vs Homedata →

Searchland

Map-first SaaS platform for land and planning professionals. £195/seat/month with no developer API — if you want programmatic access to planning applications, title data, or flood risk, Homedata gives you a REST API instead of a per-seat web UI.

Searchland vs Homedata →

Nestdata

Enterprise bulk data supplier for direct mail campaigns — no public pricing, no developer API, enterprise contracts only. If you need self-serve REST API access to property data, Homedata is the developer-friendly alternative.

Nestdata vs Homedata →

Know your costs before you ship.

Pay as you go — 100 tokens = £1, no subscription needed. Transparent weights — most endpoints cost 1 token, address find costs 2, retrieve costs 5. No hidden credit multipliers.

✓ Pay as you go, no subscription needed ✓ 23 endpoints, published weights ✓ Transparent call weights ✓ <5min to first call ✓ OpenAPI schema
Last reviewed: May 2026  ·  Reviewed by the Homedata Team  ·  Pricing data verified from PropertyData.co.uk public documentation