Amadeus APIs

31 APIs42 Endpoints5 Categories

API Catalog(3 of 31)

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

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

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