Airport DistanceAirport Distance API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 1312ms|p50: 1194ms|p75: 1391ms|p90: 1627ms|p99: 2099ms

Overview

To use Airport Distance, you need an API key. You can get one by creating a free account and visiting your dashboard.

GET Endpoint

URL
https://api.apiverve.com/v1/airportdistance

Example

How to call the Airport Distance API in different programming languages.

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/airportdistance?iata1=JFK&iata2=LAX" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/airportdistance?iata1=JFK&iata2=LAX', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/airportdistance?iata1=JFK&iata2=LAX', headers=headers)

data = response.json()
print(data)
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"

)

func main() {
    req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/airportdistance?iata1=JFK&iata2=LAX", nil)

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Example Response
{
  "status": "ok",
  "error": null,
  "data": {
    "distanceMiles": 2470.23,
    "distanceKm": 3974.2,
    "distanceNauticalMiles": 2145.12,
    "estimatedFlightTime": "5h 24m",
    "timezoneDiffHours": -3,
    "bearing": 265,
    "direction": "West",
    "isInternational": false,
    "carbonEstimateKg": 543,
    "airport1": {
      "name": "John F Kennedy International Airport",
      "iata": "JFK",
      "icao": "KJFK",
      "city": "New York",
      "state": "New-York",
      "country": "US",
      "elevation": 13,
      "latitude": 40.63980103,
      "longitude": -73.77890015,
      "timezone": "America/New_York"
    },
    "airport2": {
      "name": "Los Angeles International Airport",
      "iata": "LAX",
      "icao": "KLAX",
      "city": "Los Angeles",
      "state": "California",
      "country": "US",
      "elevation": 125,
      "latitude": 33.94250107,
      "longitude": -118.4079971,
      "timezone": "America/Los_Angeles"
    }
  }
}

Authentication

The Airport Distance API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Airport Distance API directly in your browser with live requests and responses.

Parameters

The Airport Distance API supports multiple query options. Use one of the following:

Some Airport Distance parameters marked with Premium are available exclusively on paid plans.View pricing

Option 1: Get Airport Distance from IATA

ParameterTypeRequiredDescriptionDefaultExample
iata1stringrequired
The IATA code of the first airport (e.g. JFK)
-JFK
iata2stringrequired
The IATA code of the second airport (e.g. LAX)
-LAX

Option 2: Get Airport Distance from ICAO

ParameterTypeRequiredDescriptionDefaultExample
icao1Premiumstringrequired
The ICAO code of the first airport (e.g. KJFK)
-KJFK
icao2Premiumstringrequired
The ICAO code of the second airport (e.g. KLAX)
-KLAX

Response

The Airport Distance API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <distanceMiles>2470.23</distanceMiles>
    <distanceKm>3974.2</distanceKm>
    <distanceNauticalMiles>2145.12</distanceNauticalMiles>
    <estimatedFlightTime>5h 24m</estimatedFlightTime>
    <timezoneDiffHours>-3</timezoneDiffHours>
    <bearing>265</bearing>
    <direction>West</direction>
    <isInternational>false</isInternational>
    <carbonEstimateKg>543</carbonEstimateKg>
    <airport1>
      <name>John F Kennedy International Airport</name>
      <iata>JFK</iata>
      <icao>KJFK</icao>
      <city>New York</city>
      <state>New-York</state>
      <country>US</country>
      <elevation>13</elevation>
      <latitude>40.63980103</latitude>
      <longitude>-73.77890015</longitude>
      <timezone>America/New_York</timezone>
    </airport1>
    <airport2>
      <name>Los Angeles International Airport</name>
      <iata>LAX</iata>
      <icao>KLAX</icao>
      <city>Los Angeles</city>
      <state>California</state>
      <country>US</country>
      <elevation>125</elevation>
      <latitude>33.94250107</latitude>
      <longitude>-118.4079971</longitude>
      <timezone>America/Los_Angeles</timezone>
    </airport2>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  distanceMiles: 2470.23
  distanceKm: 3974.2
  distanceNauticalMiles: 2145.12
  estimatedFlightTime: 5h 24m
  timezoneDiffHours: -3
  bearing: 265
  direction: West
  isInternational: false
  carbonEstimateKg: 543
  airport1:
    name: John F Kennedy International Airport
    iata: JFK
    icao: KJFK
    city: New York
    state: New-York
    country: US
    elevation: 13
    latitude: 40.63980103
    longitude: -73.77890015
    timezone: America/New_York
  airport2:
    name: Los Angeles International Airport
    iata: LAX
    icao: KLAX
    city: Los Angeles
    state: California
    country: US
    elevation: 125
    latitude: 33.94250107
    longitude: -118.4079971
    timezone: America/Los_Angeles
CSV Response
200 OK
keyvalue
distanceMiles2470.23
distanceKm3974.2
distanceNauticalMiles2145.12
estimatedFlightTime5h 24m
timezoneDiffHours-3
bearing265
directionWest
isInternationalfalse
carbonEstimateKg543
airport1{name:John F Kennedy International Airport,iata:JFK,icao:KJFK,city:New York,state:New-York,country:US,elevation:13,latitude:40.63980103,longitude:-73.77890015,timezone:America/New_York}
airport2{name:Los Angeles International Airport,iata:LAX,icao:KLAX,city:Los Angeles,state:California,country:US,elevation:125,latitude:33.94250107,longitude:-118.4079971,timezone:America/Los_Angeles}

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
distanceMilesnumber2470.23
Distance in statute miles
distanceKmnumber3974.2
-
distanceNauticalMilesPremiumnumber2145.12
Distance in nautical miles (aviation standard)
estimatedFlightTimestring"5h 24m"
Estimated flight duration (e.g., 5h 24m)
timezoneDiffHoursPremiumnumber-3
Timezone difference in hours between airports
bearingPremiumnumber265
Compass bearing from airport1 to airport2 (0-360 degrees)
directionPremiumstring"West"
Compass direction (e.g., North, Southwest, East)
isInternationalPremiumbooleanfalse
Whether the flight crosses international borders
carbonEstimateKgPremiumnumber543
Estimated CO2 emissions in kg per passenger (based on ICAO methodology)
airport1Premiumobject{...}
Details about the first airport
â”” namestring"John F Kennedy International Airport"
-
â”” iatastring"JFK"
-
â”” icaostring"KJFK"
-
â”” citystring"New York"
-
â”” statestring"New-York"
-
â”” countrystring"US"
-
â”” elevationnumber13
Airport elevation in feet
â”” latitudenumber40.63980103
Airport latitude
â”” longitudenumber-73.77890015
Airport longitude
â”” timezonestring"America/New_York"
Airport timezone (e.g., America/New_York)

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Airport Distance through GraphQL to combine it with other API calls in a single request. Query only the airport distance data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Airport Distance in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  airportdistance(
    input: {
      iata1: "JFK"
      iata2: "LAX"
    }
  ) {
    distanceMiles
    distanceKm
    distanceNauticalMiles
    estimatedFlightTime
    timezoneDiffHours
    bearing
    direction
    isInternational
    carbonEstimateKg
    airport1 {
      name
      iata
      icao
      city
      state
      country
      elevation
      latitude
      longitude
      timezone
    }
    airport2 {
      name
      iata
      icao
      city
      state
      country
      elevation
      latitude
      longitude
      timezone
    }
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Airport Distance API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Airport Distance requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Airport Distance API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Airport Distance

Official Airport Distance packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Airport Distance works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Frequently Asked Questions

How do I get an API key for Airport Distance?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Airport Distance and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Airport Distance cost?

Each successful Airport Distance API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful airport distance lookups.

Can I use Airport Distance in production?

The free plan is for testing and development only. For production use of Airport Distance, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Airport Distance from a browser?
Yes! The Airport Distance API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Airport Distance credit limit?

When you reach your monthly credit limit, Airport Distance API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?