AviationData.Systems Airports API V1
Community OpenAPI document · agent-readyMaps GeolocationPlaces Searchbasic6 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Lets an AI agent look up airports by IATA code, name, or proximity to coordinates and list countries and their codes.
Use for: I need the airport that matches a given IATA code, Search for airports by name, Autocomplete an airport name from a few letters, Find the airports nearest to these coordinates
Not supported: Provides airport and country reference lookups only; it does not return live flight status, schedules, or bookings, so pair it with a flight-data API for those.
The AviationData.Systems Airports API looks up airport and country reference data over REST. It finds airports by IATA code, by name, or by autocomplete prefix, returns the airports nearest to a set of coordinates, and lists countries and their codes. The specification declares HTTP basic authentication, though these lookup endpoints require no credential.
Install Jentic One Beta
Connect the AviationData.Systems Airports API V1 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AviationData.Systems Airports API V1, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faviationdata.systems%2Faviationdata" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faviationdata.systems%2Faviationdata" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AviationData.Systems Airports API V1 API.
Find an airport by its IATA code
Find airports matching a name
Autocomplete airport names from a prefix
Find the airports nearest to a set of coordinates
Look up a country by its code
List the available countries
Use Cases
Patterns agents use AviationData.Systems Airports API V1 API for, with concrete tasks.
★ Resolve airport codes in travel tools
Travel and booking tools need to turn a code or name into a known airport. The Airports API finds an airport by IATA code, by name, or by autocomplete, so an integration can validate input and show the right airport as a user types.
Given an IATA code, return the matching airport and its details.
Find airports near a location
Apps that work with coordinates need the closest airports to a point. The API returns the airports nearest to a latitude and longitude, so an integration can suggest departure options near a user or a place.
Given coordinates, return the nearest airports to that point.
Populate country reference data
Forms and filters often need a country list and code lookups. The API lists countries and resolves a country by its code, so an integration can populate dropdowns and validate country input from one source.
List the available countries and resolve one by its code.
Let an agent resolve airports on demand
An AI agent handling travel questions can turn a code, name, or location into an airport itself. Through Jentic the agent discovers the right lookup by intent and runs it, returning the matching airport or the nearest options to the user.
Given a city's coordinates, return the nearest airport to the user.
Key Endpoints
6 endpoints — the aviationdata.
METHOD
PATH
DESCRIPTION
GET
/v1/airport/iata/{airport_iata}
Find an airport by IATA code
GET
/v1/airport/name/{airport_name}
Find airports by name
GET
/v1/airport/autocomplete/{airport_name}
Autocomplete airport names from a prefix
GET
/v1/airport/nearest/{result_count}/{latitude}/{longitude}
Find the nearest airports to coordinates
GET
/v1/country/code/{country_code}
Look up a country by its code
GET
/v1/country_list
List the available countries
GET
/v1/airport/iata/{airport_iata}
Find an airport by IATA code
GET
/v1/airport/name/{airport_name}
Find airports by name
GET
/v1/airport/autocomplete/{airport_name}
Autocomplete airport names from a prefix
GET
/v1/airport/nearest/{result_count}/{latitude}/{longitude}
Find the nearest airports to coordinates
GET
/v1/country/code/{country_code}
Look up a country by its code
GET
/v1/country_list
List the available countries
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring airport lookups into an agent yourself means integrating each endpoint and mapping the reference-data shapes. With Jentic you install once, import AviationData Airports from the Directory, and start querying right away.
Permission scoping
Running Jentic in your own instance, you decide which AviationData operations the agent may call, so you can allow the airport and country lookups you want and keep the surface narrow. Access is granted per operation.
Credential isolation
Where the API expects HTTP basic credentials, your own Jentic One instance holds them encrypted and injects them only at call time, so they never reach the agent's prompt, logs, or context.
Intent-based discovery
Agents find AviationData through Jentic's intent search: a request like find the nearest airport to these coordinates resolves to the right operation with inputs prepared.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Amadeus Airport & City Search
Searches airports and cities for travel autocomplete.
Use Amadeus Airport & City Search when a workflow needs combined airport and city autocomplete.
FAQs
Specific to using AviationData.Systems Airports API V1 API through Jentic.
Is there an MCP server for the AviationData Airports API?
You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call the airport lookups directly by intent, so you connect the API without maintaining separate MCP tooling.
Can I limit which AviationData operations my agent can call?
Yes. Because you run Jentic yourself, you choose which airport and country lookups your agent can call, so you can allow the searches you want and withhold the rest. Scoping is applied per operation.
Does the AviationData Airports API require authentication?
The specification declares HTTP basic authentication, but the airport and country lookup endpoints in this version require no credential. Where credentials are expected, Jentic injects them from your stored credential at call time.
How can I search for an airport?
You can find an airport by its IATA code, search by name, autocomplete from a name prefix, or return the airports nearest to a set of coordinates.
Does the API cover countries as well as airports?
Yes. Alongside airport lookups, it lists countries and resolves a country by its code, so you can use it for country reference data too.
How does an agent find these lookups in Jentic?
The agent searches Jentic by intent, such as finding the nearest airport to a set of coordinates, and Jentic returns the matching operation ready to run.
GET STARTED