Airport Code Converter API
Overview
To use Airport Code Converter, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/airportcodeconverterExample
How to call the Airport Code Converter API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/airportcodeconverter?code=MCI" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/airportcodeconverter?code=MCI', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/airportcodeconverter?code=MCI', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/airportcodeconverter?code=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))
}{
"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
}
}Authentication
The Airport Code Converter API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Airport Code Converter API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Airport Code Converter API:
Convert Airport Code
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
code | string | required | The airport code to convert (IATA: 3 letters, ICAO: 4 letters) | - |
Response
The Airport Code Converter 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 version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<input>MCI</input>
<inputType>IATA</inputType>
<iata>MCI</iata>
<icao>KMCI</icao>
<name>Kansas City International Airport</name>
<city>Kansas City</city>
<state>Missouri</state>
<country>US</country>
<elevation>1026</elevation>
<latitude>39.2976</latitude>
<longitude>-94.7139</longitude>
<timezone>America/Chicago</timezone>
<found>true</found>
</data>
</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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains 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:
| Field | Type | Sample Value | Description |
|---|---|---|---|
input | string | Original airport code provided in request | |
inputType | string | Detected input code format (IATA or ICAO) | |
iata | string | Three-letter IATA airport code | |
icao | string | Four-letter ICAO airport code | |
name | string | Official airport name | |
city | string | City where airport is located | |
state | string | State or province where airport is located | |
country | string | Country code (ISO 3166-1 alpha-2) | |
elevationPremium | number | Airport elevation in feet above sea level | |
latitudePremium | number | Airport latitude coordinate | |
longitudePremium | number | Airport longitude coordinate | |
timezonePremium | string | Airport timezone (e.g., America/Chicago) | |
found | boolean | Whether airport code was found in database |
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 Code Converter through GraphQL to combine it with other API calls in a single request. Query only the airport code converter data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
airportcodeconverter(
input: {
code: "MCI"
}
) {
input
inputType
iata
icao
name
city
state
country
elevation
latitude
longitude
timezone
found
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Airport Code Converter 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 Code Converter 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 Code Converter 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 Code Converter
Official Airport Code Converter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Airport Code Converter 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 Code Converter?
How many credits does Airport Code Converter cost?
Each successful Airport Code Converter 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 code converter lookups.
Can I use Airport Code Converter in production?
The free plan is for testing and development only. For production use of Airport Code Converter, 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 Code Converter from a browser?
What happens if I exceed my Airport Code Converter credit limit?
When you reach your monthly credit limit, Airport Code Converter 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.








