Airport Data API

Name: Airport Data API API
Brand: Airport Data API
Availability: InStock

★ Only Publicly Available SpecData EnrichmentAddress Validationnone5 EndpointsREST

For Agents

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

Quickstart

Get started with Airport Data API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"resolve an airport by IATA code"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Airport Data API API.

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

GET STARTED

Start building with Airport Data API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Airport Data API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Airport Data API API for, with concrete tasks.

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

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.

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.

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.

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

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for airport data api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Airport Data API requires no credentials. Jentic still routes the call through its execution layer for consistent telemetry and retry logic, so agents receive the same interface as authenticated APIs.

Intent-based discovery

Agents search by intent ('look up airport by IATA code', 'find nearby airports') and Jentic returns the matching GET operation with its parameter schema.

Time to first call

Direct integration: under an hour for any of the five endpoints. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Airport Gap API

Adds distance calculations and favourites on top of airport lookup

Choose Airport Gap when you need distance-between-airports calculations or persistent favourites; choose Airport Data for free no-auth lookups

Alternative

Amadeus Airport & City Search

Commercial-grade airport and city search with deeper metadata and SLA

Use Amadeus when you need GDS-grade reliability, multi-language city search, and integration with booking flows

Complementary

Flightradar24

Live flight tracking layered on top of resolved airport identifiers

Add Flightradar24 when the resolved airport needs live departure/arrival data for status updates

FAQs

Specific to using Airport Data API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.