Amadeus Flight Offers Search

What authentication does the Flight Offers Search API use?

Amadeus uses OAuth 2.0 with the client_credentials grant. You exchange your Amadeus client_id and client_secret for an access token at the Amadeus token endpoint /v1/security/oauth2/token, sending grant_type=client_credentials in a form-encoded body, then send the token as Authorization: Bearer on each /shopping/flight-offers request. Amadeus's authorization guide shows the token response carrying expires_in of 1799 seconds. Note that this specification declares no securityScheme of its own; Amadeus documents the OAuth 2.0 flow in a separate Authorization specification and in its developer guides. Through Jentic, your client id and secret are stored encrypted by your own Jentic One instance and injected at execution time.

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?

Amadeus publishes its limits per environment in the API Rate Limits developer guide at amadeus4dev.github.io/developer-guides/api-rate-limits/. Flight Offers Search falls under the general Self-Service bucket, not the artificial-intelligence and partner bucket, so the guide states 10 transactions per second per user in the test environment and 40 transactions per second per user in production, with no more than 1 request every 100ms. That guide states no monthly transaction cap. Treat 429 responses as a signal to back off and retry with a delay.

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

Install Jentic One using the one-line installer from its GitHub repo, run jentic register on your agent machine, then import Flight Offers Search from the API Directory and store your Amadeus client id and secret once. Your agent then searches Jentic for search flight offers, loads the operation schema, and executes either the GET or POST flight-offers operation with the user's travel parameters. Keep the agent on a separate machine from the instance, as the hardening guide describes.

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.