Isoline API

Isoline API calculates the areas that you can reach from a location. In other words, the API tells you how far you can go from a place to help you find new locations and businesses opportunities.

With the Isoline API, you can calculate:

  • Isochrones - isolines representing area reachable within given travel time;
  • Isodistances - isolines representing area reachable within given travel distance;

Check out the API Playground to create isochrones and isodistances:

Isochrone API and Isodistance API Live Demo

Authentication and API key

To use the Isoline API, you'll need an API key. You can register and get a Isoline API Key for free without a credit card.

We offer a free plan, so there's no need to stress about cost. Start for free and upgrade to a paid plan when the needs of your project increase. For more information on our plans, visit the Pricing page.

How to get Geoapify API key

  1. Register on Geoapify MyProjects page
  2. Create a new project.
  3. Go to the API Keys section. One API key is generated automatically. You can generate multiple API keys per project if required.
  4. Optionally, you can protect the API key by listing allowed IP addresses, HTTP referrers, origins, and CORS.
  5. Choose "Isoline API" and an API key to generate a URL and programming code.
  6. Press the "Try" button to execute the API call and get the result object example.

API reference

The Isoline API, available via HTTP Get request, is used to get single or multi-value isolines.

Request URL

Request parameters

Name Description
apiKey Required parameter for API key
lat Latitude of the location
lon Longitude of the location
type Type of isoline: isochrone or isodistance. Possible values: "time", "distance".
mode Transportation or travel mode. Check the "Supported travel modes" section for more information.
range Isoline range value or array of range values. For an isochrone time in seconds, for an isodistance distance in meters
id id of previously generated isoline

Supported travel modes

These travel modes are supported by the API:

Mode Max vehicle weight Max vehicle height Description
A passenger car routing mode drive 3.5t 1.6m A passenger car
A small delivery truck routing mode light_truck 3.5t 3.2m A light truck, for example, small delivery truck or camping car
A medium-size truck routing mode medium_truck 7.5t 4.1m A medium-size truck
A truck routing mode truck 22t 4.1m A truck
A heavy truck routing mode heavy_truck 40t 4.1m A heavy truck
A truck with dangerous goods routing mode truck_dangerous_goods 22t 4.1m A truck carrying dangerous goods
A long-truck routing mode long_truck 22t 4.1m A long truck with a maximal length of 34m
A bus routing mode bus A bus. This mode checks bus access during the route calculation.
A scooter routing mode scooter A motor scooter or moped.
A motorcycle routing mode motorcycle A motorcycle.
A bicycle routing mode bicycle A city bicycle
A mountain bicycle routing mode mountain_bike A mountain bicycle to ride on unpaved surfaces but slower on paved terrain.
A road bicycle routing mode road_bike A road-style bicycle with narrow tires and lightweight construction.
A walking routing mode walk A pedestrian mode
A hiking routing mode hike A hiking mode additionally to pedestrian mode uses hiking trails and higher difficulty trails
A transit routing mode transit A transit or public transport mode.
An approximated transit routing mode approximated_transit A transit or public transport mode uses approximated (built on available in OSM transit routes) data for route calculation.

Response HTTP status codes

Name Description
200 OK - response contains valid GeoJSON for the requested isoline(s)
202 Accepted - request is in processing. Is returned when big range value (more than 1 hour / 10 km) or multiple range values are set. Response properties contain a "id", GeoJSON can be queried later, once calculation is complete
400 Invalid Request - missing or malformed parameters or combination of parameters
401 Not Authorized - apiKey is missing, invalid, unknown or usage_quota has been reached
503 Service Unavailable - in case of server error or calculation failure

NOTE Isoline calculations are computationally expensive and can take multiple seconds. If calculation takes more than 30 seconds, Isoline API may return HTTP 202 with an empty FeatureColleciton, containing only the request ID. You can then use it to query isolines by ID later - up to one hour from the initial request.

Response Object

  • If the calculation was successful and HTTP status returned is 200, the response object contains GeoJSON FeatureCollection object.
  • If HTTP status returned is 202, only properties object with "id" will be returned.
  • If HTTP status returned is 400 or 401, only error object will be returned.
Name Description
type "FeatureCollection"
features Contains Feature objects of type "Multipolygon". One feature per one range value
properties Contains id, which could be used to query the isoline later
error Error object, contaning error description and details

Request URL examples

Build a single isoline

A typical request for isochrone data looks like this:

Isoline API supports the following parameters:

  • lat, lon - latitude and longitude of the location;
  • type - possible values: "time" (isochrone), "distance" (isodistance);
  • mode - transportation or travel mode. Supported values: "drive", "transit", "approximated_transit", "walk", "bicycle";
  • range - defines travel time in seconds for isochrones, and travel distance in meters for isodistances.

and returns GeoJSON, with a unique request ID in the FeatureCollection "properties" object, and each isoline contour is represented by an individual GeoJSON Feature.

Build a multi-range isoline

It is possible to calculate multiple isoline contours at once, with up to 10 different range values. To achieve this, you just need to specify the "range" parameter multiple times.

Example API call that returns 15 and 30-minute isochrones for a given location:

Get an existing isoline

It's possible to retrieve results of earlier Isoline API requests for up to one hour from the time of the initial request. This could be done with an HTTP request with id parameter:

The value for the id parameter could be an id of FeatureCollection or Feature returned with a regular Isoline API.

Code samples

Geoapify returns data in GeoJSON format, which could be easily drawn by most of map client libraries. The examples below show how to add a GeoJSON object to a map.

Visualize isoline with "Leaflet" library

L.geoJSON(data, {
    style: function (feature) {
        // add layer style here
        return {color: '#222222'};

Visualize isoline with MapLibre GL / Mapbox GL library'isoline-data-source', {
  type: "geojson",
  data: isolineGeoJSON,
  id: 'isoline-line',
  type: "line",
  source: 'isoline-data-source',
  paint: {
    "line-color": '#6666ff',
    "line-width": 2,
  id: this.isolineLayerName,
  type: "fill",
  source: 'isoline-fill',
  paint: {
    "fill-color": '#6666ff',
    "fill-opacity": 0.3,

Visualize isoline with "OpenLayers" library

var vectorSource = new ol.source.Vector({
    features: (new ol.format.GeoJSON({
        featureProjection: "EPSG:3857"

var style = new{
    stroke: new{
        color: 'rgba(0, 0, 255, 1.0)',
        width: 3
    fill: new{
        color: 'rgba(0, 0, 255, 0.1)'

var vectorLayer = new ol.layer.Vector({
    source: vectorSource,
    style: style



To calculate the cost of each Geoapify request, we use credits. This helps us simplify our Pricing and standardize API calls.

The following rules determine how much a Isoline API request costs:

API name Definition of 1 request Example
Isochrone (Isoline API with type="time") Every 5 requested minutes cost 1 credit 30-minutes isochrone costs 6 credits
Isodistance (Isoline API with type="distance") Every 5 requested km cost 1 credit 25-km isodistance costs 5 credits

Our FREE pricing plan includes 3000 credits per day. Start with the FREE plan and upgrade later, if needed! In addition, we allow you to cache/store calculated isolines on your side with no restrictions.