Amadeus Flight Offers Search

What authentication does the Flight Offers Search API use?

The API uses OAuth 2.0 client-credentials. You exchange an Amadeus client_id and client_secret for a short-lived bearer token at the Amadeus auth endpoint, then send it as Authorization: Bearer on each /shopping/flight-offers request. Through Jentic, the client_id and client_secret are stored encrypted in the vault and the token exchange is performed server side.

Can I search multi-city itineraries with the Flight Offers Search API?

Yes. Use POST /shopping/flight-offers with a structured request body containing multiple originDestinations entries. Each entry has its own origin, destination, and date, which lets you build itineraries with three or more legs in a single call. The GET endpoint only supports round-trip and one-way.

What are the rate limits for the Flight Offers Search API?

The Amadeus Self-Service test environment limits Flight Offers Search to 10 transactions per second per application, with monthly transaction caps depending on your tier. Production limits are negotiated per Amadeus contract. Treat 429 responses as a signal to back off and retry with exponential delay.

How do I search flights with the Flight Offers Search API through Jentic?

Install the SDK with pip install jentic, then search Jentic for search flight offers, load the operation schema, and execute either the GET or POST flight-offers operation with the user's travel parameters. Jentic handles OAuth token exchange and refresh, so the agent only deals with the search request and response.

Are the prices returned by the Flight Offers Search API guaranteed?

No. Prices reflect real-time airline inventory at the moment of the search and can change before booking. To confirm a price, call the Flight Offers Price endpoint with the selected offer before proceeding to booking; only the price returned by that confirmation step is bookable.

Can I limit what my agent is allowed to do with the Flight Offers Search API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you can grant only the GET /shopping/flight-offers search for simple round-trip queries, only the POST /shopping/flight-offers search for multi-city itineraries, or both. Neither operation books, tickets, or services a reservation, so those actions stay out of the agent's reach entirely. Your Amadeus client id and secret are held by your own instance and injected only at execution time, never exposed to the agent's prompt or context.