Amadeus Flight Most Booked Destinations
Browse all Amadeus APIs✓ Official Vendor SpecAnalyticsBusiness Intelligenceoauth21 EndpointsREST
For Agents
Return the destinations most frequently booked from an origin city in a given month so an agent can surface popular routes or inform inventory planning.
Use for: List the top booked destinations from London in July, Find the most popular routes departing from JFK last month, Get booking volume rank for destinations from CDG, I want the top 10 booked cities from MAD this summer
Not supported: Does not return real-time prices, bookable offers, or hotel data — use only to retrieve ranked booked destinations from an origin city by month.
The Amadeus Flight Most Booked Destinations API returns a ranked list of the destinations most frequently booked from a given origin city in a given month. Each entry includes the destination IATA code, a booking volume rank, and a percentage share of the origin's total bookings. Travel sites and analysts use it to power 'top destinations from {city}' content, plan inventory, and benchmark route popularity without parsing transactional booking data themselves.
Install Jentic One Beta
Connect the Flight Most Booked Destinations to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flight Most Booked Destinations, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 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.
Capabilities
What an agent can do with Flight Most Booked Destinations API.
Return the top booked destinations from a given origin city for a specific calendar month
Rank destinations by booking volume and share of total origin bookings
Limit results to a configurable max page size for compact summaries
Compare booking demand across months to spot trending destinations
Sort by rank or analytics share to suit either popularity displays or analyst views
Use Cases
Patterns agents use Flight Most Booked Destinations API for, with concrete tasks.
★ Top Destinations Editorial Content
Travel publishers populate 'top 10 cities Londoners are flying to this month' articles by calling /travel/analytics/air-traffic/booked with originCityCode=LON and a period. The response is small enough to embed in a CMS as a static snapshot and refresh monthly, providing data-backed editorial without manually compiling booking figures.
Call /travel/analytics/air-traffic/booked with originCityCode=LON and period=2026-05 and return the top 10 destinations with their booking share.
Route Demand Benchmarking
Inventory and revenue teams at airlines, OTAs, and hotel chains track how a given destination's booking share evolves month over month from a key feeder market. The endpoint provides ranked share data without requiring a direct transactional feed and is fast enough to refresh weekly across hundreds of origin-month pairs.
Compare the booking share of MAD-LIS for January, February, and March 2026 by calling the booked-traffic endpoint for each period.
Personalised Destination Suggestions
Loyalty programs surface destinations that are currently popular among travellers from the same home airport as the user. The agent calls the most-booked endpoint with the user's home origin and the current month, then filters out destinations the user has already visited, leaving a short list of fresh ideas.
Get the top 20 booked destinations from LHR for the current month, exclude the user's last 5 visited cities, and return the remaining top 5.
Agent-Driven Route Insight via Jentic
An analyst-facing AI assistant answering 'what are people flying to from Paris right now?' calls Flight Most Booked Destinations through Jentic for the current month and summarises the top-ranked cities with their booking shares. Jentic resolves OAuth and parameter shaping, so the agent only declares the question.
Call jentic.search('most booked Amadeus destinations from a city'), load the operation, and execute it with originCityCode=PAR and period set to the current month to return ranked cities with shares.
Key Endpoints
1 endpoints — the amadeus flight most booked destinations api returns a ranked list of the destinations most frequently booked from a given origin city in a given month.
METHOD
PATH
DESCRIPTION
GET
/travel/analytics/air-traffic/booked
List most booked destinations from an origin city by month
GET
/travel/analytics/air-traffic/booked
List most booked destinations from an origin city by month
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Amadeus client_id and client_secret are stored encrypted in the Jentic vault. Jentic runs the OAuth 2.0 client_credentials exchange and refreshes the bearer token automatically before each analytics call.
Intent-based discovery
Agents search Jentic by intent ('most booked Amadeus destinations from a city') and Jentic returns the /travel/analytics/air-traffic/booked operation with its originCityCode and period parameters.
Time to first call
Direct Amadeus integration: 1 day for OAuth and city-code resolution. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Airport and City Search
Resolves city names to IATA codes required as input here.
Use upstream when the user names a city in natural language and the agent needs the IATA code.
FAQs
Specific to using Flight Most Booked Destinations API through Jentic.
What authentication does the Flight Most Booked Destinations API use?
Amadeus Self-Service OAuth 2.0 client_credentials. Exchange client_id and client_secret at https://api.amadeus.com/v1/security/oauth2/token for a bearer token and pass it in the Authorization header. Through Jentic, the credentials live in the encrypted vault and the token is refreshed automatically before each /travel/analytics/air-traffic/booked call.
What origin codes does the API accept?
It expects an IATA city code (such as LON, NYC, PAR), not an airport code. The Test environment only returns data for a small set of cities listed in the amadeus4dev/data-collection repo; Production covers any IATA city Amadeus indexes.
What are the rate limits for the Flight Most Booked Destinations API?
Amadeus Self-Service Test environment caps analytics endpoints at 10 transactions per second per API key with a monthly quota; Production limits scale with the chosen plan tier. Bearer tokens themselves expire after roughly 30 minutes.
How do I get the top booked destinations from a city through Jentic?
Run pip install jentic, then call jentic.search('most booked Amadeus destinations from a city'), load the operation, and execute it with originCityCode and period (YYYY-MM). Jentic handles the OAuth exchange and returns the ranked destination list.
How fresh is the booking data?
Amadeus aggregates the data per calendar month; you query by period in YYYY-MM format. The most recent complete month is typically available within a few days of month-end.
Is the Flight Most Booked Destinations API free?
The Test environment is free with limited monthly quota. Production access is metered per transaction under an Amadeus Self-Service plan; tier pricing is published on the Amadeus for Developers portal.
GET STARTED