UK Land Data API - Parcels, Planning, Titles, Owners avatar

UK Land Data API - Parcels, Planning, Titles, Owners

Pricing

from $18.00 / 1,000 land parcel returneds

Go to Apify Store
UK Land Data API - Parcels, Planning, Titles, Owners

UK Land Data API - Parcels, Planning, Titles, Owners

UK land and planning data: search land parcels in any local authority by size and tenure, read the HM Land Registry titles and registered owners behind them, the planning applications on them, the properties inside them, and the flood, green belt, heritage and allocation layers that cover them.

Pricing

from $18.00 / 1,000 land parcel returneds

Rating

0.0

(0)

Developer

Nabeel Hassan

Nabeel Hassan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

UK Land Data API - Parcels, Planning, Titles and Owners

Find a UK development site, then find out who owns it, what has been applied for on it, and what stops you building on it.

What it collects

  • Land parcels by local authority, filtered on size in square metres and on freehold or leasehold tenure, with the ratio of each parcel that is already developed.
  • Ownership from HM Land Registry: title number, tenure, registered addresses, registered proprietors with company numbers and countries, and the ultimate owner behind a holding company.
  • Planning applications at a point or inside a polygon: the authority's reference, the proposal, the number of residential units, the authority's own status and the derived status side by side, the decision and its date, the applicant and the agent, and the link to the authority's page.
  • Properties by UPRN: full address, property type and state, Ordnance Survey classification, planning use class, building height and roof height in metres, estimated floor count, and current and potential EPC ratings with certified floor area.
  • Site designations: flood zones, green belt, conservation areas, listed buildings, airport and rail safeguarding, rights of way, agricultural land classification, regeneration areas, brownfield register entries, land availability assessments, Homes England sites, power infrastructure, strategic industrial locations and renewable energy sites.
  • Coverage fractions on every constraint and policy, so a flood zone clipping one corner of a site never reads the same as one covering all of it.

FAQ

What data does this UK land API return?

Land parcels with size and developed-area ratio, HM Land Registry title numbers and registered owners, planning applications with status and decision, properties with UPRN, height and EPC data, and the planning constraint, allocation and opportunity layers covering a site. Coverage is England, Wales and Scotland by local authority, addressed through Office for National Statistics GSS codes.

How do I find out who owns a piece of land in the UK?

Search parcels in the local authority, read the parcel's details to get its HM Land Registry title numbers, then run title details on those numbers. Each title returns its registered proprietors, their company numbers and countries of registration, the date ownership last changed, and the ultimate owner where the registered proprietor is a holding company.

Can I search planning applications by location?

Yes. Planning search takes a latitude and longitude pair or a GeoJSON polygon and returns every planning application the provider holds for that area, grouped by planning authority. Each application carries its reference, proposal description, unit count, status, decision and dates. Give the pair as latitude first; the actor converts it to the longitude-first order the API expects, so a swapped pair cannot quietly return a real place somewhere else.

What is a GSS code and where do I get one?

A GSS code is the Office for National Statistics identifier for a UK local authority, written as one letter and eight digits, such as E06000023 for Bristol. Run the list regions mode to get every code this API accepts along with the authority name.

Do searches return full records?

Searches on this API return identifiers rather than records: up to 100,000 parcel IDs, or planning references grouped by authority. This actor reads the full record behind each identifier by default, and applies your row cap before the lookups so a search returning thousands of identifiers does not spend thousands of calls filling a small run. Turn hydration off to collect identifiers only.

Why is the full boundary missing from my rows?

Geometry is off by default, because a multipolygon in a spreadsheet cell is size without use. Every row already carries a centre point. Turn on full geometry to get the GeoJSON ring, which also switches the site feature modes from the provider's geometry-free endpoint to its full one.

Do I need my own API key?

Yes. This actor is bring-your-own-key: it calls the provider with your own account credentials and never ships a key of its own. Paste the key on its own rather than a whole header line. The account status mode checks the key works, and tells apart a key the provider does not recognise from a key it does recognise on a subscription that has expired or been blocked.

What does it cost?

Pay per result. Parcels and titles are the richest rows and cost the most; parcel identifiers and planning references cost a fraction of a hydrated record; the region catalogue and the account status check are priced near zero so you can run them before committing to a large job. Platform usage is included. Rows for identifiers the provider has no record for are never charged.

Example output

{
"recordType": "parcel",
"requested": "E06000023",
"found": true,
"parcelId": "1a2b3c4d5e6f",
"parcelSizeSqm": 18336.97,
"developedAreaRatio": 0.2865,
"titleNumbers": ["K375897", "TT17693"],
"titleCount": 2,
"uprns": ["50121170", "50100934"],
"intersectingUprns": ["10091868676"],
"planningApplicationIds": ["E07000112+Y18/1381/FH"],
"planningApplicationCount": 1,
"developmentConstraints": "flood_zone_2 (34%); rail_safeguarded_land (100%)",
"developmentOpportunities": "brownfield_register (54%)",
"localPlanPolicies": "local_planning_authority (100%); settlement_boundaries (54%)",
"latitude": 51.454514,
"longitude": -2.58791
}

Keyword map

UK land data API, land registry ownership API, land parcel search API, planning application API, UK planning data API, site sourcing API, land assembly data, freehold leasehold title lookup, UPRN property lookup API, EPC data API, green belt flood zone constraints API, SHLAA land availability data, brownfield register API, development opportunity data, GSS code local authority search.

Notes

Bring your own key. Read only: every route this actor calls reads data, so a scheduled run cannot change anything in your provider account. Rate limiting, retries and per-endpoint batch ceilings are handled for you, and a missing or refused key ends the run cleanly with an explanation rather than failing it.