Flight Most Traveled Destinations

Name: Flight Most Traveled Destinations API
Brand: Flight Most Traveled Destinations
Availability: InStock

✓ Official Vendor SpecAnalyticsBusiness Intelligenceoauth21 EndpointsREST

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

Quickstart

Get started with Flight Most Traveled Destinations in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"most travelled Amadeus destinations from a city"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Flight Most Traveled Destinations API.

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

GET STARTED

Start building with Flight Most Traveled Destinations API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Flight Most Traveled Destinations API for, with concrete tasks.

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

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.

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.

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.

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

1 endpoints — 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.

METHOD

PATH

DESCRIPTION

GET

/travel/analytics/air-traffic/traveled

List most travelled destinations from an origin city by month

GET

/travel/analytics/air-traffic/traveled

List most travelled destinations from an origin city by month

Why though 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 travelled Amadeus destinations from a city') and Jentic returns the /travel/analytics/air-traffic/traveled 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.

Alternative

Flight Most Booked Destinations

Same shape, but ranks destinations by bookings rather than flown traffic.

Use when the commercial-booking signal matters more than the realised traffic signal.

Complementary

Flight Busiest Traveling Period

Identifies the busiest months to travel from a given origin.

Use to pick which period to query the most-travelled endpoint for.

Complementary

Flight Inspiration Search

Surfaces cheap destinations from an origin; pair with most-travelled for popular and affordable.

Use together when the agent should rank destinations by both traffic and price.

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 Traveled Destinations API through Jentic.

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.