Product
TravelTime Isochrone API
Generate the area reachable within a set travel time by car, public transport, bike or on foot.
With Isochrone API you can:
- Generate isochrones for driving, public transport, cycling and walking
- Send multiple locations in a single request for bulk analysis
- Model travel times <4 hours, with off-peak and peak data, arrival and departure times
- Run unlimited requests on a fixed annual price, with no per-call charge
What Isochrone API returns
TravelTime Isochrones API returns a polygon showing the reachable areas from a specific origin, based on a maximum travel time and transport mode. It features adjustable shape detail outputs include GeoJSON, KML and WKT.
Read moreTry TravelTime Isochrone API
Try free API keyAPI lite demo
Polygons for every transport mode
Public transport isochrones
Traffic-aware drive time polygons
Global multi-modal coverage
Isochrone API at a glance
Quick overview of TravelTime Isochrone API specifications.
| Transport modes | Driving, public transport, cycling, walking |
|---|---|
| Maximum travel time | 4 hours, all modes |
| Locations per request | 10 per search type (departure or arrival) |
| Combine polygons | Union and intersect, server-side |
| Time settings | Arrival and departure times and dates |
| Reproducible results | Yes — modelled from typical conditions, not live traffic |
| Shape detail | Fully customisable |
| Output formats | GeoJSON, KML, WKT |
| Response times | Fast - under 300ms up to 3 hour isochrones |
| Display restrictions | No restriction - use your TravelTime polygons anywhere |
| Pricing | Fixed annual, unlimited requests |
Compare isochrone response times
Benchmarking drive time polygon response times from 100+ locations.
| Journey time |  |  |  |  |  |  |
|---|---|---|---|---|---|---|
| 10 min | 90 ms | 928 ms | 28 ms | 45 ms | 153 ms | 132 ms |
| 15 min | 102 ms | 1,046 ms | 42 ms | 50 ms | 297 ms | 355 ms |
| 30 min | 105 ms | 1,948 ms | 120 ms | 86 ms | 878 ms | 876 ms |
| 45 min | 113 ms | 3,698 ms | 251 ms | 162 ms | 2,040 ms | 3, 493 ms |
| 1 hr | 127 ms | 4,210 ms | 379 ms | 258 ms | 3,220 ms | 4, 011 ms |
| 90 min | 155 ms | N/S | 370 ms | 413 ms | N/S | 4, 904 ms |
| 2 hr | 184 ms | N/S | 502 ms | 505 ms | N/S | 11, 101 ms |
| 3 hr | 290 ms | N/S | 882 ms | 658 ms | N/S | Unknown |
vsGenerate isochrones in bulk
Multiple search locations
Unions and intersections
Remove post-processing
Reproducible isochrone results
Re-run calculations
Predict future travel times
Exclude live traffic anomalies
Pricing
How we price the TravelTime APIs
Get unlimited isochrones for a fixed annual subscription based on your capacity, support, and caching needs. Not a bill for every API call.
Chat to our team about pricingIsochrone FAQs
An isochrone API returns a polygon covering everywhere reachable within a set travel time from a location. You send an origin, a travel time and a transport mode; it returns a shape you can display on a map or join against your own data.
The TravelTime Isochrone API supports travel times up to four hours, across every transport mode. Google's Isochrones API caps driving at one hour, and walking and cycling at two. Mapbox caps all modes at one hour.
Yes. Public transport is modelled from published timetables rather than estimated from road speeds, so service frequency, interchanges and time of day are all accounted for. Google, Mapbox, and HERE support driving, cycling and walking only.
TravelTime Isochrone API accepts multiple search locations in a single request, and can union or intersect the resulting polygons server-side. Google only accepts one origin per request, so bulk work means one call per location.
Under 300 milliseconds at every drive time polygon benchmarked — 90ms for a 10-minute isochrone, 127ms for an hour, 290ms for three hours. Response times stay low as travel times grow, so isochrones can be generated inside a user-facing search rather than pre-computed. TravelTime also supports caching for even faster results.
Both. Departure searches show where you can reach from a location; arrival searches show where you can travel from and still arrive on time. Journey times reflect typical peak and off-peak conditions, so the same request returns the same polygon every time.
GeoJSON, KML and WKT. GeoJSON and KML load directly into QGIS and ArcGIS; WKT suits databases and warehouses such as PostGIS, Snowflake and BigQuery.
Yes. There's no requirement to use our own mapping libraries or SDKs, and no restriction on where the polygons appear. Mapbox requires Isochrone API results to be displayed on a Mapbox map using one of their libraries or SDKs.
A fixed annual price with unlimited requests, rather than per call — so cost is known before you build and doesn't grow with usage.