Connect aviation identifiers with the airports in your travel product. Look up four-letter ICAO airport codes to retrieve airport names, IATA codes and location details, or download the directory to match records across your systems.
Pass EGLL in the icao parameter to retrieve London Heathrow Airport, its IATA code and location identifiers. Replace YOUR_API_KEY with your assigned key.
curl --get 'https://content.airhex.com/api/v3.7.10/airports/' \
--data-urlencode 'apikey=YOUR_API_KEY' \
--data-urlencode 'icao=EGLL'[
{
"airhex_id": "53779",
"iata": "LHR",
"icao": "EGLL",
"name": "London Heathrow Airport",
"city_code": "LON",
"country_code": "GB",
...
}
]Abbreviated response. The ellipsis (…) represents additional airport fields omitted here and is not part of the actual JSON response.
View the full Airports API reference →Look up a specific airport, find airports by location, or export the directory with these query parameters.
| Parameter | Required | Default | Description |
|---|---|---|---|
apikey |
Yes | None | Your assigned API key. Get a free test API key. |
iata |
Conditional | None | Three-letter IATA airport code, such as LHR. |
icao |
Conditional | None | Four-letter ICAO airport code, such as EGLL. |
city_code |
Conditional | None | Three-letter IATA city code, such as LON, to find airports associated with a city. |
country_code |
Conditional | None | Two-letter ISO country code, such as GB, to find airports in a country. |
name |
Conditional | None | Airport name or partial name, such as Heathrow. |
dump |
Conditional | 0 | Set to 1 to export the database. Overrides the other lookup parameters; coverage filters still apply. |
show_disabled |
No | 0 | Set to 1 to include inactive or disabled records. By default, only active records are returned. |
response_type |
No | JSON | Response format: JSON, XML or CSV. CSV triggers a file download. |
major_only |
No | 0 | Set to 1 to include only airports with commercial flights. |
Provide at least one of iata, icao, city_code, country_code, name, or dump=1. Setting dump=1 overrides the other lookup parameters.
View all request parameters →Use ICAO and IATA codes from the same record to connect your data sources. Keep the airport name and location available for display, and retain airhex_id for record identity.
| Field | Type | Example | Description |
|---|---|---|---|
airhex_id |
Identifier | 53779 | Permanent Airhex record identifier. Retain it to associate updates with the same record. |
iata |
String | LHR | Three-letter IATA airport code for matching departure and arrival locations. |
icao |
String | EGLL | Four-letter ICAO airport identifier for matching data from aviation sources. |
name |
String | London Heathrow Airport | Airport name for search results, itineraries and passenger information. |
city_code |
String | LON | IATA city code associated with the airport. A city can have multiple airports. |
country_code |
String | GB | Two-letter ISO country code for the airport location. |
major_airport |
Integer | 1 | 1 indicates an airport with scheduled commercial flights; 0 covers other records. |
active |
Status | 1 | Operational status: 1 = active, 0 = inactive. |
Export the active airport directory as CSV and build a local index from records with a populated icao field. Keep iata where available to support matching with booking data. Add major_only=1 if your product needs only airports with commercial flights.
curl --get 'https://content.airhex.com/api/v3.7.10/airports/' \
--data-urlencode 'apikey=YOUR_API_KEY' \
--data-urlencode 'dump=1' \
--data-urlencode 'response_type=CSV' \
--output airports.csvPass LHR in iata and read icao from the response. This lets your application match a booking supplier’s airport identifier to a source that uses ICAO codes, using both codes from the same airport record.
curl --get 'https://content.airhex.com/api/v3.7.10/airports/' \
--data-urlencode 'apikey=YOUR_API_KEY' \
--data-urlencode 'iata=LHR'Search with name and inspect the returned icao field. Partial names may return several matches, so compare the airport name, country and other identifiers before selecting a record.
curl --get 'https://content.airhex.com/api/v3.7.10/airports/' \
--data-urlencode 'apikey=YOUR_API_KEY' \
--data-urlencode 'name=Heathrow'Match airports from sources that use different code systems so your travel product can combine records for the same departure or arrival location.
Turn ICAO identifiers from aviation feeds into airport names and IATA codes for customer support tools, dashboards and passenger information.
Keep a shared airport directory across your data imports and reports, with ICAO codes, IATA codes and location details tied to the same record.
ICAO airport identifiers have four letters, such as EGLL for London Heathrow. IATA airport codes have three letters, such as LHR. Use icao or iata according to the code system supplied by your source; the response provides both fields where available.
Yes. Look up the airport with icao and read the returned iata field. You can also look up an IATA code with iata and read icao. Check that the destination field is populated before creating a mapping; do not assume every record has both identifiers.
No. A city code such as LON is a separate destination identifier. Use city_code to find airports associated with a city, then use the icao value from the relevant airport record. A city can be served by multiple airports.
The default request returns active records and does not restrict results to airports with commercial flights. Set major_only=1 for that restriction. The broader dataset can include other location types; check icao before adding records to an ICAO lookup, and use major_airport and sub_type from the full response to distinguish facilities.
Set show_disabled=1 to include inactive or disabled records, and inspect active in the response. Keep that status available when resolving historical data so an old airport reference is not automatically offered as an active booking destination.
Yes, with an appropriate GEO Essentials license. Use dump=1 to export JSON, XML or CSV, and choose major_only and show_disabled for the coverage you need. Index populated icao values for local lookups while retaining airhex_id as the permanent record identifier.
Retain airhex_id and updated from the full response and refresh your local directory periodically. Check for populated code fields before creating mappings. If a lookup cannot resolve a source code, preserve the original value for review rather than guessing a match from a similar airport name.
No. This endpoint provides airport reference data for identifying and matching locations. Obtain live flight status, runway availability and operational notices from the appropriate operational data provider. The active field describes the airport record’s operational status, not current flight conditions.
Match aviation identifiers to recognizable airports across booking, support and reporting, without maintaining your own ICAO-to-IATA directory.
Explore the complete airport dataset, including IATA and ICAO codes, names, city and country identifiers, time zones, coordinates, operational status and contact details. View all request parameters, coverage filters and response fields, with individual lookups and bulk exports in JSON, XML and CSV.
Look up airport latitude and longitude by IATA or ICAO code, or export coordinates for airport maps and location search in your travel product.
Look up airport IATA codes, match codes to airport names, cities and ICAO identifiers, or export an airport code directory with the Airhex API.
Look up airport time zones by IATA or ICAO code. Retrieve time zone identifiers and UTC offsets to support local-time displays in your travel product.