Flight Offers Search

Name: Flight Offers Search API
Brand: Flight Offers Search
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceShipping Logisticsoauth22 EndpointsREST

For Agents

Search for bookable flight offers between airports on specific dates and retrieve pricing, segments, and fare rules. Returns offer IDs that can be passed to downstream pricing or order-creation flows.

Connect the Flight Offers Search to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flight Offers Search, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 Offers Search API.

Search one-way and round-trip flight offers by IATA origin, destination, and travel dates

Filter offers by cabin class, included airline codes, max connections, and non-stop preference

Retrieve detailed segment data including operating carrier, aircraft type, and layover duration

Return pricing breakdowns with base fare, taxes, and total per traveler type

GET STARTED

Start building with Flight Offers Search API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Flight Offers Search, keeping it validated and agent-ready.

Flight Offers Search returns a list of bookable flight offers based on origin, destination, dates, and traveler details. The API exposes both a GET endpoint for simple itinerary lookups and a POST endpoint that accepts richer search criteria including connection limits, cabin restrictions, and fare-class preferences. Results include detailed pricing, segment information, baggage allowances, and fare rules so an agent can present options or hand the offer ID to a separate booking flow. The test environment runs against a static subset of GDS inventory; production keys must be requested from Amadeus before live results are available.

Use Cases

Patterns agents use Flight Offers Search API for, with concrete tasks.

★ Travel agent itinerary lookup

Travel concierge agents query the Flight Offers Search endpoint to surface bookable itineraries that match a traveler's requested origin, destination, dates, and cabin preferences. The API returns priced offers including segment timings, carriers, and baggage rules so the agent can summarise top options for the user. Each offer includes an opaque offer ID that downstream Amadeus pricing and booking endpoints accept directly.

Call POST /shopping/flight-offers with originLocationCode JFK, destinationLocationCode CDG, departureDate 2026-09-15, returnDate 2026-09-22, adults 2, currencyCode USD, max 5 and return the three cheapest offers.

Price comparison and fare alerts

Monitoring agents poll Flight Offers Search on a schedule for a fixed origin-destination pair to detect price drops or availability changes. The API supports filtering by airline codes, max connections, and non-stop only, keeping result sets small enough to fit inside an agent's context window. Comparing successive payloads makes it possible to trigger notifications when a fare crosses a threshold.

Run GET /shopping/flight-offers daily for origin LAX, destination JFK, departureDate next Friday, adults 1, nonStop true, and emit an alert when totalPrice drops below 250.

Multi-city corporate trip planning

Travel-management agents construct multi-leg itineraries on behalf of business travelers using the POST endpoint, which accepts an originDestinations array describing each leg's airports and date windows. The response groups segments per leg with full pricing and fare conditions, so the agent can present a single combined offer for approval. This avoids stitching together three separate searches and risking mismatched availability.

POST /shopping/flight-offers with three originDestinations (NYC->LHR, LHR->FRA, FRA->NYC) across consecutive weeks, travelers list of one ADULT, and return the cheapest combined offer.

AI agent flight search via Jentic

An AI agent using Jentic discovers Flight Offers Search through a natural-language query like 'search for flight offers'. Jentic returns the operation schema with required parameters, the agent fills them from user intent, and Jentic executes the call against Amadeus with the OAuth2 token stored in the credential vault. The agent never handles the client secret directly and gets a structured response it can summarise back to the user in seconds.

Use Jentic to search 'flight offers between two airports', load the operation schema, and execute a search for ATL to SEA on 2026-10-01 for 1 adult, max 3 results.

Key Endpoints

2 endpoints — flight offers search returns a list of bookable flight offers based on origin, destination, dates, and traveler details.

METHOD

PATH

DESCRIPTION

GET

/shopping/flight-offers

Search flight offers via query parameters

POST

/shopping/flight-offers

Search flight offers with structured body for complex itineraries

GET

/shopping/flight-offers

Search flight offers via query parameters

POST

/shopping/flight-offers

Search flight offers with structured body for complex itineraries

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 MAXsystem vault. Jentic exchanges them for short-lived OAuth2 access tokens at execute time so agents never see the long-lived secret in their context.

Intent-based discovery

Agents search 'search for flight offers' and Jentic returns both operations on /shopping/flight-offers with their input schemas, so the agent picks GET for simple lookups or POST for multi-leg searches without browsing Amadeus docs.

Time to first call

Direct Amadeus integration: 1-3 days for OAuth2 token handling, sandbox onboarding, and parameter mapping. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amadeus Flight Offers Price

Confirms the final price and seat availability for an offer returned by Flight Offers Search before booking.

Use right after Flight Offers Search to reprice the chosen offer ID before creating a booking — guards against stale fares.

Complementary

Amadeus Flight Create Orders

Creates a confirmed PNR booking from a priced flight offer.

Choose this once the user confirms an offer — completes the search-price-book sequence with traveler details and payment.

Alternative

Amadeus Flight Cheapest Date Search

Finds the cheapest dates for a route within a window instead of returning bookable offers.

Pick this when the user is flexible on dates and wants a price calendar instead of specific itineraries.

FAQs

Specific to using Flight Offers Search API through Jentic.

What authentication does the Flight Offers Search API use?

The API requires OAuth2 client-credentials tokens issued by Amadeus. Through Jentic, the client_id and client_secret are stored encrypted in the MAXsystem vault and an access token is fetched per call — your agent only sees a scoped bearer token, never the long-lived secret.

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

Yes. Use POST /shopping/flight-offers with an originDestinations array containing one entry per leg, each with originLocationCode, destinationLocationCode, and a departureDateTimeRange. The response returns combined offers spanning all legs with unified pricing.

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

Amadeus enforces tier-based limits: the free Self-Service test environment allows 10 transactions per second and a monthly cap, while production access (granted on request) raises both. Jentic surfaces 429 responses unchanged so retry logic can back off.

How do I run a flight search through Jentic?

Run pip install jentic and authenticate with your ak_* key, then search 'search for flight offers' to load the GET /shopping/flight-offers operation schema. Provide originLocationCode, destinationLocationCode, departureDate, and adults, then call execute — Jentic handles OAuth token exchange behind the scenes.

Does this API book or pay for flights?

No. Flight Offers Search only returns priced offer objects. To book, you pass the offer ID to Amadeus Flight Create Orders and handle payment separately — that endpoint is a different API in the Amadeus catalogue.

Is the test environment usable for production traffic?

No. The test environment hosts a static subset of GDS inventory and is intended for development only. Real bookable inventory requires production credentials and a switch to the production base URL, which Amadeus provisions after a review.