Airports Lookup API

GET

Resolve airport codes to official airport names and locations.

Airports Lookup resolves 3-letter IATA codes into official airport names, matching ICAO codes, cities, states, country codes and country names. Paid plans add ICAO code lookups, search by airport name or city, geographic coordinates, elevation, local timezones and the current UTC offset across more than 29,000 facilities.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/airports?iata=MCI

Query parameters

iatastring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "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",
    "country_name": "United States",
    "utc_offset": "-06:00",
    "city_info": {
      "name": "Kansas City",
      "altName": "",
      "country": "US"
    }
  }
}

About the Airports Lookup API

An airport database API with IATA and ICAO codes for 29,000+ airports worldwide. Query the database by passing a 3-letter IATA code to retrieve the airport's official name, state, city, country code and English country name. The dataset covers over 29,000 airports and receives weekly updates. Upgraded subscriptions can also query directly by 4-letter ICAO code, search airports by partial name or city (optionally within one country, up to 10 matches per call with the total match count), and receive geographic coordinates, runway elevation, timezone identifiers, the airport's current UTC offset with daylight saving applied, and alternate city names.

What people use it for

Flight Booking Confirmation: When passengers enter an airport code, travel sites translate the code into the full facility name and destination city on itineraries.
Air Freight Routing: Logistics platforms convert flight manifests containing IATA codes into verified destination countries and cities to plan regional ground transfers.
Flight Plan Mapping: To plot flight paths, aviation software queries ICAO codes on paid plans to map runway coordinates and airport elevation.
Expense Report Auditing: Audit corporate travel receipts by matching ticket codes against declared employee itineraries to catch incorrect destination claims.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Airports Lookup

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Airports Lookup API.

Read the docs →

Can I search by both 3-letter and 4-letter airport codes, or by name?

Yes - the service includes dedicated lookups for 3-letter IATA codes on every plan and 4-letter ICAO codes on paid plans across a catalog of more than 29,000 airports worldwide. Paid plans can also search by partial airport name or city, optionally filtered to one country, and get up to 10 matches per call.

How far does the Starter plan go for airport lookups?

Each lookup costs 2 credits. Starter provides 200,000 credits each month, covering 100,000 airport lookups, which works out to about $0.30 per 1,000 calls. The Free plan includes 100 lookups per month.

Do I get GPS coordinates and timezones on the Free plan?

No. Airport latitude, longitude, elevation, timezone, current UTC offset, and extended city information are premium fields reserved for paid plans. Looking up airports by ICAO code, and searching by airport name or city, also require a paid plan. The country name is included on every plan.

How often is the airport data updated?

The dataset covers over 29,000 airports and is updated on a weekly schedule to keep airport identifiers, names, and geographic details current.

Can I use this airport data in a commercial travel app?

Yes, as long as you are on a paid plan. You can display and use the airport data directly inside your own application, though redistributing or reselling the raw dataset is not permitted.

Request parameters — GET /v1/airports

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`iata`Required	string	`MCI`	The IATA code of the airport for which you want to get the information (e.g., MCI)

Example request

1
2

curl "https://api.apiverve.com/v1/airports?iata=MCI" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/airports

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample 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",
    "country_name": "United States",
    "utc_offset": "-06:00",
    "city_info": {
      "name": "Kansas City",
      "altName": "",
      "country": "US"
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`icao`	string	`"KMCI"`	International Civil Aviation Organization airport code
`iata`	string	`"MCI"`	International Air Transport Association airport code
`name`	string	`"Kansas City International Airport"`	Official name of the airport
`city`	string	`"Kansas City"`	City where the airport is located
`state`	string	`"Missouri"`	State or province where airport is located
`country`	string	`"US"`	Country code where airport is located
`elevation`Premium	number	`1026`	Airport elevation in feet above sea level
`lat`Premium	number	`39.2975997925`	Airport latitude coordinate for mapping
`lon`Premium	number	`-94.7138977051`	Airport longitude coordinate for mapping
`tz`Premium	string	`"America/Chicago"`	IANA timezone name for the airport location
`country_name`	string	`"United States"`	English name of the country, derived from the country code (null if the code is not a recognized ISO region)
`utc_offset`Premium	string	`"-06:00"`	The airport's current offset from UTC (e.g. -05:00), with daylight saving applied at the time of the call
`city_info`Premium	object	`{...}`	Additional city information including alternate names
`name`Premium	string	`"Kansas City"`	Primary city name for the airport location
`altName`Premium	string	`""`	Alternate name for the city if available
`country`Premium	string	`"US"`	Country code for the city location

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Airports Lookup calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/airports

No SDK to install — this is a plain HTTPS call to /v1/airports with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/airports" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/airports-apiSource, issues and the examples this page is built from.ReferenceAirports Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/airportsnpm APIVerve.API.AirportsLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/airports

Install the Node.js SDK, then call the Airports Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/airports

Node.js

const res = await fetch("https://api.apiverve.com/v1/airports", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/airportsThe published Node.js client, versioned and signed.GitHubapiverve/airports-apiSource, issues and the examples this page is built from.ReferenceAirports Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.AirportsLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/airports

No SDK to install — this is a plain HTTPS call to /v1/airports with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/airports",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/airportsnpm APIVerve.API.AirportsLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/airports

Install the C# / .NET SDK, then call the Airports Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.AirportsLookup

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/airports");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.AirportsLookupThe published C# / .NET client, versioned and signed.GitHubapiverve/airports-apiSource, issues and the examples this page is built from.ReferenceAirports Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/airportsnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/airports

No SDK to install — this is a plain HTTPS call to /v1/airports with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/airports", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/airportsnpm APIVerve.API.AirportsLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/airports

No SDK to install — this is a plain HTTPS call to /v1/airports with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/airports");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/airportsnpm APIVerve.API.AirportsLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/airports

No SDK to install — this is a plain HTTPS call to /v1/airports with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/airports")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/airportsnpm APIVerve.API.AirportsLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read

Airports Lookup API

Try it — live request, no key required

About the Airports Lookup API

What people use it for

Ways to call it

Other ways to use Airports Lookup

Questions.

Request parameters — GET /v1/airports

Required

Authentication

Response — GET /v1/airports

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/airports

Resources

Also published for

Call it from Node.js — GET /v1/airports

Resources

Also published for

Call it from Python — GET /v1/airports

Resources

Also published for

Call it from C# / .NET — GET /v1/airports

Resources

Also published for

Call it from Go — GET /v1/airports

Resources

Also published for

Call it from PHP — GET /v1/airports

Resources

Also published for

Call it from Ruby — GET /v1/airports

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Airports Lookup API

Transportation

Related articles

Ready to build with Airports Lookup? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog