Switch to Homedata
in under 15 minutes.
Drop-in code examples for every major UK property data provider. Same endpoints you're used to: more data in every response.
Choose your current provider
Click your provider for a step-by-step migration guide with code diffs.
getAddress.io
Submitted address matching plus a separate browser widget for autocomplete. The matching API requires both address and postcode.
View guide ↓Ideal postcodes
Postcode lookup and submitted address matching. Use the browser widget for autocomplete; backend API calls use an API key header.
View guide ↓PropertyData.co.uk
Property analytics + prices. Same data, better structure. Homedata returns UPRN-level detail.
View guide ↓Loqate (GBG)
Address verification + cleansing. Submit address and postcode to address match for one property; use the browser widget for typeahead.
View guide ↓Sprift
Property data packs. Homedata gives the same data via API (EPC, flood risk, prices, title info) without manual reports.
View guide ↓StreetData
Postcode-level property data. Homedata offers the same at UPRN level: individual property records, not postcode averages.
View guide ↓Every migration follows 3 steps
Get your API key
Get an API key, pay as you go, 100 tokens = £1, no subscription needed. Bonus tokens with an optional monthly subscription. Your key is ready in seconds.
Swap the endpoint
Replace the old provider URL with the Homedata equivalent. Auth moves to an Authorization header.
Map the fields
Homedata returns richer responses. Map the fields you need: everything from your old provider is there, plus bedrooms, EPC, floor area, and more.
Migrate from getAddress.io
getAddress uses a postcode + house number lookup. Homedata address match requires both address and postcode and returns one property with its UPRN. HTTP 200 costs 5 tokens; HTTP 422 no_match or multiple_matches is never charged.
curl "https://api.getAddress.io/find/SW1A2AA?api-key=YOUR_KEY"
# Response:
{
"postcode": "SW1A 2AA",
"latitude": 51.50354,
"longitude": -0.12768,
"addresses": [
"10 Downing Street, , , , , London, "
]
}
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.
What you gain
- ✓ UPRN: unique property identifier for every address (getAddress doesn't return this)
- ✓ Structured fields: address_line_1, address_line_2, town, postcode (not a comma-separated string)
- ✓ Submitted address matching, both address and postcode required
- ✓ Property data on retrieve: pass the UPRN to get bedrooms, EPC, floor area, last sold price
- ✓ Pay as you go: 100 tokens = £1, first top-up matched, vs getAddress's pay-per-lookup model
Full comparison: Homedata vs getAddress.io →
Migrate from ideal postcodes
Ideal Postcodes uses a postcode lookup endpoint. Homedata's postcode endpoint returns the same addresses, each with a UPRN that chains into the property endpoints for enrichment.
curl "https://api.ideal-postcodes.co.uk/v1/postcodes/SW1A2AA?api_key=YOUR_KEY"
# Response:
{
"result": [
{
"postcode": "SW1A 2AA",
"line_1": "10 Downing Street",
"line_2": "",
"post_town": "London",
"uprn": "100023336956"
}
]
}
curl -H "Authorization: Api-Key YOUR_KEY" \
"https://api.homedata.co.uk/address/postcode/SW1A2AA/"
# Response:
{
"postcode": "SW1A 2AA",
"addresses": [
{
"uprn": 100023336956,
"address": "10 Downing Street, London, SW1A 2AA"
}
]
}
Key differences
- ✓ Auth in header:
Authorization: Api-Key xxxinstead ofapi_key=query param - ✓ Property enrichment: every address returns a UPRN, which chains straight into the property endpoints for bedrooms, EPC, floor area and last sold price
- ✓ Area statistics: a second call to the postcode-profile endpoint returns median prices, property type breakdown and broadband speeds for the same postcode
- ✓ Pay as you go: 100 tokens = £1 and your first top-up is matched. Ideal Postcodes charges from the first lookup.
Full comparison: Homedata vs Ideal Postcodes →
Migrate from propertyData.co.uk
PropertyData focuses on area-level analytics. Homedata provides both area stats and individual property records via API.
import requests
# PropertyData: area-level metrics only
r = requests.get(
"https://api.propertydata.co.uk/prices",
params={"key": "YOUR_KEY", "postcode": "SW1A 2AA"}
)
data = r.json()
# Returns: average_price, median_price, transaction_count
# No individual property records
import requests
headers = {"Authorization": "Api-Key YOUR_KEY"}
# Individual property lookup by UPRN
r = requests.get(
"https://api.homedata.co.uk/properties/100023336956/",
headers=headers
)
prop = r.json()
# Returns: bedrooms, bathrooms, epc_rating, epc_score,
# floor_area_sqm, last_sold_price, last_sold_date,
# construction_age, tenure, property_type,
# flood_risk, noise_level, deprivation_score...
What you gain
- ✓ UPRN-level data: individual property records, not just postcode averages
- ✓ Comparable sales: 20 nearest sold prices for any property
- ✓ Price trends: 12 months of monthly median asking prices by outcode
- ✓ Environmental risk: flood, radon, noise, air quality per property
- ✓ Transparent pricing: published token pricing (100 tokens = £1) vs PropertyData's opaque enterprise quotes
Full comparison: Homedata vs PropertyData →
Migrate from Loqate
Loqate uses a find/retrieve two-step pattern. Homedata address match requires address and postcode. HTTP 200 includes address fields plus address_resolution for 5 tokens; HTTP 422 no_match or multiple_matches is never charged.
// Step 1: Find
const find = await fetch(
`https://api.addressy.com/Capture/Interactive/Find/v1.1/json3.ws?Key=${key}&Text=10+downing`
);
const { Items } = await find.json();
const id = Items[0].Id;
// Step 2: Retrieve
const retrieve = await fetch(
`https://api.addressy.com/Capture/Interactive/Retrieve/v1/json3.ws?Key=${key}&Id=${id}`
);
// Returns: address lines only
// Run on your server; keep the API key out of browser code.
const headers = { Authorization: `Api-Key ${process.env.HOMEDATA_API_KEY}` };
const params = new URLSearchParams({
address: '10 Downing Street', postcode: 'SW1A 2AA',
});
const response = await fetch(
`https://api.homedata.co.uk/address/match/?${params}`, { headers },
);
const matched = await response.json();
if (response.status === 422) {
throw new Error(`Check the address: ${matched.reason}. No charge.`);
}
if (!response.ok) throw new Error(`HTTP ${response.status}`);
console.log(matched.uprn, matched.address_resolution);
Key differences
- ✓ Submitted address matching: both address and postcode required
- ✓ UPRN as identifier: universal, permanent, government-standard (not a proprietary ID)
- ✓ Retrieve returns the property, not just address lines, but the full property record
- ✓ Simple auth: one API key in a header vs Loqate's key-per-service model
- ✓ Transparent pricing: pay as you go, 100 tokens = £1. No sales calls, no minimum contracts.
Full comparison: Homedata vs Loqate →
Migrate from sprift
Sprift delivers property data as manual reports or CRM integrations. Homedata delivers the same data categories via API: programmatic, real-time, no manual steps.
Data mapping
| Sprift Data | Homedata Endpoint | Difference |
|---|---|---|
| EPC certificate | /properties/{uprn}/ | Rating + score + certificate date |
| Flood risk | /properties/{uprn}/ | 4 risk categories, colour-coded |
| Price history | /properties/{uprn}/ | Full transaction log |
| Comparable sales | /comparables/{uprn}/ | 20 nearest sold prices. Arranged per customer rather than sold self-serve; the same evidence is included in the complete property profile. |
| Planning apps | /planning/search/ | Nearby applications |
| Area demographics | /postcode-profile/ | IMD, broadband, property mix |
Full comparison: Homedata vs Sprift →
Migrate from streetData
StreetData provides postcode-level aggregate data. Homedata provides UPRN-level property records: individual properties, not averages.
What changes
- ✓ UPRN-level records: query individual properties, not postcode averages
- ✓ Live listings: current for-sale/rental properties with prices and agents
- ✓ Bulk export: download filtered datasets as CSV/JSON via API
- ✓ Self-serve: sign up, get key, start querying. No sales process.
Full comparison: Homedata vs StreetData →
Ready to switch?
Get your API key now. Pay as you go, 100 tokens = £1, no subscription needed, no sales call. Bonus tokens with an optional monthly subscription. Most migrations take under 15 minutes.