canonical: https://jentic.com/apis/airportdata.com/airportdata

# Airport Data API

Jentic publishes the only available OpenAPI specification for Airport Data API, keeping it validated and agent-ready. Airport Data API is a free reference service that returns IATA and ICAO codes, names, geographic coordinates, and other airport attributes. The five endpoints support listing all airports, lookup by IATA or ICAO code, free-text search, and nearby-airport queries by latitude/longitude. Useful for travel apps, flight planners, and any pipeline that needs to resolve airport identifiers to structured records.

## For AI agents

Resolve airport identifiers, search by name, and find airports near a coordinate using a free public API.

## Scope

Does not handle flight schedules, ticket pricing, live tracking, or runway-level data - use for static airport metadata lookup only.

## Capabilities

- Resolve IATA codes to full airport records via /airports/iata/{iataCode}
- Resolve ICAO codes to full airport records via /airports/icao/{icaoCode}
- Search airports by partial name or city through /airports/search/{searchTerm}
- Find the nearest airports to a given latitude/longitude pair
- List the full airport catalogue for offline indexing or local caching

## Use cases

### IATA/ICAO Code Resolution

Convert raw IATA or ICAO codes inside a flight or itinerary record into full airport metadata including name, city, country, and coordinates. The dedicated /airports/iata/{iataCode} and /airports/icao/{icaoCode} endpoints return a single record per call with typical response under 100 ms. No API key is required.

Example prompt: Look up IATA code 'JFK' and return the airport name, city, country, and coordinates

### Nearby Airport Discovery

Suggest the closest airports to a user's location using the /airports/nearby/{latitude}/{longitude} endpoint. Useful for hotel apps, ride-sharing handoff to airport rides, and travel itineraries that infer departure/arrival airports from a city address. Returns airports ranked by distance.

Example prompt: Find airports near latitude 40.7128, longitude -74.0060 and return the top 3 ranked by distance

### Airport Search Autocomplete

Drive a city- or airport-name autocomplete in a booking flow by hitting /airports/search/{searchTerm} on each keystroke after a 200 ms debounce. The endpoint returns matching airports ordered by relevance, supporting typo-tolerant prefix matching for cities and airport names.

Example prompt: Search for airports matching 'london' and return the top 5 results with IATA codes

### Agent Airport Enrichment via Jentic

An itinerary or travel agent enriches raw flight codes by searching Jentic for the right Airport Data operation and executing it with the IATA or ICAO code. Because the API requires no key, end-to-end search-load-execute typically completes in under a second through Jentic.

Example prompt: Search Jentic for 'resolve an airport by IATA code', load the operation, and execute it with iataCode 'LHR'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /airports | List all airports |
| GET | /airports/iata/{iataCode} | Resolve an airport by IATA code |
| GET | /airports/icao/{icaoCode} | Resolve an airport by ICAO code |
| GET | /airports/search/{searchTerm} | Search airports by name or city |
| GET | /airports/nearby/{latitude}/{longitude} | Find airports near a coordinate |

## Key resources

- **Airports** — List, search, and look up airports by IATA or ICAO code or by proximity

## Why Jentic

- **Setup:** Wiring Airport Data by hand still means building lookup calls, handling responses, and writing your own retry logic even though it needs no credentials. Through Jentic you install once, import Airport Data from the API Directory, and your agent calls it through the same execution layer as authenticated APIs.
- **Permission scoping:** Airport Data needs no credentials and is read-only, so scope your agent by operation: limit it to the operations it needs, such as IATA lookup or nearby search, and leave out the ones it does not use.
- **Credential handling:** Airport Data requires no credential, and Jentic still routes each call through your own Jentic One instance for consistent execution. No secret enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up airport by IATA code' or 'find nearby airports', and Jentic returns the matching GET operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Airport Gap API** — Adds distance calculations and favourites on top of airport lookup
- **Amadeus Airport & City Search** — Commercial-grade airport and city search with deeper metadata and SLA
- **Flightradar24** — Live flight tracking layered on top of resolved airport identifiers

## FAQ

### Why is there no official OpenAPI spec for Airport Data API?

Airport Data API does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Airport Data API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Airport Data API use?

None. The API is fully public; no key, token, or signed request is required. Through Jentic the operation is exposed unchanged so agents can call it with no credential setup.

### Can I find airports near a coordinate with the Airport Data API?

Yes. GET /airports/nearby/{latitude}/{longitude} returns airports ranked by distance from the supplied point. Useful for inferring departure airports from a hotel address or user GPS fix.

### What are the rate limits for the Airport Data API?

The service does not publish a documented rate cap, but as a free public API it should be treated with polite client behaviour: cache responses, avoid bursty traffic, and back off on any HTTP 429 or 503.

### How do I resolve an IATA code through Jentic?

Install with pip install jentic, then search for 'resolve an airport by IATA code', load the /airports/iata/{iataCode} operation, and execute with the iataCode path parameter. No bearer token or API key is needed.

### Does the Airport Data API include flight schedules or live status?

No. It is reference data only - names, codes, and coordinates. For schedules and live arrivals/departures use Flightradar24 or Amadeus alongside this API.

### Can I limit what my agent is allowed to do with the Airport Data API?

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, and Airport Data is read-only with no credentials to manage. Scope by operation: allow only the endpoints the agent needs, such as IATA lookup or nearby search, and leave out the ones it does not use, like the full airport list or ICAO lookup. The agent can then resolve the codes or coordinates you permit and nothing more.