Amadeus APIs
31 APIs42 Endpoints5 Categories
Categories
API Catalog(6 of 31)
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 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 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.
Connect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famadeus.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famadeus.com" | 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.