//Product (beta)

TravelTime Data API

Points of interest, public transport, land cover, population, environment
and administrative areas — six data layers, aggregated by H3 cell
for any travel-time catchment.

Request access data to Data API beta

6 data layers

POIs, public transport, land cover, population, areas & boundaries, and environment

1 API

One HTTP API, queryable by coordinates, by H3 cell, geohash and bounding box

14 countries

Available in 14 countries, with continuously growing coverage and datasets

Billions of stops

Billions of transit stops mapped across the globe, for routing and catchments


TravelTime Data API returns six data layers:

  • Points of interest: Millions of amenities, including Culture, Education, Transportation, Shopping categories
  • Public transport: stations, lines, agencies and service frequency from TravelTime's own transport graph
  • Land cover: parks, green space and beaches, stored as H3 aggregates so you can ask what share of an area is open space
  • Population and census: population per cell, plus small-area demographics and income
  • Environmental: noise, pollution, flood risk. crime, and more data available to build a better picture of an area.
  • Areas: the administrative boundary hierarchy, with cells for any division to feed into the other layers

What is a POI database?

A POI database is a structured collection of places — their names, coordinates, categories, addresses and attributes — that applications query to answer, "what is here?".

TravelTime Data API gives you access to our POI data layer. Foursquare, OpenStreetMap and Overture are matched into one layer, with authoritative government registers added per country, and a source-count signal on every record.

Read more

//POIs · GB · H3 catchment

Try TravelTime Data API

Full Playground

API lite demo

Location
Travel time (weekday morning)
30 min
Mode of transport
Public transport

Data API at a glance

Quick overview of TravelTime Data API specifications.

Data layersPoints of interest, public transport, land cover, population and census, administrative areas
POI sourcesFoursquare, OpenStreetMap, Overture — plus national government registers
POI taxonomy16 groups, three levels (group / category / detail)
Query methodsCoordinates and radius, bounding box, free text, H3 cell, geohash
H3 resolutions6 to 10 for POIs, 9 for population
Geohash precision6 to 7
Confidence filteringmin_sources, 1–3, on independent source count
Authority overlaysHealth, education, childcare, civic and EV locations from national registers
Coverage14 countries (and growing) one dataset per country. CONFIRM
Country scopingRequired per request — cross-border queries are rejected, not silently served
Output formatGeoJSON and a shared JSON envelope across every layer
Response timesCONFIRM
Display restrictionsNone.
PricingFree for non-commercial use, and included in the commercial production plan — with no limits on usage.

❯01 Data layer

Global points of interest dataset

Millions of POIs — shops, restaurants, schools, pharmacies, stations, car parks — broken in 16 groups, with further categories and details.

Build location scoring, integrate into your search or site analysis, with an accurate data layer at the core.

POI Documentation

❯02 Data layer

Public transit stops and lines

Stations, lines, agencies and service frequency for every market TravelTime covers, drawn from the transport graph behind our journey time models.

Answer whether a place is genuinely connected, not just whether a station appears nearby. Build commute scoring, accessibility ratings, and assess site viability for anywhere that matters to you and your customers.

Public transport documentation

❯03 Data layer

Green space and land cover

Named parks, green space and beaches, pre-aggregated to H3 cells across every covered country.

Build coverage maps instead of sourcing, clipping and intersecting polygons yourself. And the geometry is still there when you want to draw it rather than measure it.

Green space and polygons documentation

❯04 Data layer

Population and census data

Get population per H3 cell, plus small-area demographics and income wherever a national statistics office publishes them.

Aggregate across a whole catchment in a single call with ease — and layer with other data like POIs, green spaces, and TravelTime’s routing calculations, to measure true accessibility.

Population documentation

❯05 Data layer

Administrative boundaries

Every country's administrative hierarchy as published — local authorities, counties, census divisions, and the levels below them.

Ask any division for its H3 cells, then query every other layer against them. Report in the geographies your regulator or client uses, while analysing in travel time.

Area documentation

❯06 Data layer

Environmental data

Understand noise, air quality, flood risk, deprivation, broadband, and crime.

Build a picture of what an area is like — so a catchment can be scored on liveability, risk or connectivity. Every signal carries its own publisher and vintage.

Environmental documentation

A Google Places API alternative

All data layers included for
free in your TravelTime plan

Learn more
Google Maps→

Coverage

Each country is a separate dataset, built from source on its own cadence.

Coverage levels:

  • Full coverage - Places, public transport, population, green space and environment data.
  • Core coverage - The same, without environment data.
  • Transport only - Public transport data.
See the full inventory

TravelTime Data API FAQs

16 groups resolving through category to detail — retail, food and drink, healthcare, education, transport, leisure and more. The taxonomy is filterable at any of the three levels, so you can request all healthcare or only GP surgeries.

It's derived from timetable feeds but not served raw. Stops are clustered into stations and service frequency is attached, so a station is a station rather than a set of platforms and poles.

Named parks, green space and beaches, pre-aggregated to H3 cells so you can measure what share of an area is open space. Underlying polygons are available where you need the geometry itself.

WorldPop gridded population per cell, plus small-area census demographics and income where a country's statistics office publishes them. Cells with genuinely unknown population are reported as unknown rather than zero.

Administrative divisions, yes — browse the hierarchy and request any division's H3 cells, then query any layer against them.


Get started with
TravelTime Data API