canonical: https://jentic.com/apis/amadeus.com/amadeus-flight-busiest-traveling-period

# Amadeus Flight Busiest Traveling Period

The Amadeus Flight Busiest Traveling Period API returns the busiest months of the year for a given city, ranked by passenger or arrivals volume. The single GET endpoint at `/travel/analytics/air-traffic/busiest-period` accepts a city IATA code and a year and returns each month with a traveller count and a score, which is enough to surface 'best time to visit' insights or to plan capacity-aware marketing campaigns. Data is derived from anonymised historical traffic.

## For AI agents

Return the busiest travel months for a city based on historical air traffic. Agents call `/travel/analytics/air-traffic/busiest-period` to inform 'best time to visit' content.

## Scope

Does not return live flight prices, real-time bookings, or per-day traffic - use only for monthly busiest-period rankings for a destination city.

## Capabilities

- Return the busiest months of the year for a destination city by IATA code
- Rank months by passenger volume or by arrivals depending on the period parameter
- Surface seasonality patterns to inform travel content and SEO pages
- Compare year-over-year traffic by changing the year parameter on the same city
- Help marketing teams time campaigns around peak demand windows
- Feed seasonality into pricing or availability messaging on a destination page

## Use cases

### Best Time to Visit Content

Travel publishers and destination marketers can produce data-backed 'best time to visit' guides by calling `/travel/analytics/air-traffic/busiest-period` for the target city. The endpoint returns each month ranked by traffic, which is enough to write 'Madrid is busiest in August' with a real number rather than guesswork. The data refreshes per year so content can be regenerated annually.

Example prompt: Call `/travel/analytics/air-traffic/busiest-period` for cityCode=MAD, period=2025, and return the top three months by traveller volume.

### Marketing Campaign Timing

Aligning paid media to demand peaks improves conversion. By pulling the busiest period for each top destination, a marketing platform can schedule destination ads to run in the weeks leading up to peak months rather than spending evenly across the year. The single endpoint is cheap enough to run for hundreds of cities in a planning cycle.

Example prompt: For a list of top 50 destinations, return the peak month per city to feed the media planning calendar.

### Capacity Planning for Travel Operators

Tour operators and ground handlers planning supply for the year ahead need objective seasonality data. The busiest-period endpoint provides month-by-month volume for each destination, which is enough to staff guides, prebook hotel allotments, and schedule transfers in line with expected demand rather than relying on last year's gut feel.

Example prompt: Pull monthly traveller counts for cityCode=BCN for 2025 and feed them into a staffing model for 2026.

### Agent Travel Recommendations

An AI travel assistant asked 'when is Lisbon least crowded?' can call the busiest-period endpoint and invert the ranking to surface quieter months. Through Jentic the agent searches for 'find the busiest travel months for a city', loads the schema, executes the call, and writes a natural-language recommendation referencing the actual numbers.

Example prompt: Use Jentic to call the busiest-period operation for LIS in 2025 and return the three least-crowded months in plain English.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/travel/analytics/air-traffic/busiest-period` | Return busiest months for a city by traffic |

## Key resources

- **Busiest Traveling Period** — GET monthly traffic ranking for a city in a given year.

## Why Jentic

- **Setup:** Wiring the Flight Busiest Traveling Period API by hand means handling the Amadeus OAuth 2.0 client_credentials exchange, refreshing the bearer token, and parsing the monthly ranking response from GET `/travel/analytics/air-traffic/busiest-period` against the correct Amadeus host and version. Through Jentic you install once, import Flight Busiest Traveling Period from the API Directory, store the Amadeus client credentials once, and your agent calls it.
- **Permission scoping:** The destination city code and direction 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 busiest travel months for 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 performs 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 'find the busiest travel months for Madrid', and Jentic returns the `/travel/analytics/air-traffic/busiest-period` operation with its input schema so the agent supplies the city code and period without scanning the Amadeus docs.

## Related APIs

- **Amadeus Flight Most Traveled Destinations** — Returns the top destinations from a given origin rather than seasonality of arrivals.
- **Amadeus Flight Most Booked Destinations** — Ranks destinations by booking volume from a given city.
- **Amadeus Flight Cheapest Date Search** — Finds the cheapest dates which can then be cross-referenced against busiest months.

## FAQ

### What authentication does the Flight Busiest Traveling Period API use?

The API uses the Amadeus OAuth 2.0 client-credentials flow. Exchange API key and secret at the Amadeus token endpoint and send the bearer token on `/travel/analytics/air-traffic/busiest-period` calls. Jentic keeps the credentials in the encrypted vault and refreshes tokens automatically.

### What does the period parameter control?

The period parameter selects which year of historical traffic the response is based on, while a separate parameter switches between ranking by total travellers and ranking by arrivals. Pick the metric that matches the question - total travellers for marketing demand, arrivals for inbound capacity planning.

### What are the rate limits for the Flight Busiest Traveling Period API?

Rate limits are not declared in the OpenAPI spec and depend on the Amadeus contract tier. The endpoint is read-only and cacheable per city and year, so cache results aggressively to stay under the per-second cap when running across hundreds of destinations.

### How do I find peak months through Jentic?

Run pip install jentic, then use the search query 'find the busiest travel months for a city'. Jentic returns the `/travel/analytics/air-traffic/busiest-period` operation, you load the schema, supply cityCode and period, and execute. The ranked monthly response can drive a content page directly.

### Does the response cover every city in the world?

Coverage is best for major commercial-airport cities and may be sparse for smaller destinations. The test environment carries only a subset of production data, so confirm the city you need is supported in production before building a feature around it.

### Is the Flight Busiest Traveling Period API free?

Amadeus self-service APIs include a free test environment with quota limits and a paid production tier. Production access is contracted with Amadeus and pricing scales with transaction volume - confirm current rates in the developer portal.

### Can I limit what my agent is allowed to do with the Flight Busiest Traveling Period API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The city code and direction here travel as query parameters rather than as a path resource, so access is scoped per operation: you grant the agent only the busiest-period read on GET `/travel/analytics/air-traffic/busiest-period.` It cannot reach other Amadeus analytics or booking operations unless you explicitly add them.