Amadeus APIs

31 APIs42 Endpoints5 Categories

API Catalog(12 of 31)

Branded Fares Upsell

The Amadeus Branded Fares Upsell API takes a flight offer and returns the carrier's branded fare families for that itinerary, complete with included services such as bags, seat selection, and refundability. The single POST to /shopping/flight-offers/upselling sends an existing flight offer payload back to Amadeus and gets matching upsell options, so booking flows can present 'Economy Light' through 'Business Flex' tiers side by side. It targets airline.com replacement experiences and corporate booking tools that need branded merchandising rather than a single base fare.

1 endpoints

Flight Availabilities Search

The Amadeus Flight Availabilities Search API returns seat availability per booking class for one or more origin-destination pairs and dates. The single POST to /shopping/availability/flight-availabilities is closer to a GDS availability call than to a fare search — it gives the number of bookable seats per Reservation Booking Designator on each flight segment, which is what travel agencies and OTAs need to construct multi-segment tickets without overselling. Use this when a fare-only search is not enough and you need raw availability per cabin class.

1 endpoints

Flight Cheapest Date Search

The Amadeus Flight Cheapest Date Search API returns the cheapest available dates to fly between two cities, ranked by total fare. The single GET endpoint at /shopping/flight-dates accepts an origin, destination, and a flexible date range and returns price points keyed by date pair, which is what powers 'when is it cheapest?' calendar widgets and flexible-date search experiences. It is intended for inspirational and flexible-date searches rather than precise booking flows.

1 endpoints

Flight Create Orders

The Amadeus Flight Create Orders API turns a priced flight offer into a confirmed booking with a Passenger Name Record. The single POST endpoint takes a flight offer (already validated by Flight Offers Price), traveller details, and contact information, and returns an order id, ticketing status, and the underlying PNR reference. It is the final step in the Self-Service flight-shopping flow before payment is captured downstream by the integrator.

1 endpoints

Flight Inspiration Search

The Amadeus Flight Inspiration Search API answers the question 'where can I fly from here for cheap?' Given an origin IATA code, it returns the cheapest destinations Amadeus has cached for that origin within an optional date range, max price, duration, and one-way or round-trip filter. Each entry includes a sample price, sample dates, and a link to a follow-up Flight Offers Search call. Travel sites use it to power 'cheap flights from London' homepage modules without running an exhaustive search at request time.

1 endpoints

Flight Offers Price

The Amadeus Flight Offers Price API reconfirms the live price, taxes, and fare conditions of one or more flight offers returned by Flight Offers Search. The single POST endpoint takes a flight-offers payload and returns a verified price block with detailed fare components, baggage allowances, fare rules, and any availability changes since the original search. Booking flows call it as the gate between search and order creation, since search results are cached and may drift before checkout.

1 endpoints

Flight Offers Search

Jentic publishes the only available OpenAPI specification for Flight Offers Search, keeping it validated and agent-ready. The Amadeus Flight Offers Search API returns priced flight itineraries from over 500 airlines on demand. It supports both a GET endpoint for simple round-trip queries and a POST endpoint for complex multi-city, multi-passenger searches with cabin class, fare type, and connection constraints. Travel platforms, online travel agencies, and corporate booking tools use it to power live flight search experiences with real availability and fares.

2 endpoints

Flight Order Management

The Amadeus Flight Order Management API retrieves and cancels flight orders previously created via Flight Create Orders. The two endpoints — GET and DELETE on /booking/flight-orders/{flight-orderId} — let an integrator pull the full order state including travellers, segments, ticketing status, and PNR reference, or cancel the order within the airline's void window. It is the post-booking servicing layer of the Amadeus Self-Service flight stack.

2 endpoints

Hotel Booking

The Amadeus Hotel Booking API turns a confirmed hotel offer into a real reservation with the underlying hotel provider. The single POST endpoint takes an offer id from Hotel Search, traveller and guest details, plus payment information, and returns one or more booking ids and provider confirmation numbers. It is the final step in the Self-Service hotel flow and submits real reservations against live hotel inventory, so test bookings should never run against the production environment.

1 endpoints

Hotel Search API

The Amadeus Hotel Search API returns live hotel offers — rates, room types, board options, cancellation policies — for a list of Amadeus hotelIds and a stay window. It powers the price-and-availability step of a hotel booking funnel: take a shortlist of hotels and produce concrete, bookable offers with offerIds that can be confirmed downstream by the Hotel Booking API. Two endpoints cover the flow: a list call that returns offers across many hotels at once, and a detail call that re-prices a single offer before booking.

2 endpoints

Seatmap Display

The Amadeus Seatmap Display API returns the cabin layout and per-seat metadata for a flight, enabling the seat-selection step of a booking flow. Two endpoints cover the common patterns: a GET keyed on a confirmed flight order id, and a POST that accepts an in-progress flight offer and returns the seat map before the booking is committed. Each seat in the response includes coordinates, characteristics (window, aisle, exit row, extra legroom), availability, and applicable price.

2 endpoints

Tours and Activities

The Amadeus Tours and Activities API returns bookable experiences — guided tours, attraction tickets, day trips — around a geographic location. Three endpoints cover the access patterns: a radius search around a coordinate, a bounding-box search across a rectangular area, and a detail lookup by activity id. Each result includes pricing, ratings, an image, and a booking URL, making it suitable for itinerary apps and travel concierge agents that want to surface concrete things to book at a destination.

3 endpoints

Connect Your Agent

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.