Amadeus APIs
31 APIs42 Endpoints5 Categories
Categories
API Catalog(6 of 31)
Airport & City Search
The Amadeus Airport & City Search API turns partial place strings into structured airport and city records for autocomplete and search experiences. The /reference-data/locations endpoint accepts a keyword such as 'lon' and returns matching airports and cities with IATA codes, geo coordinates, time zones, and the parent metropolitan area, while /reference-data/locations/{locationId} returns a single record by ID. It is the standard building block behind 'where do you want to go?' inputs in flight and travel UIs.
2 endpointsAirport Nearest Relevant
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.
1 endpointsHotel Name Autocomplete
The Amadeus Hotel Name Autocomplete API returns matching hotels and destinations from a partial keyword, helping booking interfaces and travel agents surface suggestions as a user types. It searches hotel names, chains, cities, and airports across the Amadeus reference data set and returns the IATA code, geographic coordinates, and hotel identifiers needed to feed downstream search calls. The single endpoint is built for low-latency typeahead use, with configurable result counts and category filters for hotels, locations, or both.
1 endpointsLocation Score
The Amadeus Location Score API returns category-rated areas around a geographic point, scoring nearby zones for travel-relevant categories such as sights, restaurants, shopping, nightlife, and transport. It is designed for travel planners that need to characterise a destination beyond a single coordinate — surfacing 'where to stay for nightlife' or 'best zone for sightseeing' in a city. The single endpoint accepts latitude and longitude with optional radius and category filters and returns rated polygons with a score per category.
1 endpointsPoints of Interest
The Amadeus Points of Interest API returns named landmarks and attractions around a geographic location, with category labels (sights, restaurants, shopping, nightlife) and popularity ranks. Three endpoints cover the common access patterns: a radius search around a coordinate, a bounding-box search across a rectangular area, and a detail lookup by point-of-interest id. The API is designed for travel itinerary builders, city-guide apps, and AI agents that need to populate a destination with concrete things to do.
3 endpointsSafe Place
The Amadeus Safe Place API returned safety ratings for geographic areas, scoring them across categories such as women safety, physical harm, theft, political freedom, medical, and LGBTQ safety. Three endpoints covered the access patterns: a radius search around a coordinate, a bounding-box search over a rectangular area, and a detail lookup by safety-rated location id. Note that this API was scheduled for permanent decommission by Amadeus on 12 April; review the current Amadeus self-service portal before integrating, and consider GeoSure as the vendor-recommended alternative for safety scoring.
3 endpointsConnect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.