canonical: https://jentic.com/apis/amadeus.com/amadeus-on-demand-flight-status

# Amadeus On-Demand Flight Status

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

## For AI agents

Look up the current operational status of a specific flight by carrier code, flight number, and date - including scheduled vs actual times, gates, terminals, and delay reasons.

## Scope

Does not handle bookings, schedules in bulk, or passenger record management - use for status of a specific flight on a specific date only.

## Capabilities

- Retrieve scheduled and actual departure and arrival times for a specific flight
- Surface gate, terminal, and aircraft type for a flight on a given date
- Detect cancellations and delays so an agent can trigger rebooking workflows
- Pass carrier code plus flight number plus date to identify any commercial flight in the Amadeus schedule
- Power passenger notification flows that alert travellers to status changes

## Use cases

### Passenger flight status alerts

Power an alert pipeline that notifies travellers about gate changes, delays, and cancellations on their booked flights. Poll the On-Demand Flight Status endpoint at appropriate intervals before departure (more frequent in the final hours), compare results to the previously known state, and trigger SMS, push, or email notifications when something changes. The single endpoint is easy to schedule and the response shape is stable.

Example prompt: Call GET /schedule/flights with carrierCode=BA flightNumber=123 scheduledDepartureDate=2026-07-04 every 30 minutes and emit an alert if the departure time changes.

### Operational dashboard for travel managers

Travel managers handling a portfolio of business-traveller bookings need a real-time view of which flights are on time, delayed, or cancelled. Hitting On-Demand Flight Status for each booked flight returns the canonical status data needed to drive a dashboard - colour-coding flights by delay risk and surfacing actionable items like 'rebook needed' for cancellations. Pair with internal CRM to map flights to traveller records.

Example prompt: For each of 50 booked flights, call /schedule/flights once per hour and return any with status CANCELLED or with a delay greater than 30 minutes.

### AI agent travel assistant

An AI agent helping a traveller throughout their day uses On-Demand Flight Status to answer 'is my flight on time?' with current data rather than stale information. The agent calls Jentic to discover the operation, executes it with the carrier code, flight number, and date from the user's itinerary, and returns the actual status, gate, and any delay reason in a natural-language reply.

Example prompt: Use Jentic to search 'check flight status', execute On-Demand Flight Status with the user's carrier code, flight number, and date, and return a one-sentence status summary with current gate.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /schedule/flights | Get current status of a specific flight |

## Key resources

- **Schedule Flights** — Single endpoint that returns the operational status of a specific flight on a specific date.

## Why Jentic

- **Setup:** Wiring On-Demand Flight Status by hand means running the Amadeus Self-Service OAuth 2.0 client_credentials exchange, refreshing the bearer token before it expires, choosing the v2 test or production host, and passing the carrierCode, flightNumber, and scheduledDepartureDate triplet on each poll. Through Jentic you install once, import On-Demand Flight Status from the API Directory, store the client_id and client_secret once, and your agent calls it.
- **Permission scoping:** The carrier code, flight number, and date travel as query parameters on the GET to /schedule/flights, not in the URL path, so scoping is by operation rather than by a specific flight. Limit the agent to the operations it needs, such as reading current flight status, and it stays a read-only status caller with no path to booking or order operations.
- **Credential handling:** Your Amadeus client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which runs the OAuth exchange and injects a fresh bearer token at execution time. The secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check flight status', and Jentic returns the /schedule/flights operation with its carrierCode, flightNumber, and scheduledDepartureDate parameters so the agent calls it directly.

## Related APIs

- **Amadeus Airport On-Time Performance** — Airport On-Time Performance gives historical reliability for an airport; On-Demand Flight Status gives the current status of a specific flight.
- **Amadeus Flight Delay Prediction** — Delay Prediction estimates the probability of a future delay; On-Demand Flight Status reports the actual operational status.
- **Amadeus Flight Order Management** — Flight Order Management lets you act on a delay or cancellation by retrieving and amending a booked itinerary.

## FAQ

### What authentication does the On-Demand Flight Status API use?

OAuth 2.0 client credentials. Exchange your Amadeus API key and secret for a bearer access token, then pass it as the Authorization header on each call. Through Jentic, the client secret stays encrypted in the vault and the agent only ever receives a scoped token.

### What inputs identify a flight?

GET /schedule/flights requires carrierCode (the IATA airline code, e.g. BA), flightNumber (e.g. 123), and scheduledDepartureDate (YYYY-MM-DD). The triplet uniquely identifies any commercial flight on the Amadeus schedule.

### What status fields are returned?

Each response includes scheduled and actual departure and arrival times, terminal and gate, aircraft equipment, the operating airline, and a status code indicating on-time, delayed, or cancelled. This is the same data Amadeus surfaces to GDS-connected travel agents.

### What are the rate limits for the On-Demand Flight Status API?

Amadeus enforces per-second and per-month transaction quotas that vary by environment. The test environment is suitable for development with low quotas; production limits are configured in your Amadeus for Developers contract.

### How do I check flight status through Jentic?

Install with pip install jentic, then search 'check flight status' to discover the On-Demand Flight Status operation. Load its schema and execute with carrierCode, flightNumber, and scheduledDepartureDate. Jentic returns the parsed status payload ready for use. Get started with Jentic One, the self-hosted execution layer.

### Is the test environment a good source of live data?

The test environment returns a representative subset of flights and may not reflect every commercial flight worldwide. Use it for prototyping; for live operational data, upgrade to the production tier.

### Can I limit what my agent is allowed to do with the On-Demand Flight Status API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use, so you can grant it only the read-only GET /schedule/flights operation. The carrier code, flight number, and date travel as query parameters rather than in the URL path, so the agent scopes to the status-lookup operation as a whole and never gains a path to booking or order-management calls. Scoped this way, it stays a read-only status caller that can check a flight but cannot amend an itinerary.