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

Install Jentic One Beta

Connect the Flight Most Traveled Destinations to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flight Most Traveled 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.

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 | sh

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 instance

Jentic 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 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

GET STARTED

Start building with Flight Most Traveled Destinations API

Explore with Jentic

View OpenAPI Document

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

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.