TravelTime Data API

The TravelTime Data API gives you places, public transport, roads, population, green space and environment data through one HTTP API. You can query it by coordinate, by H3 cell or by geohash.

These docs explain each dataset, show how to query it, and list every endpoint.

What data you get

Each Data API dataset has its own page.

Dataset	What it contains	Endpoint to start with
Points of interest	Cafés, schools, pharmacies, shops and more, in 16 category groups. Each place has a name, location, category, brand and `verified` field.	`GET /v1/pois/near`
Public transport	Stations, lines and operators, with the number of services in a typical weekday morning.	`GET /v1/pt/stations/near`
Roads	Motorway entrances and exits in the US, with the motorway and direction each one leads onto.	`GET /v1/roads/access-points/near`
Population and areas	Residents per H3 cell, census demographics where a country publishes them, and administrative boundaries.	`GET /v1/h3/population`
Green space	Parks, forests, gardens and other open land, as named polygons and as area per H3 cell.	`GET /v1/h3/land-cover`
Environment	Noise, air quality, flood risk, deprivation, broadband and crime per H3 cell, from government open data.	`GET /v1/h3/environment`

Not every country has every dataset. See what's available in each country.

Use it with the TravelTime API

The TravelTime API calculates where you can get to within a travel time. The Data API tells you what is there. Both use the same H3 grid. You can pass the cells from one API to the other.

Get the reachable cells from POST /v4/h3/fast, then send them as cells to a Data API endpoint such as GET /v1/h3/pois.

bash

curl -H "Authorization: Bearer $POI_API_KEY" \
  "$POI_BASE/v1/h3/pois?country=GB&cells=89195da494bffff,89195da4947ffff"

Use with the TravelTime API shows both requests.

Base URL and authentication

The base URL is https://beta.poi.traveltimeapp.com. Every request needs an API key.

Get a key at /signup. Enter your email and we email you a confirmation link. Press it and we show your key, starting with poi_live_, on screen, then email you a copy. We store a hash of the key, so we cannot send that same key again after that.

Set two environment variables and every example in these docs runs as written:

bash

export POI_BASE="https://beta.poi.traveltimeapp.com"
export POI_API_KEY="poi_live_..."

Send the key as a bearer token on every request. This request lists the countries the Data API covers.

bash

curl -H "Authorization: Bearer $POI_API_KEY" \
  "$POI_BASE/v1/countries"

A missing, malformed or revoked key returns 401 Unauthorized from every /v1/* endpoint.

Lost or leaked key

Sign up again at /signup with the same email. We email you a confirmation link. When you click it, we revoke the old key and send a new one. The old key works until you confirm.

Rate limits

A key allows 10 requests per second and 20,000 requests per day. Above either limit the response is 429 with a Retry-After header. Both caps are enforced per worker process — production runs 4 workers, each with its own bucket — so the ceiling a key can actually reach is up to 4× either number.

Versioning

Paths under /v1 are a stable contract. Breaking changes go to /v2. Endpoints in the live schema that are not in these docs can change.

Get help

Where next

Quickstart: get a key and make your first two requests.
Query by coordinate, H3 cell or geohash: choose a query type.
Use with the TravelTime API: get the data inside a travel time.
Data: what is in each dataset, where it is available and how reliable it is.
Data updates: how often the data changes and how to check its date.
API reference: every endpoint and parameter.
Errors: every error code and what to show your users.