UPRN lookup: find a UPRN for an address.

The Unique Property Reference Number (UPRN) is an identifier of up to 12 digits assigned to every addressable property in Great Britain. UPRNs are issued by GeoPlace, a partnership between Ordnance Survey and the local-government Local Government Association, and are derived from the National Address Gazetteer.

Each UPRN identifies a single, addressable place: a flat, a house, a commercial unit, a parcel of land. Once issued, a UPRN never changes: properties can be renumbered, renamed, merged or split, but the underlying identifier remains stable. That stability makes UPRN the canonical key for joining UK property records across systems and over time.

UPRNs were originally locked behind commercial Ordnance Survey licences. In July 2020 the underlying dataset was opened, and the OS Open UPRN dataset is now published under the Open Government Licence: the IDs themselves are free, but bulk download, refresh cadence, and address-matching workflow remain a non-trivial engineering effort.

• Numeric only, no letters or hyphens
• 1 to 12 digits long; most modern UPRNs are 12 digits
• Not sequential, geographic, or otherwise meaningful: treat as an opaque key
• Stable: never reissued, never reassigned

Three identifiers are commonly mixed up. They identify different things:

• UPRNUnique Property Reference Number. Identifies a property. Issued by GeoPlace.
• USRNUnique Street Reference Number. Identifies a street, not a property.
• UDPRNUnique Delivery Point Reference Number. Identifies a Royal Mail postal delivery point. Useful for postage; weaker for property-level data joins because a single property can have multiple UDPRNs (or none).

For property-data work, UPRN is almost always the right key.

For surveyors and conveyancers

Matching addresses by free-text string is error-prone: abbreviations, typos, formatting differences, and address-line order all break naive joins. UPRN avoids the problem entirely: a single numeric key joins Land Registry title data, EPC certificates, planning history, building regulations applications, and flood records to the same property.

For landlords and portfolio managers

UPRN is a stable primary key for property-management systems. It survives tenancy changes, postal-address reformatting, and database migrations. Portfolios indexed by UPRN can quickly retrieve EPC ratings, MEES compliance status, and council tax bands without per-property string-matching.

For developers and proptech platforms

Free-text address inputs are a perennial source of data quality problems. Replacing them with UPRN-driven lookup eliminates duplicates, prevents typos breaking matches, and lets you enrich every record with EPC, Land Registry, planning, and risk data. Two API calls, address resolution then property retrieval, return a complete UPRN-keyed property record.

For commercial UPRN resolution and property enrichment at scale, the Homedata UPRN API provides programmatic access. Two primary workflows:

1. Address-to-UPRN resolution. Submit a free-text address or postcode to the address-match endpoint. The API returns the matched UPRN and a confidence score. Free-text fuzzy matching handles abbreviations, ordering differences, and typos.
2. UPRN-to-property retrieval. Once you have a UPRN, the property-retrieve endpoint returns the joined record (type, beds, EPC band, last sold price, listing event history, environmental risk, council tax band, and 40+ attributes) in a single response.

Both endpoints are pay as you go: 100 tokens = £1, and a monthly subscription earns bonus tokens.

UPRN is overkill for some tasks: simple address validation, postcode-to-coordinate conversion, or free-text postcode lookup. For these, lighter address-validation services may be cheaper. UPRN's value comes from its role as a join key for property data: if you're not joining records, you may not need it at all.

UPRN-matched property records

Resolve a free-text address to its UPRN and receive the joined property record (type, beds, EPC band, sold price history, environmental risk) in a single response.

Addresses across the UK

Backed by a dataset of over 36 million addresses covering England, Wales, Scotland and Northern Ireland, through a single licensed feed.

Built for scale

Bulk address-matching, deduplication, and UPRN enrichment: available to every account, paid per row in tokens. Sub-second response on the property-record endpoint.

No bulk download required

Skip the OS Data Hub workflow. No CSV imports, no GeoPackage parsing, no quarterly refresh cycle. The API stays current.

A UPRN is a Unique Property Reference Number: an identifier of up to 12 digits assigned by GeoPlace to every addressable property in Great Britain. It is the canonical key used to join Land Registry, EPC, planning, council tax, and address data.

For one address, create a Homedata account, top up and use address lookup in your dashboard. A successful match returns the UPRN and costs 5 tokens (5p). For a list, send each address and postcode to the API. OS Open UPRN is a bulk download of identifiers and coordinates; it contains no address text.

UPRN identifies a property (a building or land parcel). USRN identifies a street. UDPRN identifies a Royal Mail postal delivery point. UPRN is the most useful identifier for joining property records across UK government data services.

In Scotland, yes: UPRNs cover Great Britain (England, Wales and Scotland), and the OS Open UPRN dataset covers Great Britain only. Northern Ireland addresses are held in a separate database (Pointer) and are not included in OS Open UPRN.

The OS Open UPRN dataset is published under the Open Government Licence. The Homedata UPRN resolution API is pay as you go: 100 tokens = £1, 5 tokens on a successful match, first top-up matched 100%.

Yes. Once you have a UPRN you can join it to Land Registry sold price records, the EPC register, planning application history, council tax bands, and environmental risk data. The Homedata API returns these joined records via a single call.

No: UPRNs are numeric only, with no letters. They are 1 to 12 digits long, with most modern UPRNs being 12 digits.

Yes. UPRNs are issued at the planning-approval or address-creation stage, before completion. New builds appear in the OS Open UPRN dataset within a few months of address creation.

Yes. The Homedata API supports address-to-UPRN resolution at scale. Submit an address and postcode to address match. HTTP 200 returns the address-level retrieve body plus address_resolution for 5 tokens. HTTP 422 no_match or multiple_matches is never charged. Bulk resolution is available to every account: the only limit is your token balance.

Addresses captured via free-text input forms, third-party lists, or non-UK sources typically have no UPRN attached. To UPRN-enrich an address list, run each address string through an address-matching API such as Homedata's, which uses fuzzy matching to resolve free-text input to its most likely UPRN.