canonical: https://jentic.com/apis/amadeus.com/amadeus-flight-most-booked-destinations

# Amadeus Flight Most Booked Destinations

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.

## For AI 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.

## Scope

Does not return real-time prices, bookable offers, or hotel data - use only to retrieve ranked booked destinations from an origin city by month.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| Method | Path | Description |
| --- | --- | --- |
| GET | /travel/analytics/air-traffic/booked | List most booked destinations from an origin city by month |

## Key resources

- **Booked Air Traffic Analytics** — Single GET endpoint returning the most booked destinations from a given origin city in a given month.

## Why Jentic

- **Setup:** Wiring the Flight Most Booked Destinations API by hand means handling the Amadeus OAuth 2.0 client_credentials exchange, refreshing the bearer token, and calling GET /travel/analytics/air-traffic/booked with the right query parameters against the correct Amadeus host and version. Through Jentic you install once, import Flight Most Booked Destinations from the API Directory, store the Amadeus client credentials once, and your agent calls it.
- **Permission scoping:** The origin city code and period travel as query parameters, not as a resource id in the URL path, so scoping is by operation. You limit the agent to the operations it needs, such as reading the most booked destinations from a city, and it cannot reach other Amadeus analytics or booking operations unless you add them.
- **Credential handling:** Your Amadeus client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which runs the client_credentials exchange and injects a fresh bearer token at execution time. The raw secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list the most booked destinations from Paris in July', and Jentic returns the /travel/analytics/air-traffic/booked operation with its originCityCode and period parameters so the agent reads the ranking without browsing the Amadeus docs.

## Related APIs

- **Flight Most Traveled Destinations** — Same shape, but ranks destinations by traffic volume rather than bookings.
- **Flight Busiest Traveling Period** — Identifies the busiest months to travel for a given origin.
- **Flight Inspiration Search** — Surfaces cheap destinations from an origin; pair with most-booked for popular and affordable.
- **Airport and City Search** — Resolves city names to IATA codes required as input here.

## FAQ

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

### Can I limit what my agent is allowed to do with the Flight Most Booked Destinations API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and scoping here is by operation since the origin city code and period travel as query parameters rather than as a resource id in the URL path. You grant the agent only the operations it needs, such as reading the most booked destinations from a city via GET /travel/analytics/air-traffic/booked, and it cannot reach any other Amadeus analytics or booking operations unless you add them. Your Amadeus client_id and client_secret stay stored by your own instance and are injected at execution time, so the agent never sees the raw secret.