canonical: https://jentic.com/apis/aviationdata.systems/aviationdata

# AviationData.Systems Airports API V1

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.

## For AI agents

Lets an AI agent look up airports by IATA code, name, or proximity to coordinates and list countries and their codes.

## Scope

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.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Given a city's coordinates, return the nearest airport to the user.

## Key endpoints

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

## Key resources

- **Airport by IATA** — Find an airport by its IATA code
- **Airport by name** — Search or autocomplete airports by name
- **Nearest airports** — Airports closest to a set of coordinates
- **Countries** — Country lookups by code and the country list

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Amadeus** — Provides travel data including flights, airports, and bookings.
- **Amadeus Airport & City Search** — Searches airports and cities for travel autocomplete.
- **LocationIQ** — Geocodes addresses and coordinates to place data.

## FAQ

### 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.