Skip to content

Travel-Time Isoline ​

A travel-time isoline (isochrone) is the area that can be reached within a given number of minutes, accounting for the road network and speed limits, and optionally traffic at a requested time.

Resource URL ​

https://www.mapquestapi.com/isoline/v1/time

Resource Information ​

HTTP MethodsGET, POST
Request FormatsURL query parameters, JSON body
Response FormatsJSON
AuthenticationRequires key query param
Rate LimitedYes

Direction ​

A request is either outbound or inbound, and exactly one of from or to must be supplied.

  • Outbound: reachable from a location. Start at from and optionally departAt. The result is the area that can be reached by traveling away from that point.
  • Inbound: can get to a location. End at to and optionally arriveBy. The result is the area from which that point can be reached, honoring one-way streets and turn restrictions in the inbound direction.

A request with both from and to, or that mixes from with arriveBy or to with departAt, is rejected.

Time and Traffic ​

Traffic is opt-in: giving a time is what requests traffic data.

  • No time (default). Without departAt or arriveBy, the isoline is time-independent: live and historical traffic are not used, but long-term road closures are respected. The same request returns the same result whenever it is made.
  • now. departAt=now or arriveBy=now uses traffic conditions at the time of the request.
  • A specific time. Live and historical traffic for that time and day of the week are used.

Request Parameters ​

Request ParameterDescriptionRequired
key
String
The API Key, which is needed to make requests to MapQuest services.Yes
from
Coordinates
The center point the isoline is calculated outward from. Accepted forms:
  • lat,lng string - 39.7392,-104.9903
  • {lat, lng} object - {"lat": 39.7392, "lng": -104.9903}
  • {lat, lon} object - {"lat": 39.7392, "lon": -104.9903}
Use the Geocoding API to convert an address to coordinates first.
Yes
(or to)
to
Coordinates
The center point the isoline is calculated inward to. Same accepted forms as from.Yes
(or from)
within
Number collection
One or more travel-time limits in minutes, each producing an isoline polygon. For example, within=5,10,15 returns the 5, 10, and 15 minute isolines. Fractional values such as 2.5 are accepted.

Maximum: 5 values per request. Each value must be greater than 0. Maximum value: 540 (9 hours).
Yes
departAt
String
The departure time from from. Giving a time uses traffic for that time; see Time and Traffic. Accepted forms:
  • now - The time of the request.
  • Local date-time - 2026-11-03T08:30:00, interpreted in the local time zone of the from location.
  • Date-time with offset - 2026-11-03T15:30:00Z or 2026-11-03T08:30:00-07:00, converted to local time at the from location.
In a GET query string, encode a + offset as %2B.

Default: none (time-independent, no traffic).
No
(requires from)
arriveBy
String
The time to arrive at to. Same forms, traffic behavior, and default as departAt, applied to the to location.No
(requires to)
routeType
String
Specifies the type of travel used to calculate the isoline. Acceptable values are:
  • fastest - Driving, optimized for quickest travel time.
  • shortest - Driving, optimized for shortest distance.
  • pedestrian - Walking. Avoids limited access roads; ignores turn restrictions.
  • bicycle - Will only use roads on which bicycling is appropriate.
Default: fastest
No
quality
String
Trades isoline precision against response time.
  • fast - Lowest precision, fastest response.
  • balanced - Reasonable precision and response time.
  • high - Highest precision, slowest response.
Default: balanced
No
generalize
Integer
Smooths the isoline by removing detail finer than this distance, in meters. 0 returns the full-resolution shape. Higher values result in fewer points and a coarser shape.

Default: 0
Maximum: 4294967295
No

Response Object ​

FieldDescription
fromThe point the isoline was calculated from, as a latLng object, after snapping to the nearest road. Only present when from was supplied.
departAtThe departure time used for the calculation, in ISO 8601 format with the local offset of the from location. Only present when departAt was supplied.
toThe point the isoline was calculated to, as a latLng object, after snapping to the nearest road. Only present when to was supplied.
arriveByThe arrival time used for the calculation, in ISO 8601 format with the local offset of the to location. Only present when arriveBy was supplied.
isolinesA GeoJSON FeatureCollection. Contains one Feature per value in within, in the order requested.
isolines.features[].properties.withinThe within value this polygon represents.
isolines.features[].properties.unitAlways min. Present so time and distance features share the same shape.
isolines.features[].geometryA GeoJSON Polygon, or a MultiPolygon when the reachable area is disconnected (for example, separated by water with no ferry). Coordinates are [lng, lat] per the GeoJSON specification. Inner rings represent unreachable holes.
warningsAn array of non-fatal notices, each with a code and message. Present only when applicable. See Warning Codes.

Warning Codes ​

CodeDescription
locationSnappedThe from/to point was more than 100 meters from the nearest road and was snapped to it.

Error Responses ​

Errors are returned as application/problem+json.

StatusDescription
400A parameter is missing or invalid. errors lists each problem with a pointer to the parameter, such as #/within/1.
422The from/to point could not be matched to a road.
502The isoline could not be calculated.
503The isoline service is temporarily unavailable. Please retry.

Example Request ​

GET ​

15 minute drive-time isoline from downtown Denver, independent of traffic:

bash
curl -X GET 'https://www.mapquestapi.com/isoline/v1/time' \
  --url-query 'key=YOUR_API_KEY' \
  --url-query 'from=39.7392,-104.9903' \
  --url-query 'within=15'

The same isoline in current traffic:

bash
curl -X GET 'https://www.mapquestapi.com/isoline/v1/time' \
  --url-query 'key=YOUR_API_KEY' \
  --url-query 'from=39.7392,-104.9903' \
  --url-query 'within=15' \
  --url-query 'departAt=now'

5, 10, and 15 minute walking isolines, departing at 8:30 AM:

bash
curl -X GET 'https://www.mapquestapi.com/isoline/v1/time' \
  --url-query 'key=YOUR_API_KEY' \
  --url-query 'from=39.7392,-104.9903' \
  --url-query 'routeType=pedestrian' \
  --url-query 'within=5,10,15' \
  --url-query 'departAt=2026-11-03T08:30:00'

Everywhere a hospital can be reached from within 20 minutes, arriving by 7:00 AM (inbound isoline):

bash
curl -X GET 'https://www.mapquestapi.com/isoline/v1/time' \
  --url-query 'key=YOUR_API_KEY' \
  --url-query 'to=39.7444,-104.9407' \
  --url-query 'within=20' \
  --url-query 'arriveBy=2026-11-03T07:00:00'

POST ​

The same 5, 10, and 15 minute walking isolines as above, as a JSON body with from as an object:

bash
curl -X POST 'https://www.mapquestapi.com/isoline/v1/time' \
  --url-query 'key=YOUR_API_KEY' \
  --json '{
    "from": { "lat": 39.7392, "lng": -104.9903 },
    "routeType": "pedestrian",
    "within": [5, 10, 15],
    "departAt": "2026-11-03T08:30:00"
  }'

Example Response ​

The traffic-independent 15 minute isoline from the first example, so departAt is absent.

json
{
  "from": {
    "latLng": {
      "lat": 39.739236,
      "lng": -104.990251
    }
  },
  "isolines": {
    "type": "FeatureCollection",
    "features": [
      {
        "type": "Feature",
        "properties": {
          "within": 15,
          "unit": "min"
        },
        "geometry": {
          "type": "Polygon",
          "coordinates": [
            [
              [-105.0812, 39.7391],
              [-105.0734, 39.7788],
              [-105.0204, 39.8102],
              [-104.9511, 39.8075],
              [-104.9013, 39.7702],
              [-104.9020, 39.7098],
              [-104.9488, 39.6701],
              [-105.0211, 39.6683],
              [-105.0812, 39.7391]
            ]
          ]
        }
      }
    ]
  }
}