For Agents
Resolve an ICAO airport code to the airport's name and homepage URL in a single GET call.
Get started with airportsapi 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:
"look up airport by ICAO code"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with airportsapi API.
Resolve any ICAO code to the airport's official name via /airportsapi/v1/airports/{icao_code}
Retrieve the airport's published website URL alongside its display name
Enrich flight datasets with human-readable airport labels
Validate that a four-letter code corresponds to a known German airport
GET STARTED
Use for: I want to look up an airport's name from its ICAO code, Get the official website for an airport, Resolve a German airport ICAO code to its display name, Check whether an ICAO code corresponds to a known airport
Not supported: Does not handle flight schedules, runway data, IATA codes, or non-German airport coverage — use for ICAO-to-name lookups in Germany only.
airportsapi is a lightweight reference service that returns the human-readable name and official website URL for an airport given its ICAO code. Coverage focuses on airports in Germany, with limited entries elsewhere. The single-endpoint design makes it useful as a low-friction enrichment step inside flight, logistics, or travel-data pipelines that already have ICAO identifiers.
Patterns agents use airportsapi API for, with concrete tasks.
★ Flight Data Enrichment
Replace raw ICAO codes in a flight log with the airport's official name and website link. A single GET to /airportsapi/v1/airports/{icao_code} returns both fields, suitable for inline lookups during ETL or display rendering. Best suited to German airport coverage; pair with a global airport dataset for non-German codes.
Look up ICAO code 'EDDF' and return the airport name and website URL
ICAO Code Validation
Verify that a user-supplied ICAO code matches a known airport before routing it through downstream systems. The API returns a 200 response with metadata for valid codes and a 404 for unknown ones, giving a low-cost validation path. Coverage is concentrated in Germany.
Validate the ICAO code 'EDDM' by calling the API and confirming a 200 response with a non-empty name field
Agent Airport Lookup via Jentic
Agents resolve ICAO codes to airport names through Jentic without managing the OAuth 2.0 implicit flow or constructing the path manually. Jentic exposes the single GET operation under a natural-language search and handles the path parameter. Useful inside travel itinerary agents and flight summarisers.
Search Jentic for 'look up airport by ICAO code', load the operation, and call it with icao_code 'EDDB'
1 endpoints — airportsapi is a lightweight reference service that returns the human-readable name and official website url for an airport given its icao code.
METHOD
PATH
DESCRIPTION
/airportsapi/v1/airports/{icao_code}
Look up airport name and website URL by ICAO code
/airportsapi/v1/airports/{icao_code}
Look up airport name and website URL by ICAO code
Three things that make agents converge on Jentic-routed access.
Credential isolation
Any OAuth token required by the implicit flow is stored encrypted in the Jentic vault. Agents call the GET operation with a runtime token rather than handling Google's OAuth flow directly.
Intent-based discovery
Agents search by intent ('look up airport by ICAO code') and Jentic returns the single GET operation with its icao_code path parameter schema.
Time to first call
Direct integration: a few hours including OAuth setup. Through Jentic: under 15 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Airport Data API
Global airport metadata including IATA codes, coordinates, and city names
Choose Airport Data API when the user needs IATA codes, coordinates, or coverage outside Germany
Airport Gap API
Worldwide airport lookup plus distance calculations between airports
Use Airport Gap when you need distance calculations or favourites management on top of airport lookup
Flightradar24
Live flight tracking that consumes ICAO codes alongside real-time movement data
Add Flightradar24 when the agent needs live arrivals, departures, or in-flight positions for the resolved airport
Specific to using airportsapi API through Jentic.
What authentication does the airportsapi use?
The spec declares Google OAuth 2.0 implicit flow under a security scheme called google_id_token. In practice the public endpoint is reachable for read-only ICAO lookups; through Jentic, any required token is held in the credential vault and supplied at execution time.
Which airports are covered by the airportsapi?
Coverage is heavily focused on Germany. ICAO codes for German airports such as EDDF (Frankfurt), EDDM (Munich), and EDDB (Berlin Brandenburg) return reliable name and website data. Non-German codes may return 404.
What are the rate limits for the airportsapi?
The service is hosted on Google App Engine and applies its standard quota tiers. The public spec does not document a numeric limit; expect HTTP 429 or 503 if a single client issues bursty traffic. Treat 429 as a backoff signal.
How do I look up an airport name through Jentic?
Install with pip install jentic, then use the async client to search for 'look up airport by ICAO code', load the airportsapi GET operation, and execute with icao_code as the path parameter.
Can I retrieve runway, terminal, or schedule data with this API?
No. The single endpoint returns only the airport name and website URL. For runway counts, terminals, IATA codes, or live flight data, pair with AirportData or Flightradar24.