UPRN Lookup — UK Property Reference Numbers

What is a UPRN?

The Unique Property Reference Number (UPRN) is a 12-digit identifier assigned to every addressable property in the United Kingdom. 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.

UPRN format

• 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

UPRN vs USRN vs UDPRN

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

• UPRN — Unique Property Reference Number. Identifies a property. Issued by GeoPlace.
• USRN — Unique Street Reference Number. Identifies a street, not a property.
• UDPRN — Unique 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.

Why UPRNs matter

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 12-digit 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.

UPRN resolution via the Homedata API

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-find 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 available on the free tier (100 requests per month, no card required). Bulk resolution and higher rate limits are available on paid plans starting at £49 per month.

When you don't need a UPRN

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.