Amadeus APIs
31 APIs42 Endpoints5 Categories
Categories
API Catalog
Airline Code Lookup API
The Amadeus Airline Code Lookup API resolves IATA and ICAO airline codes to full carrier names and metadata. Given a code such as BA or AAL, it returns the carrier's commercial name and identifier mappings, which is essential for displaying human-readable airline names in flight search results, itineraries, and reporting. The single GET endpoint at /reference-data/airlines is read-only and is typically used as an enrichment step alongside Amadeus flight shopping APIs.
1 endpointsAirport & 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 endpointsAirport On-Time Performance
The Amadeus Airport On-Time Performance API predicts the probability that flights from a given airport will depart on time on a specified date. The single GET endpoint at /airport/predictions/on-time accepts an airport IATA code and a date and returns a probability score derived from historical performance and forecast conditions. It is used to flag risky connections and to decide whether to recommend buffer time on multi-leg itineraries.
1 endpointsBranded Fares Upsell
The Amadeus Branded Fares Upsell API takes a flight offer and returns the carrier's branded fare families for that itinerary, complete with included services such as bags, seat selection, and refundability. The single POST to /shopping/flight-offers/upselling sends an existing flight offer payload back to Amadeus and gets matching upsell options, so booking flows can present 'Economy Light' through 'Business Flex' tiers side by side. It targets airline.com replacement experiences and corporate booking tools that need branded merchandising rather than a single base fare.
1 endpointsFlight Availabilities Search
The Amadeus Flight Availabilities Search API returns seat availability per booking class for one or more origin-destination pairs and dates. The single POST to /shopping/availability/flight-availabilities is closer to a GDS availability call than to a fare search — it gives the number of bookable seats per Reservation Booking Designator on each flight segment, which is what travel agencies and OTAs need to construct multi-segment tickets without overselling. Use this when a fare-only search is not enough and you need raw availability per cabin class.
1 endpointsFlight Busiest Traveling Period
The Amadeus Flight Busiest Traveling Period API returns the busiest months of the year for a given city, ranked by passenger or arrivals volume. The single GET endpoint at /travel/analytics/air-traffic/busiest-period accepts a city IATA code and a year and returns each month with a traveller count and a score, which is enough to surface 'best time to visit' insights or to plan capacity-aware marketing campaigns. Data is derived from anonymised historical traffic.
1 endpointsFlight Cheapest Date Search
The Amadeus Flight Cheapest Date Search API returns the cheapest available dates to fly between two cities, ranked by total fare. The single GET endpoint at /shopping/flight-dates accepts an origin, destination, and a flexible date range and returns price points keyed by date pair, which is what powers 'when is it cheapest?' calendar widgets and flexible-date search experiences. It is intended for inspirational and flexible-date searches rather than precise booking flows.
1 endpointsFlight Check-in Links
The Amadeus Flight Check-in Links API returns the official online check-in URL for a given carrier, by IATA code. The single GET endpoint at /reference-data/urls/checkin-links accepts an airline IATA code and an optional language and returns the carrier's web check-in entry point, so itinerary emails and trip-detail screens can deep-link travellers straight to the right place. It is a small but high-value lookup that removes the need to maintain a hand-curated table of carrier check-in URLs.
1 endpointsFlight Choice Prediction
The Amadeus Flight Choice Prediction API scores a list of flight offers with the probability that a traveller will pick each option. It takes a flight-offers payload (typically the output of Flight Offers Search) and returns the same offers annotated with a probability value, so booking flows can re-rank or highlight the most likely choice. The API is intended to sit between search and pricing or order creation, helping travel sites surface fewer, better options instead of dumping a long list on the user.
1 endpointsFlight Create Orders
The Amadeus Flight Create Orders API turns a priced flight offer into a confirmed booking with a Passenger Name Record. The single POST endpoint takes a flight offer (already validated by Flight Offers Price), traveller details, and contact information, and returns an order id, ticketing status, and the underlying PNR reference. It is the final step in the Self-Service flight-shopping flow before payment is captured downstream by the integrator.
1 endpointsFlight Delay Prediction
The Amadeus Flight Delay Prediction API estimates the probability that a given scheduled flight will be delayed and assigns it to one of four delay segments — under 30 minutes, 30 to 60, 60 to 120, or over 120 minutes. The single GET endpoint takes the carrier code, flight number, scheduled departure date and time, origin, destination, duration, and aircraft code, and returns probability scores per segment. Travel apps use it to set traveller expectations, suggest tighter or looser connection times, and prioritise rebooking outreach.
1 endpointsFlight Inspiration Search
The Amadeus Flight Inspiration Search API answers the question 'where can I fly from here for cheap?' Given an origin IATA code, it returns the cheapest destinations Amadeus has cached for that origin within an optional date range, max price, duration, and one-way or round-trip filter. Each entry includes a sample price, sample dates, and a link to a follow-up Flight Offers Search call. Travel sites use it to power 'cheap flights from London' homepage modules without running an exhaustive search at request time.
1 endpointsFlight Most Booked Destinations
The Amadeus Flight Most Booked Destinations API returns a ranked list of the destinations most frequently booked from a given origin city in a given month. Each entry includes the destination IATA code, a booking volume rank, and a percentage share of the origin's total bookings. Travel sites and analysts use it to power 'top destinations from {city}' content, plan inventory, and benchmark route popularity without parsing transactional booking data themselves.
1 endpointsFlight Most Traveled Destinations
The Amadeus Flight Most Traveled Destinations API returns the destinations with the highest actual passenger traffic from a given origin city in a given month. Each entry includes the destination IATA code, a traffic rank, and a percentage share of the origin's total traffic. Travel publishers and analysts use it for 'where Londoners are flying this month' content and to benchmark route activity, separate from the Most Booked endpoint, which reflects commercial bookings rather than flown traffic.
1 endpointsFlight Offers Price
The Amadeus Flight Offers Price API reconfirms the live price, taxes, and fare conditions of one or more flight offers returned by Flight Offers Search. The single POST endpoint takes a flight-offers payload and returns a verified price block with detailed fare components, baggage allowances, fare rules, and any availability changes since the original search. Booking flows call it as the gate between search and order creation, since search results are cached and may drift before checkout.
1 endpointsFlight Offers Search
Jentic publishes the only available OpenAPI specification for Flight Offers Search, keeping it validated and agent-ready. The Amadeus Flight Offers Search API returns priced flight itineraries from over 500 airlines on demand. It supports both a GET endpoint for simple round-trip queries and a POST endpoint for complex multi-city, multi-passenger searches with cabin class, fare type, and connection constraints. Travel platforms, online travel agencies, and corporate booking tools use it to power live flight search experiences with real availability and fares.
2 endpointsFlight Order Management
The Amadeus Flight Order Management API retrieves and cancels flight orders previously created via Flight Create Orders. The two endpoints — GET and DELETE on /booking/flight-orders/{flight-orderId} — let an integrator pull the full order state including travellers, segments, ticketing status, and PNR reference, or cancel the order within the airline's void window. It is the post-booking servicing layer of the Amadeus Self-Service flight stack.
2 endpointsFlight Price Analysis
The Amadeus Flight Price Analysis API returns historical price quartiles for a given itinerary, telling the user whether a quoted fare is cheap, average, or expensive for the route and dates. The single GET endpoint takes origin, destination, departure date, currency, and optional return date and one-way flag, and returns the minimum, first quartile, median, third quartile, and maximum prices observed for similar itineraries. Travel sites use it to display 'good deal' or 'high price' badges next to live offers.
1 endpointsHotel Booking
The Amadeus Hotel Booking API turns a confirmed hotel offer into a real reservation with the underlying hotel provider. The single POST endpoint takes an offer id from Hotel Search, traveller and guest details, plus payment information, and returns one or more booking ids and provider confirmation numbers. It is the final step in the Self-Service hotel flow and submits real reservations against live hotel inventory, so test bookings should never run against the production environment.
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 endpointsHotel Ratings
The Amadeus Hotel Ratings API returns aggregated guest sentiment scores for hotels identified by Amadeus hotelIds. Each call returns an overall sentiment score together with a breakdown across categories such as service, room, location, and value, computed from review text mined across multiple sources. The single endpoint accepts up to several hotelIds at once and is designed to enrich booking interfaces, comparison shoppers, and ranking algorithms with quality signals beyond star ratings.
1 endpointsHotel Search API
The Amadeus Hotel Search API returns live hotel offers — rates, room types, board options, cancellation policies — for a list of Amadeus hotelIds and a stay window. It powers the price-and-availability step of a hotel booking funnel: take a shortlist of hotels and produce concrete, bookable offers with offerIds that can be confirmed downstream by the Hotel Booking API. Two endpoints cover the flow: a list call that returns offers across many hotels at once, and a detail call that re-prices a single offer before booking.
2 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 endpointsOn-Demand Flight Status
The Amadeus On-Demand Flight Status API returns the current operational status of a specific flight, including scheduled and actual departure and arrival times, terminal and gate assignments, aircraft type, and any reported delay or cancellation. It is keyed by carrier code, flight number, and scheduled departure date, so a single GET call returns everything needed to power a flight tracking widget, a delay-alert pipeline, or a passenger notification flow.
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 endpointsSeatmap Display
The Amadeus Seatmap Display API returns the cabin layout and per-seat metadata for a flight, enabling the seat-selection step of a booking flow. Two endpoints cover the common patterns: a GET keyed on a confirmed flight order id, and a POST that accepts an in-progress flight offer and returns the seat map before the booking is committed. Each seat in the response includes coordinates, characteristics (window, aisle, exit row, extra legroom), availability, and applicable price.
2 endpointsTours and Activities
The Amadeus Tours and Activities API returns bookable experiences — guided tours, attraction tickets, day trips — around a geographic location. Three endpoints cover the access patterns: a radius search around a coordinate, a bounding-box search across a rectangular area, and a detail lookup by activity id. Each result includes pricing, ratings, an image, and a booking URL, making it suitable for itinerary apps and travel concierge agents that want to surface concrete things to book at a destination.
3 endpointsTravel Recommendations API
The Amadeus Travel Recommendations API returns suggested destinations for a traveller based on cities they already like. Provide a seed of one or more city codes and the API returns destinations chosen by other travellers with similar preferences, complete with relevance scores. The single endpoint is designed for inspiration surfaces — homepage carousels, 'where next' modules, and AI travel concierges that need to suggest destinations rather than wait for the user to pick one.
1 endpointsTrip Purpose Prediction
The Amadeus Trip Purpose Prediction API classifies a flight itinerary as either business or leisure travel. It analyses origin, destination, departure and return dates, and the search timestamp to return a prediction with a probability score. This is a single-endpoint inference service designed for travel platforms, airline marketing teams, and travel agents that need to tailor offers, content, or upsell flows based on the inferred motivation behind a trip.
1 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.