A clearer way to build with public data

One API for UK public data.

Less time navigating datasets. More time building.
Explore UK public data through a consistent developer experience—with sources you can trace.

Development preview No payment card required

UK data. One consistent shape.
  A first requestJSON
GET /v1/postcodes/SW1A%201AA
// Illustrative response, not a live API call
{
  "data": {
    "postcode": "SW1A 1AA",
    "country": "England",
    "region": "London"
  },
  "source": "Example source metadata",
  "retrieved_at": "2026-01-01T00:00:00Z"
}
Source-aware responsesREST + JSON
Built around the UK's public-data landscapePostcodes & geographyCompaniesEnvironmentProperty & places

Fewer moving parts

From public data
to something useful.

One place to understand the shape of your data, its origins, and how to work with it. No black-box answers.

A consistent starting point

Explore endpoint documentation, request formats and response contracts without learning a different integration pattern for every source.

Explore the documentation

Know where data comes from

Data responses name the source used and show when BritDatum retrieved it. Where a publisher supplies its own update time, that is shown separately.

Understand the sources

Made for developers

Readable JSON, explicit errors, useful examples and a place to try a postcode lookup before you build an integration.

Try the explorer

The web workspace is available in development preview. See the runtime guide for the limited read-only postcode API and its database prerequisite. Other dataset integrations and paid plans remain disabled.

Take a closer look

Start with a postcode.

Look up an area using the public Postcodes.io service. See a real response and its source, clearly separated from the developing BritDatum API.

Your next step

Build with the source in sight.

Read the integration guide or create a workspace to follow the product as it develops.