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

# Amadeus Flight Most Traveled Destinations

The Amadeus Flight Most Traveled Destinations API returns the destinations with the highest actual passenger traffic from a given origin city in a given month. Each entry includes the destination IATA code, a traffic rank, and a percentage share of the origin's total traffic. Travel publishers and analysts use it for 'where Londoners are flying this month' content and to benchmark route activity, separate from the Most Booked endpoint, which reflects commercial bookings rather than flown traffic.

## For AI agents

Return the destinations with the highest passenger traffic from an origin city in a given month so an agent can surface where people actually fly, not just where they book.

## Scope

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

## Capabilities

- Return the top travelled destinations from a given origin city for a specific calendar month
- Rank destinations by passenger traffic and share of total origin traffic
- Limit results to a configurable max page size for compact summaries
- Compare flown traffic to commercial bookings on the same origin to detect mismatches
- Sort by rank or analytics share to suit either popularity displays or analyst views

## Use cases

### Where Are People Actually Flying Editorial

Travel publishers run a monthly piece showing the top destinations actually flown from a key feeder market by calling /travel/analytics/air-traffic/traveled with originCityCode and period. The traffic-based view differs from booking volumes (which can include unflown bookings) and produces a more honest 'real travel demand' headline.

Example prompt: Call /travel/analytics/air-traffic/traveled with originCityCode=LON and period=2026-05 and return the top 10 destinations with their traffic share.

### Bookings vs Traffic Variance Check

Revenue analysts call both Most Booked and Most Traveled for the same origin and period, then flag destinations where the booking rank diverges sharply from the traffic rank. A destination popular in bookings but low in traffic suggests a high cancellation or no-show rate worth investigating.

Example prompt: Get the top 20 booked and top 20 travelled destinations from PAR for last month and return any destination whose ranks differ by more than 5 positions.

### Hub Connectivity Audit

Airports and tourism boards audit how well their hub connects to global cities by ranking outbound traffic destinations by month. The endpoint provides a compact, machine-readable view suited to dashboards, without the integrator needing access to a flight-radar feed or proprietary booking warehouse.

Example prompt: Generate the top 25 outbound traffic destinations from CDG for each of the last 12 months and aggregate them into a connectivity dashboard.

### Agent-Driven Travel Trend Brief via Jentic

An AI assistant answering 'what are the busiest routes from Madrid right now?' calls Flight Most Traveled Destinations through Jentic, takes the top entries with their share, and writes a short briefing. Jentic resolves OAuth and parameter shaping so the agent only declares the question.

Example prompt: Call jentic.search('most travelled Amadeus destinations from a city'), load the operation, and execute it with originCityCode=MAD and the current month to return ranked cities with shares.

## Key endpoints

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

## Key resources

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

## Why Jentic

- **Setup:** Wiring the Flight Most Traveled 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/traveled with the right query parameters against the correct Amadeus host and version. Through Jentic you install once, import Flight Most Traveled 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 travelled 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 travelled destinations from Tokyo in March', and Jentic returns the /travel/analytics/air-traffic/traveled operation with its originCityCode and period parameters so the agent reads the ranking without browsing the Amadeus docs.

## Related APIs

- **Flight Most Booked Destinations** — Same shape, but ranks destinations by bookings rather than flown traffic.
- **Flight Busiest Traveling Period** — Identifies the busiest months to travel from a given origin.
- **Flight Inspiration Search** — Surfaces cheap destinations from an origin; pair with most-travelled 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 Traveled 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, credentials live in the encrypted vault and the token is rotated automatically before each /travel/analytics/air-traffic/traveled call.

### How does this differ from the Most Booked Destinations API?

Most Traveled ranks destinations by actual passenger traffic flown in the period, while Most Booked ranks them by commercial bookings made in that period. Bookings can include unflown reservations and cancellations, so the two views often diverge.

### What are the rate limits for the Flight Most Traveled 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 travelled destinations from a city through Jentic?

Run pip install jentic, then call jentic.search('most travelled Amadeus destinations from a city'), load the operation, and execute it with originCityCode and period in YYYY-MM. Jentic handles the OAuth exchange and returns the ranked destination list.

### Which origin codes are accepted?

An IATA city code such as LON, NYC, or PAR. Test environment coverage is limited to the city set documented in the amadeus4dev/data-collection repo; Production covers any IATA city Amadeus indexes.

### Is the Flight Most Traveled Destinations API free?

The Test environment is free with limited monthly quota. Production access is metered per transaction under an Amadeus Self-Service plan; pricing is published on the Amadeus for Developers portal.

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

Yes. Because you run your own self-hosted Jentic One instance, your own rules decide which operations and credentials the agent may use. This API takes the origin city code and period as query parameters rather than as a resource id in the path, so scoping is by operation: you grant only the read on GET /travel/analytics/air-traffic/traveled that returns ranked travelled destinations from a city. With that scope in place the agent cannot reach other Amadeus analytics or booking operations, and it never sees your raw Amadeus client_id or client_secret.