OS Places API: What It Does, What It Costs and the Alternatives
Kees Van Den Broek, Founder

OS Places API: What It Does, What It Costs and the Alternatives
If you search for a UK address API, Ordnance Survey comes up first, and for good reason: OS Places is built on the most complete addressing dataset in Great Britain. Whether it is the right choice for your project is a separate question, and it usually comes down to licensing rather than data quality.
This article is a fair description of what OS Places is, followed by an honest look at the alternatives, including where we fit and where we do not.
What the Ordnance Survey Places API is
OS Places is Ordnance Survey's address lookup web service, available through the OS Data Hub. You send it a postcode, a partial address, or a UPRN, and it returns matching addresses from AddressBase, with coordinates.
It supports the query patterns you would expect: find by postcode, free-text search across the address, find by UPRN, and nearest-address to a coordinate. It is a mature, well-documented service used widely across UK government and the public sector, and it is what NHS systems use for validating patient addresses.
What you get: AddressBase, UPRN and coverage
The value is in the underlying data. AddressBase combines Royal Mail's Postcode Address File with local authority Local Land and Property Gazetteer data and OS's own mapping. That combination matters because it includes addresses that are not postal delivery points: properties under construction, sites without letterboxes, and objects that a local authority needs to reference but Royal Mail does not deliver to.
The UPRN, the Unique Property Reference Number, is the identifier attached to each of those addressable locations. It is stable over time, which makes it the reliable way to match records between systems, and it is why public sector data so often keys on it.
Coverage is Great Britain. Northern Ireland is addressed through a separate arrangement, which surprises teams who assumed "UK" throughout.
Licensing and cost: the part that surprises people
OS Places is a premium API. AddressBase is licensed data, not open data, so access is priced rather than free, and the terms constrain what you may do with the results as much as the price constrains how many you may request.
Three things to check before you build on it:
- Which plan applies to you. Public sector organisations covered by the Public Sector Geospatial Agreement access OS data on very different terms from a commercial startup. If you are in the first group, OS Places is often the obvious answer. If you are in the second, do the arithmetic first.
- What you are allowed to store. Licensed address data usually comes with retention and redistribution constraints. Caching results in your own database may be limited, and passing them to a third party is normally restricted.
- How usage is counted, and what happens when you exceed the free allowance rather than simply what the allowance is.
None of this is a criticism of OS. It is how licensed national address data works everywhere, and the same considerations apply to any provider reselling PAF.
When OS Places is the right choice
Choose it without much deliberation when:
- You are a public sector body with PSGA access, in which case cost is largely resolved.
- You need UPRNs as a first-class output, particularly to join against other public datasets.
- You need non-postal addressable objects, not just delivery points.
- You need the most complete GB coverage available and the budget follows the requirement.
Alternatives to OS Places API
The realistic options, with their honest trade-offs:
PAF resellers such as Ideal Postcodes, Postcoder, getAddress.io and similar UK specialists. They license Royal Mail data and wrap it in developer-friendly APIs with simpler pricing. You get delivery-point addresses and usually UPRNs; you generally do not get the full non-postal AddressBase picture.
Open-data services built on the ONS Postcode Directory, such as postcodes.io. Genuinely free, no licensing complexity, and excellent for what they cover: postcode-level data, coordinates and administrative areas. They do not return the individual addresses within a postcode, because PAF and AddressBase are not open.
OpenStreetMap-based services. OpenStreetMap does carry individual addresses, under an open licence that allows storage and reuse. It is maintained by contributors, so completeness varies by area, and it has no UPRNs.
Global platform APIs from Google, Mapbox and similar. Strong international coverage and good developer experience, with licence terms that often restrict storing or displaying results outside their own map, which is a poor fit for a records system.
Cross-border address APIs such as Pro6PP. Our address lookup, validation, autocomplete and geocoding cover England alongside the Netherlands, Belgium, Germany, France, Italy, Luxembourg, Denmark, Austria, Switzerland and Spain, with global reverse geocoding, all on one key and one response format. The trade-offs are real. Our English addresses come from OpenStreetMap rather than PAF or AddressBase, so coverage is less complete than OS Places; we return no UPRNs; and Scotland, Wales and Northern Ireland are not covered at address level yet. If you need complete GB coverage or UPRNs, OS Places is the better fit. If your addresses cross the Channel, one integration beats two.
How to choose
Work backwards from the constraint that actually binds you. If it is UPRNs and non-postal addressable objects, that points at OS. If it is postcode-level analysis, open data is free and sufficient. If it is a commercial checkout, what matters is latency, response quality and how the pricing behaves at your volume. And if your addresses cross borders, coverage beyond the UK matters more than the depth of any single country, which is where a cross-border API earns its place. In that case it helps to be clear first on what validation and verification actually promise.
Where each of these options fits, and where UK address data comes from in the first place, is laid out in our overview of UK postcode and address lookup APIs.
Frequently asked questions
What is the OS Places API?
It is Ordnance Survey's address lookup service, available through the OS Data Hub. It returns addresses from AddressBase by postcode, free-text search, UPRN or nearest coordinate.
Is the OS Places API free?
No, it is a premium API built on licensed data, though the OS Data Hub includes a free allowance and public sector organisations under the Public Sector Geospatial Agreement access it on different terms. Check which plan applies to you before estimating cost.
What is the difference between OS Places API and Royal Mail PAF?
PAF is Royal Mail's file of postal delivery points. AddressBase, which OS Places serves, combines PAF with local authority gazetteer data and OS mapping, so it includes addressable locations that receive no post and attaches a UPRN to each.
What is a UPRN?
A Unique Property Reference Number: a stable identifier for an addressable location in Great Britain. It is the standard key for matching address records between systems and against public sector datasets.
Does the OS Places API cover Northern Ireland?
OS Places covers Great Britain. Northern Ireland addressing is handled separately, so check this explicitly if you need UK-wide coverage.
