Skip to main content
29M UK properties, one API call. Get an API key →
Homedata vs getAddress.io

Address lookup that returns
the property, not just the postcode.

getAddress gives you an address string. Homedata gives you the same address, plus bedrooms, EPC rating, floor area, property type, and sold price, in the same call. Address match costs 5 tokens on success, and the UPRN you get back works with 40+ property data endpoints. No separate property API needed.

Pay as you go: 100 tokens = £1, no subscription needed. Transparent weights: address match 5 tokens, retrieve 5. Property data endpoints just 1 token each.

A typical property enrichment workflow: per address

getAddress.io + property APIs

3 APIs, 3 keys
Address autocomplete getAddress API
Property data (beds, type, EPC) separate API
Flood risk / environmental another API
Sold price history yet another API
Integration cost 3 APIs to integrate + maintain
Monthly invoices 3 separate bills
Data joining Your problem to solve

Homedata

1 API, 1 key
Address matching → UPRN 2 tokens
Address retrieve (full record) 5 tokens
Property data, flood risk, EPC… 1 token each
Comparables Enterprise: arranged per customer
Integration cost 1 API, UPRN links everything
Monthly invoices 1 bill
Data joining Built in: UPRN-keyed

getAddress.io is excellent at what it does. If you need address autocomplete and nothing else, it's a solid choice. If you need property data too, a second API is unavoidable: unless you use Homedata.

Side by side

What matters when you're building a product on top of UK address and property data.

Homedata
getAddress.io
Address matching 2 tokens, with UPRN + property data on same key Per-lookup pricing; address fields only
Property data on lookup Beds, EPC, floor area, property type, sold price Address fields only, no property data
Entry price Pay as you go: 100 tokens = £1, no subscription needed Free tier for address lookup; limited to personal/test use
UPRN returned Yes: on every address result Yes: UPRN included
Additional data endpoints 19: EPC, flood, planning, crime, comparables… Address autocomplete only
Self-serve signup Instant API key, no sales call Self-serve available
Embeddable address widget homedata-address.js: zero-dep, maps to any form Yes: address autocomplete widget
UK address coverage 29 million residential properties ~30M+: Royal Mail PAF + OS AddressBase
Transparent pricing Transparent call weights: you know the cost before you build Per-lookup pricing: address calls count against quota
Developer docs Sidebar nav, 3-language code examples, interactive playground Good documentation: Swagger + guides

Where getAddress is stronger

getAddress.io is a focused, mature product. If address autocomplete is all you need, it does it well.

  • Broader address coverage

    Royal Mail PAF + OS AddressBase gives them ~30M+ addresses including commercial and new builds often missing from residential databases.

  • Established product, larger user base

    Used by thousands of developers. Longer track record, more community examples, broader framework integrations.

  • If it's only addresses you need

    For a checkout form, CRM autocomplete, or any product where you just want a validated UK address: getAddress is purpose-built for exactly that.

Where Homedata is stronger

Built for products where the address is just the starting point.

  • Property data on the same key

    EPC, flood risk, planning, crime, comparables, sold prices: all from the UPRN you get in the address matching. One integration, not four.

  • Address match costs 5 tokens on success

    Address match costs 5 tokens on success and includes address fields. Postcode lookup costs 2 tokens. HTTP 422 no_match or multiple_matches is never charged.

  • UPRN-first data model

    Every endpoint is keyed on UPRN: the same identifier from your address matching. No reformatting, no ambiguous address matching across data sources.

  • Predictable billing

    Transparent call weights: most endpoints cost 1 token, address match 5, postcode 2, retrieve 5, the complete property profile 50. You know your costs before you write the integration, not after your first month's invoice.

From address to full property: one API

Match a submitted address and postcode (5 tokens on success, address fields included), then pull everything you need about the property. One API, one key, no second integration required.

Request

curl --get "https://api.homedata.co.uk/address/match/" \
  --data-urlencode "address=10 Downing Street" \
  --data-urlencode "postcode=SW1A 2AA" \
  -H "Authorization: Api-Key YOUR_API_KEY"
# 200: address-level retrieve body plus address_resolution; 5 tokens.
# 422: reason no_match or multiple_matches; never charged.
# Use the returned UPRN for further property data.

Illustrative HTTP 200 excerpt: address match

{
  "uprn": "10002210501",
  "address": "10 Downing Street, London",
  "postcode": "SW1A 2AA",
  "address_resolution": {
    "resolution_grade": "exact",
    "matched_address": "10 Downing Street, London, SW1A 2AA",
    "flagged": false
  }
}

getAddress would stop after returning the address string. Homedata returns the property too: same API, same key, one more call.

One API for address + property data.
Transparent pricing, no surprises.

Pay as you go: 100 tokens = £1, first top-up matched 100%. Address match (5 tokens on success), retrieve (5), plus 40+ property data endpoints from one key. One API, one integration.