Airports LookupAirports Lookup API

OnlineCredit Usage:1 per callRefreshed 5 days ago
avg: 892ms|p50: 833ms|p75: 931ms|p90: 1049ms|p99: 1284ms

Overview

To use Airports Lookup, 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/airports

Example

How to call the Airports Lookup API in different programming languages.

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/airports?iata=MCI" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/airports?iata=MCI', {
  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/airports?iata=MCI', 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/airports?iata=MCI", 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": {
    "icao": "KMCI",
    "iata": "MCI",
    "name": "Kansas City International Airport",
    "city": "Kansas City",
    "state": "Missouri",
    "country": "US",
    "elevation": 1026,
    "lat": 39.2975997925,
    "lon": -94.7138977051,
    "tz": "America/Chicago",
    "city_info": {
      "name": "Kansas City",
      "altName": "",
      "country": "US"
    }
  }
}

Authentication

The Airports Lookup 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 Airports Lookup API directly in your browser with live requests and responses.

Parameters

The Airports Lookup API supports multiple query options. Use one of the following:

Some Airports Lookup parameters marked with Premium are available exclusively on paid plans.View pricing

Option 1: Get Airport Info from IATA

ParameterTypeRequiredDescriptionDefaultExample
iatastringrequired
The IATA code of the airport for which you want to get the information (e.g., MCI)
-MCI

Option 2: Get Airport Info from ICAO

ParameterTypeRequiredDescriptionDefaultExample
icaoPremiumstringrequired
The ICAO code of the airport for which you want to get the information (e.g., KMCI)
-KMCI

Response

The Airports Lookup 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>
    <icao>KMCI</icao>
    <iata>MCI</iata>
    <name>Kansas City International Airport</name>
    <city>Kansas City</city>
    <state>Missouri</state>
    <country>US</country>
    <elevation>1026</elevation>
    <lat>39.2975997925</lat>
    <lon>-94.7138977051</lon>
    <tz>America/Chicago</tz>
    <city_info>
      <name>Kansas City</name>
      <altName></altName>
      <country>US</country>
    </city_info>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  icao: KMCI
  iata: MCI
  name: Kansas City International Airport
  city: Kansas City
  state: Missouri
  country: US
  elevation: 1026
  lat: 39.2975997925
  lon: -94.7138977051
  tz: America/Chicago
  city_info:
    name: Kansas City
    altName: ''
    country: US
CSV Response
200 OK
keyvalue
icaoKMCI
iataMCI
nameKansas City International Airport
cityKansas City
stateMissouri
countryUS
elevation1026
lat39.2975997925
lon-94.7138977051
tzAmerica/Chicago
city_info{name:Kansas City,altName:,country:US}

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
icaostring"KMCI"
International Civil Aviation Organization airport code
iatastring"MCI"
International Air Transport Association airport code
namestring"Kansas City International Airport"
Official name of the airport
citystring"Kansas City"
City where the airport is located
statestring"Missouri"
State or province where airport is located
countrystring"US"
Country code where airport is located
elevationPremiumnumber1026
Airport elevation in feet above sea level
latPremiumnumber39.2975997925
Airport latitude coordinate for mapping
lonPremiumnumber-94.7138977051
Airport longitude coordinate for mapping
tzPremiumstring"America/Chicago"
IANA timezone name for the airport location
city_infoPremiumobject{...}
Additional city information including alternate names
â”” namestring"Kansas City"
Primary city name for the airport location
â”” altNamestring""
Alternate name for the city if available
â”” countrystring"US"
Country code for the city location

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 Airports Lookup through GraphQL to combine it with other API calls in a single request. Query only the airports lookup data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Airports Lookup 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 {
  airports(
    input: {
      iata: "MCI"
    }
  ) {
    icao
    iata
    name
    city
    state
    country
    elevation
    lat
    lon
    tz
    city_info {
      name
      altName
      country
    }
  }
}

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

CORS Support

The Airports Lookup 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

Airports Lookup 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 Airports Lookup 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 Airports Lookup

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

No-Code Integrations

Airports Lookup 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 Airports Lookup?
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 Airports Lookup and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Airports Lookup cost?

Each successful Airports Lookup 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 airports lookup lookups.

Can I use Airports Lookup in production?

The free plan is for testing and development only. For production use of Airports Lookup, 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 Airports Lookup from a browser?
Yes! The Airports Lookup 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 Airports Lookup credit limit?

When you reach your monthly credit limit, Airports Lookup 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?