Amadeus On-Demand Flight Status
Browse all Amadeus APIs0
AI ReadinessNon-Ready (F)0/100
Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationoauth21 EndpointsREST
For 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.
Use for: Get the current status of flight BA123 on 2026-07-04, Check whether American Airlines flight 100 is delayed today, Retrieve the actual departure time for a specific flight, Find the gate and terminal for flight LH456 tomorrow
Not supported: Does not handle bookings, schedules in bulk, or passenger record management - use for status of a specific flight on a specific date only.
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.
Install Jentic One Beta
Connect the On-Demand Flight Status to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the On-Demand Flight Status, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
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%2Famadeus-on-demand-flight-status" | 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%2Famadeus-on-demand-flight-status" | 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.
Capabilities
What an agent can do with On-Demand Flight Status API.
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
Patterns agents use On-Demand Flight Status API for, with concrete tasks.
★ 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.
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.
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.
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
1 endpoints — 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.
METHOD
PATH
DESCRIPTION
GET
/schedule/flights
Get current status of a specific flight
GET
/schedule/flights
Get current status of a specific flight
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
O
On-Demand Flight Status
- Non-Ready (F)0/100
73
Foundational Compliance73
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability100
Security0
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
73
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
38%
Example Density
How richly the API is illustrated with examples.
79%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
50%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
0
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
0%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using On-Demand Flight Status API through Jentic.
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.
GET STARTED