//Product
TravelTime Data API
Places, public transport, roads, open spaces, boundaries, demographics,
neighbourhood and proximity — eight data layers, aggregated by H3 cell
for any travel-time catchment.
8 data layers
POIs, public transport, open spaces, neighbourhood insights, demographics, and more
1 API
One HTTP API, queryable by coordinates, by H3 cell, geohash and bounding box
33 countries
Available in 33 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 eight data layers:
- Places: millions of points of interest, with addresses, categories and the registers that verify them
- Public transport: stations, stops and lines, with a count per mode for any area
- Roads: major roads and every entry and exit onto them
- Open spaces: named parks and green spaces, and how green each hexagon is
- Boundaries: the administrative boundary hierarchy, with cells for any division to feed into the other layers
- Demographics: population per cell, plus census data on households, age, renting, cars and income
- Neighbourhood: noise, air quality, flood risk, crime, deprivation and broadband
- Proximity: walk, transit and drive ratings and travel times to everyday essentials
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.
❯Places
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.
❯Public transport
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.
❯Open spaces
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.
❯Demographics
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.
❯Boundaries
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.
❯Neighbourhood
Local area insights
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.
Data API at a glance
Quick overview of TravelTime Data API specifications. Full documentation here.
| Data layers | Places, public transport, roads, open spaces, boundaries, demographics, neighbourhood, proximity |
|---|---|
| POI sources | Foursquare, OpenStreetMap, Overture — plus national government registers |
| POI taxonomy | 16 groups, three levels (group / category / detail) |
| Query methods | Coordinates and radius, bounding box, free text, H3 cell, geohash |
| H3 resolutions | 6 to 10 for POIs, 9 for population |
| Geohash precision | 6 to 7 |
| Confidence filtering | min_sources, 1–3, on independent source count |
| Authority overlays | Health, education, childcare, civic and EV locations from national registers |
| Coverage | 33 countries (and growing), one dataset per country |
| Country scoping | Not needed for location queries — the country is only set for name searches, and a location outside coverage returns an error |
| Output format | GeoJSON and a shared JSON envelope across every layer |
| Display restrictions | None |
| Pricing | Included in all TravelTime fixed cost plans. 120 HPM limit for Basic users. Contact us for a quote or sign up for a key to get started for free. |
TravelTime Data API demos
Discover how your business can use the TravelTime Data API.
//For marketplace & location search
AI-powered search
Natural-language AI search using real location reasoning: transport data, road networks, multi-modal routes, and our Data API.
Try demo
//For property portals
Location scoring
Score any home or location based on what your buyers care about, from walking times to broadband. Build custom scoring for your business.
Try demo
//For developers and location teams
Data API
Set your location and catchment, then dive into what's within reach, layer by layer: amenities, transport, green space, and more.
Try demo
A Google Places API alternative
All TravelTime data layers are included in our fixed-cost plans: accurate, high-quality places, local area insights, administrative boundaries and more — plus powerful journey time data, ready for you to build with.
Learn more
→Coverage
Each country is a separate dataset, built from source on its own cadence.
Coverage levels:
- Full data - All eight data layers.
- Partial data - Places, public transport and most other layers.
- Public transport only - Stations, stops and lines.
TravelTime Data API FAQs
Get the H3 cells reachable within a travel time from the TravelTime API, then send those cells to the Data API to find out what is in them — places, people, open space and more. The same application ID and API key work for both.
The Data API has full data in 33 countries, and we are adding 33 more. Public transport data — stations, stops and lines — covers a further 95 countries. The coverage page lists every country and the layers it has.
16 groups resolving through category to detail — automotive, business and services, culture, education, food and drink and more. The taxonomy is filterable at any of the three levels, so you can request all of food and drink or only bakeries.
Every place carries a count of the independent sources that list it, and you choose how many are required, from one to three. Places confirmed by a government register, such as the NHS, CQC or Food Hygiene Rating Scheme, are marked as verified.
It's derived from timetable feeds but not served raw. Stops are grouped into stations and departures per hour are attached for peak, off-peak, evening and weekend, so a station is a station rather than a set of platforms and poles.
Named parks, gardens, woods, heaths and beaches, pre-aggregated to H3 cells so you can measure how green any area is, including the countryside. You can also look up a named open space and get the cells it covers.
WorldPop gridded population per cell, plus small-area census demographics and income where a country's statistics office publishes them. Where the census has no data for a cell, the field is returned as null with the reason, rather than as zero.
Noise, air quality, flood risk, crime, deprivation and broadband per H3 cell, or totalled across an area. Every value names its source, so you know who published it and when.
Local authorities and other administrative divisions, yes — browse the hierarchy, request any division's H3 cells, then query any layer against them. UK boundaries carry their GSS codes. Postcode districts are not included.
Major roads with every entry and exit onto them, and proximity: walk, transit and drive ratings from 0 to 100, with travel times to everyday essentials, for any H3 cell.
Each country is a separate dataset, refreshed on its own cadence. Every dataset reports the date it was last loaded, so you always know how current it is.
JSON by default, or GeoJSON as a FeatureCollection. Long results are paged with a cursor.
Up to 120 requests per minute per application, across all Data API endpoints. Contact us if you need a higher limit.
Yes, where a source requires it. OpenStreetMap data, for example, is licensed under the ODbL, and the attribution page lists the wording for every source.