Register a Self-Service app in the Amadeus for Developers portal to get an API Key/Secret, then obtain an OAuth2 access token via the Client Credentials grant, the same auth flow used by all Amadeus self-service APIs.
Call GET /v1/travel/predictions/flight-delay (test.api.amadeus.com for the test environment) with the Bearer access token in the Authorization header.
Supply query parameters describing the exact flight: originLocationCode, destinationLocationCode, departureDate (YYYY-MM-DD), departureTime (HH:MM:SS), arrivalDate, arrivalTime, aircraftCode, carrierCode, flightNumber, and duration (ISO 8601, e.g. PT31H10M).
Read the response's delay-probability breakdown, which gives a likelihood distribution across delay bands (e.g. under 30 minutes, 30-60, 60-120, over 120 minutes/cancelled) so you can surface a delay-risk indicator to the traveller before booking.
Source the carrierCode/flightNumber/aircraftCode/duration parameters from the specific segment of a Flight Offers Search result you're evaluating, so the prediction matches the actual flight being considered.
Use an official SDK where possible (e.g. amadeus-python's amadeus.travel.predictions.flight_delay.get(...), or the amadeus-node/java equivalents) instead of hand-building the query string.
Known gotchas
DECOMMISSIONED 2026-07-17: Amadeus shut down the Self-Service APIs portal — self-service API keys are disabled and the portal is inaccessible as of this date. These endpoints remain available only through an Amadeus Enterprise contract (Enterprise portal unaffected). Self-serve alternatives: Duffel, or an aggregator. Do not attempt self-service key registration; it was paused before shutdown.
All flight-identifying parameters (departure/arrival date+time, aircraftCode, carrierCode, flightNumber, duration) must be supplied together and must match a real, currently scheduled flight — you can't query with just origin/destination/date.
This is a probabilistic ML model trained on historical delay data, not a live/real-time delay feed, so it should be presented to users as a risk estimate rather than a guaranteed status.
Like other Amadeus self-service APIs, test-environment credentials/quota are separate from production; moving from test.api.amadeus.com to the production host typically requires your app to be upgraded/approved for production access first.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?