Amadeus APIs

31 APIs42 Endpoints5 Categories

API Catalog(4 of 31)

Flight 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 endpoints

Flight 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 endpoints

Flight 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 endpoints

Flight 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 endpoints

Connect Your Agent

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 | sh

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 instance

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