Airport Code Converter API GET

Airport Code Converter is a simple tool for converting between IATA (3-letter) and ICAO (4-letter) airport codes. Submit either format and get the corresponding code back.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/airportcodeconverter

Verification

Format

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

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Airport Code Converter response payload
  }
}

About the Airport Code Converter API

Airport Code Converter automatically detects whether you've submitted an IATA or ICAO code based on length, then returns the corresponding code in the other format. Uses a comprehensive database of 40,000+ airports worldwide.

What people use it for

Flight Systems: Convert between IATA and ICAO codes for flight booking systems and aviation applications
Data Integration: Normalize airport codes when integrating data from different aviation sources
Travel Apps: Display both IATA and ICAO codes to users for comprehensive airport identification

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 Airport Code Converter

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 Airport Code Converter API.

Read the docs →

What does the Airport Code Converter API do?

Airport Code Converter is a simple tool for converting between IATA (3-letter) and ICAO (4-letter) airport codes. Submit either format and get the corresponding code back.

How do I authenticate Airport Code Converter API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Airport Code Converter API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Airport Code Converter API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Airport Code Converter API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Airport Code Converter API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/airportcodeconverter

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
`code`Required	string	`MCI`	The airport code to convert (IATA: 3 letters, ICAO: 4 letters)

Example request

1
2

curl "https://api.apiverve.com/v1/airportcodeconverter?code=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/airportcodeconverter

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": {
    "input": "MCI",
    "inputType": "IATA",
    "iata": "MCI",
    "icao": "KMCI",
    "name": "Kansas City International Airport",
    "city": "Kansas City",
    "state": "Missouri",
    "country": "US",
    "elevation": 1026,
    "latitude": 39.2976,
    "longitude": -94.7139,
    "timezone": "America/Chicago",
    "found": true
  }
}

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
`input`	string	`"MCI"`	Original airport code provided in request
`inputType`	string	`"IATA"`	Detected input code format (IATA or ICAO)
`iata`	string	`"MCI"`	Three-letter IATA airport code
`icao`	string	`"KMCI"`	Four-letter ICAO airport code
`name`	string	`"Kansas City International Airport"`	Official airport name
`city`	string	`"Kansas City"`	City where airport is located
`state`	string	`"Missouri"`	State or province where airport is located
`country`	string	`"US"`	Country code (ISO 3166-1 alpha-2)
`elevation`Premium	number	`1026`	Airport elevation in feet above sea level
`latitude`Premium	number	`39.2976`	Airport latitude coordinate
`longitude`Premium	number	`-94.7139`	Airport longitude coordinate
`timezone`Premium	string	`"America/Chicago"`	Airport timezone (e.g., America/Chicago)
`found`	boolean	`true`	Whether airport code was found in database

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	Airport Code Converter 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/airportcodeconverter

No SDK to install — this is a plain HTTPS call to /v1/airportcodeconverter 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/airportcodeconverter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

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

Also published for

@apiverve/airportcodeconverternpm apiverve-airportcodeconverterPyPI APIVerve.API.AirportCodeConverterNuGet

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/airportcodeconverter

Install the Node.js SDK, then call the Airport Code Converter 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/airportcodeconverter

Node.js

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

Resources

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

Also published for

apiverve-airportcodeconverterPyPI APIVerve.API.AirportCodeConverterNuGet

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

Call it from Python — GET /v1/airportcodeconverter

Install the Python SDK, then call the Airport Code Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-airportcodeconverter

Python

import requests

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

Resources

PyPIapiverve-airportcodeconverterThe published Python client, versioned and signed.GitHubapiverve/airportcodeconverter-apiSource, issues and the examples this page is built from.ReferenceAirport Code Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/airportcodeconverternpm APIVerve.API.AirportCodeConverterNuGet

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/airportcodeconverter

Install the C# / .NET SDK, then call the Airport Code Converter 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.AirportCodeConverter

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/airportcodeconverter");
Console.WriteLine(json);

Resources

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

Also published for

@apiverve/airportcodeconverternpm apiverve-airportcodeconverterPyPI

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

Call it from Go — GET /v1/airportcodeconverter

No SDK to install — this is a plain HTTPS call to /v1/airportcodeconverter 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/airportcodeconverter", 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/airportcodeconverternpm apiverve-airportcodeconverterPyPI APIVerve.API.AirportCodeConverterNuGet

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

Call it from PHP — GET /v1/airportcodeconverter

No SDK to install — this is a plain HTTPS call to /v1/airportcodeconverter 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/airportcodeconverter");
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/airportcodeconverternpm apiverve-airportcodeconverterPyPI APIVerve.API.AirportCodeConverterNuGet

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

Call it from Ruby — GET /v1/airportcodeconverter

No SDK to install — this is a plain HTTPS call to /v1/airportcodeconverter 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/airportcodeconverter")
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/airportcodeconverternpm apiverve-airportcodeconverterPyPI APIVerve.API.AirportCodeConverterNuGet

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

Airport Code Converter API GET

Try it — live request, no key required

About the Airport Code Converter API

What people use it for

Ways to call it

Other ways to use Airport Code Converter

Questions.

Request parameters — GET /v1/airportcodeconverter

Required

Authentication

Response — GET /v1/airportcodeconverter

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/airportcodeconverter

Resources

Also published for

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

Resources

Also published for

Call it from Python — GET /v1/airportcodeconverter

Resources

Also published for

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

Resources

Also published for

Call it from Go — GET /v1/airportcodeconverter

Resources

Also published for

Call it from PHP — GET /v1/airportcodeconverter

Resources

Also published for

Call it from Ruby — GET /v1/airportcodeconverter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Airport Code Converter API

Transportation

Related articles

Ready to build with Airport Code Converter? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog