Amadeus Airport Nearest Relevant
Browse all Amadeus APIs72
AI ReadinessAI-Aware (A-)72/100
Official vendor OpenAPI document · agent-readyMaps GeolocationPlaces Searchoauth21 EndpointsREST
For Agents
Find the nearest commercial airports to a coordinate, ranked by traffic. Agents call /reference-data/locations/airports with lat/long to seed flight searches with the right origin.
Use for: I want to find the nearest airport to a hotel address, Find all airports within 100 km of these GPS coordinates, Search for the busiest airport closest to a given lat/long, Get the IATA code for the airport nearest the user's current location
Not supported: Does not return flight schedules, terminal layouts, or non-commercial airfields - use for finding commercial airports closest to a coordinate only.
The Amadeus Airport Nearest Relevant API returns the commercial airports closest to a given latitude and longitude, ranked by relevance. The single GET endpoint at /reference-data/locations/airports takes coordinates plus an optional radius and returns each airport with its IATA code, distance, time zone, and an analytics score that reflects passenger traffic. It is used to default a flight search to the nearest airport and to suggest secondary airports for fare comparisons.
Install Jentic One Beta
Connect the Airport Nearest Relevant to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Airport Nearest Relevant, 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%2Famadeus.com%2Famadeus-airport-nearest-relevant" | 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%2Famadeus.com%2Famadeus-airport-nearest-relevant" | 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 Airport Nearest Relevant API.
Look up the nearest commercial airports to a latitude and longitude pair
Filter results to a configurable radius in kilometres around the coordinate
Rank nearby airports by analytics score so high-traffic hubs appear first
Retrieve each airport's IATA code, name, and distance for direct use in a flight search
Return time zone metadata so layover times can be computed without a second call
Suggest secondary airports within range for fare-comparison searches
Use Cases
Patterns agents use Airport Nearest Relevant API for, with concrete tasks.
★ Geo-Aware Flight Search
When a user opens a travel app the device exposes GPS coordinates but not an airport code. The /reference-data/locations/airports endpoint converts those coordinates into the closest commercial airport with an IATA code, which can then seed the origin field of a flight search. Sorting by analytics score keeps the default to the busiest airport rather than a small regional one.
Call /reference-data/locations/airports with latitude=48.85, longitude=2.35 and return the IATA code of the highest-ranked airport.
Multi-Airport Fare Comparison
Frequent travellers compare fares across several airports near their home. By calling the lookup with a radius of 100 km the API returns every commercial airport in range so the front end can run parallel flight searches against each origin. This catches cheaper fares from secondary airports that a single-airport search would miss.
Get every airport within 100 km of latitude=51.51, longitude=-0.13 and run a fare comparison across all returned IATA codes.
Travel Manager Coordinate Mapping
Corporate travel platforms often store meeting venues by address, not by airport. Geocode the address, then call the lookup to get the nearest airport for use in the booking flow. The endpoint returns distance and time zone in the same response, which is enough to flag long ground transfers in an itinerary.
After geocoding the venue address, fetch the closest airport for those coordinates and warn the user if the distance exceeds 80 km.
Agent-Driven Geo Booking
An AI travel agent given 'book a flight from where I am' needs to translate the user's GPS into an airport before calling Flight Offers Search. Through Jentic the agent searches for 'nearest airport to coordinates', loads the schema, and executes the lookup. The IATA code from the top result then feeds directly into the next operation.
Use Jentic to find the airport-nearest-relevant operation, pass the device coordinates, and feed the resulting IATA code into a Flight Offers Search call.
Key Endpoints
1 endpoints — the amadeus airport nearest relevant api returns the commercial airports closest to a given latitude and longitude, ranked by relevance.
METHOD
PATH
DESCRIPTION
GET
/reference-data/locations/airports
Find airports nearest to a coordinate, ranked by traffic
GET
/reference-data/locations/airports
Find airports nearest to a coordinate, ranked by traffic
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Airport Nearest Relevant
- AI-Aware (A-)72/100
100
Foundational Compliance80
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability100
Security50
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
80
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
49%
Example Density
How richly the API is illustrated with examples.
97%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
54%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
50
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
50%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Airport Nearest Relevant API by hand means running Amadeus OAuth2 to get a token, targeting the test.api.amadeus.com/v1 host, and refreshing that token yourself. Through Jentic you install once, import the Airport Nearest Relevant API from the API Directory, store the OAuth2 credentials once, and your agent calls it.
Permission scoping
The Airport Nearest Relevant API exposes a single read-only /reference-data/locations/airports endpoint whose coordinates travel as query parameters rather than a path resource, so limit the agent to that one operation. You choose whether the agent may call it, and no other operations exist to add.
Credential isolation
Your Amadeus OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find commercial airports nearest a coordinate', and Jentic returns the matching Amadeus operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Amadeus Airport & City Search
Looks up airports by keyword rather than by latitude and longitude.
Choose this when the agent has a typed place name; use Airport Nearest Relevant when only coordinates are available.
FAQs
Specific to using Airport Nearest Relevant API through Jentic.
What authentication does the Airport Nearest Relevant API use?
The API uses the Amadeus OAuth 2.0 client-credentials flow. Exchange API key and secret for a bearer token at the Amadeus token endpoint and send it on /reference-data/locations/airports calls. Jentic stores the credentials in the encrypted vault and refreshes tokens automatically.
Can I limit the search to a specific radius?
Yes. The endpoint accepts a radius parameter in kilometres so you can return only airports within, for example, 100 km of the supplied coordinate. The default radius and maximum allowed value are documented in the Amadeus self-service portal.
What are the rate limits for the Airport Nearest Relevant API?
Rate limits are not declared in the OpenAPI spec and depend on the Amadeus contract tier. The lookup is read-only and cacheable, so cache responses keyed on coordinate and radius to stay well under the per-second cap for your account.
How do I find the nearest airport through Jentic?
Run pip install jentic, then search Jentic for 'nearest airport to coordinates'. The /reference-data/locations/airports operation surfaces with its input schema; pass latitude, longitude, and radius and execute. The IATA code in the top result can flow straight into a Flight Offers Search.
Does the API return more than just the IATA code?
Yes. Each result includes the airport name, IATA code, distance from the supplied coordinate, time zone, and an analytics score that reflects passenger traffic, all in a single response.
Is the Airport Nearest Relevant API free?
Amadeus self-service APIs include a free test environment with quota limits and a paid production tier. Production access is contracted with Amadeus and pricing scales with transaction volume - check current rates in the developer portal.
Can I limit what my agent is allowed to do with the Airport Nearest Relevant API?
Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials your agent may use. This API exposes only a single read-only operation, a GET on /reference-data/locations/airports that takes the coordinate and radius as query parameters, and you choose whether the agent may call it. Because no other operations exist, that lookup is the full extent of what the agent can reach, and your stored Amadeus OAuth2 credentials are injected at execution time rather than exposed to the agent.
GET STARTED