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 endpointsThe 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 endpointsThe 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 endpointsThe 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 endpointsThe 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 endpointsThe 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 endpointsStep 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 | shStep 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.