A complete booking engine with Amadeus solves this by giving your platform the ability to search, compare, and book all four products in a single flow, connected to the same inventory infrastructure, managed through the same agent dashboard, and presented under your own brand.
The case for building a multi-product travel booking engine is fundamentally a revenue argument. When a customer books a two-week holiday, the total transaction value across flights, accommodation, ground transport, and a cruise or tour activity can be three to five times the value of the flight ticket alone. An agency that captures only the flight component captures only a fraction of the revenue available from that customer interaction.
There is also a retention argument. A customer who books their entire trip through your portal has stronger brand loyalty than a customer who booked only their flights with you and handled everything else elsewhere. The more of the trip you own, the harder it is for the customer to see a reason to look at a competitor next time.
And there is an operational argument. Managing four separate supplier relationships, commission structures, and booking workflows is significantly more complex than managing a single integrated platform that handles all four through a single API layer. Amadeus provides a single API layer across flights, hotels, car rentals, and cruises, which makes a properly built multi-product platform operationally viable rather than just theoretically desirable.
Before getting into the architecture and build process, it is worth being specific about what the Amadeus API catalog actually covers across each product. The depth of content available through Amadeus is one of the main reasons it works as the single integration layer for a complete booking engine rather than requiring separate supplier connections for each product.
Product | Amadeus Content Coverage | Key APIs | Inventory Scale |
|---|---|---|---|
Flights | 400+ airlines, including 130+ LCCs, full-service carriers across 190 markets, and NDC content from 35 airlines | Flight Offers Search, Flight Offers Price, Flight Create Orders, SeatMaps, On-Demand Flight Status, Check-In Links | Covers approximately 82% of global scheduled airline capacity |
Hotels | 150,000+ accommodation suppliers, 500,000+ properties, Amadeus Value Hotels net rate program, alternative accommodations | Hotel List API, Hotel Search API, Hotel Offers API, Hotel Orders API, Hotel Ratings API | Properties across all major destinations with commission and pre-paid net rate options |
Car Rentals | 75 mobility providers, 42,000+ rental locations across 1,800+ cities, major global brands, and regional operators | Car Rental Search API, Car Rental Booking API | Coverage across every major airport and city destination globally |
Cruises | Major global cruise lines, real-time inventory and pricing, cabin categories, and departure ports | Cruise Boarding API, Cruise Offers API (via Enterprise) | Access to major lines, including Royal Caribbean, Carnival, Norwegian, MSC, and others |
Transfers | Airport transfer providers, private car services, shuttle bookings | Transfer Search API, Transfer Orders API | Coverage across major airports and city pairs globally |
Tours and Activities | 101+ tour operators, destination experiences, attractions, and activities | Tours and Activities API | 200,000+ experiences across global destinations |
The breadth of this coverage is what makes Amadeus the practical foundation for a complete booking engine. A single integration with Amadeus through its GDS integration framework gives your platform access to all of the above product categories without requiring separate supplier negotiations and integrations for each one. That said, the technical complexity of building the booking flows for each product is different, and understanding those differences is important when scoping the project.
Flight booking is where the most agents and most travel technology developers have the most experience, so it makes sense to start here. The Amadeus flight layer is also the most mature and most thoroughly documented part of the API catalog, which makes it the natural starting point for any multi-product build.
The Flight Offers Search API returns live availability, routing options, and fares from over 400 airlines for any origin-destination pair and travel date combination. Results include branded fare families where the airline publishes them, showing Economy Flex versus Economy Saver options rather than just a bare fare. The Flight Offers Price API confirms the exact price of a selected offer before the customer commits, handling the fare verification step that every production booking engine needs to get right.
For platforms that need content beyond what is available through the traditional GDS channel, the AQC flight API integration extends the Amadeus layer to include LCC content and direct airline feeds that sit outside the standard GDS distribution channel.
The Flight Create Orders API handles PNR creation for confirmed bookings. From there, PNR management covers modifications, cancellations, and ancillary additions. The SeatMaps API enables an interactive seat selection step within the booking flow. The Check-In Links API provides direct links to airline online check-in pages, giving customers a cleaner post-booking experience within your platform rather than sending them to airline websites to find the check-in page themselves.
Amadeus is currently the only GDS offering NDC content from 35 airline partners across 165 countries. For airlines that now distribute their best fares and ancillary offers exclusively or preferentially through NDC rather than through the traditional EDIFACT GDS channel, the Amadeus NDC integration means your booking engine shows those fares within the standard search results rather than missing them entirely. This is particularly relevant for Lufthansa Group, Air France-KLM, and American Airlines, all of which have significant NDC-only content.
Adding hotel search and booking to a flight-only portal is the most commercially significant step in building a complete booking engine. Hotel margin structures are typically more favorable than flight commissions, and the ability to offer a customer a complete flight-plus-hotel package at the point of booking significantly increases average order value.
The Amadeus Hotel List API returns hotels near a destination based on geographic coordinates, airport code, or city name, giving your search interface the autocomplete and mapping capability customers expect. The Hotel Search API returns real-time availability and pricing for a given destination and date range. Results include room types, rate plans, cancellation policies, and property details.
The Amadeus Value Hotels program gives travel agencies access to pre-paid net rate inventory across 400,000-plus properties. Net rate inventory means the agency buys at a wholesale price and marks up to a retail price, retaining the margin directly rather than earning a commission. For agencies with the volume to make pre-paid inventory work, this is typically the most profitable way to sell hotel accommodation through the Amadeus platform.
The Hotel Ratings API provides sentiment scores and category ratings derived from guest reviews, giving your platform the ability to surface quality indicators alongside pricing without needing to scrape third-party review sites. This matters for conversion because customers making accommodation decisions without quality signals tend to abandon booking flows at higher rates than those who can see property ratings alongside the fare.
The most effective way to present flight-plus-hotel to customers in a complete booking engine is a combined search flow where the customer enters their origin, destination, travel dates, and number of guests in one search form, and the results page shows both flight and hotel options in the same view. The customer selects their preferred flight, and the hotel results automatically adjust to the destination and dates of the selected flight. This connected flow converts significantly better than presenting flight and hotel searches as separate tabs or separate pages. Flight Terminus builds this connected flow into every B2C flight booking portal and custom B2B flight booking solution that includes hotel content.
Car rental is the most straightforward of the four product categories to add to a complete booking engine in terms of API complexity, and it is often the product that agents underestimate as a revenue opportunity. A customer flying into a destination without pre-arranged ground transport is a warm prospect for a car rental booking the moment they land, and capturing that booking at the same time as the flight and hotel removes the customer's need to go to a rental platform later.
The Amadeus Car Rental Search API connects to 75 mobility providers across 42,000-plus locations in over 1,800 cities worldwide. The search returns real-time availability, vehicle categories, pricing, and rental terms for a given pickup location, pickup date and time, and dropoff date and time. Coverage spans major global brands alongside regional operators and specialty rental providers.
The car rental search interface in your booking engine should pre-populate the pickup location with the arrival airport from the customer's selected flight. The customer should not need to re-enter their destination after selecting a flight. Similarly, the pickup date and time should default to the flight arrival date and a reasonable post-arrival time, with the customer able to adjust these if needed. This friction reduction at the car rental search step significantly increases the rate at which customers who complete a flight booking go on to add a car rental.
The car rental booking flow is also where insurance, GPS navigation, child seat, and additional driver add-ons are presented. These ancillary products generate margin without adding operational complexity and should be part of the car rental booking flow in any complete booking engine build.
Cruise is the highest average-order-value product in the complete booking engine stack, and it is the product most agents associate with specialist knowledge and specialist platforms. That association is understandable historically, but the Amadeus cruise booking capability has matured enough to make it viable as an integrated component of a general travel booking engine rather than a standalone specialist system.
The Amadeus cruise booking layer provides access to major global cruise lines, including Royal Caribbean, Carnival, Norwegian, MSC, and others, through the Enterprise API tier. The API returns real-time cabin availability across ship categories, departure ports, itineraries, and sailing dates. Pricing is returned at the cabin category level with details of what each category includes in terms of meals, beverages, and on-board amenities.
Cruise booking has a longer decision cycle than flights, hotels, or car rentals. Customers comparing cruise options spend more time on the results page, want more content about the ship, the itinerary ports, and the cabin categories before converting. Your cruise booking interface needs to support richer product content display than the flight or hotel results pages do. Itinerary maps, ship deck plans, cabin images, and included amenity lists are all content that drives cruise conversion rates and should be part of the build specification.
Some agencies will want to use the cruise module as a standalone product where customers search by departure port and sailing date without a flight attached. Others will want to offer a cruise as part of a fly-cruise package where the customer books a flight to the embarkation port alongside the cruise booking. Both flows are supported within a properly built, complete booking engine, and the choice between them shapes how the cruise search interface is presented within the broader portal. For agencies that want to build a dedicated cruise-focused portal, Flight Terminus's travel aggregator portal development service covers this as a standalone deployment alongside the multi-product complete booking engine option.
Understanding the technical architecture of a complete booking engine helps agencies make informed decisions during the planning phase and communicate clearly with the development team. Here is how the components fit together across all four product categories.
Amadeus provides one authentication layer for all product APIs. A single OAuth 2.0 token generated from your Amadeus API credentials is used to make calls across the flight, hotel, car rental, and cruise endpoints. This single-credential architecture is one of the practical advantages of building a complete booking engine on Amadeus rather than stitching together four different supplier APIs with four different authentication systems.
The search engine layer handles all product-specific search queries, formats them for the relevant Amadeus API endpoints, and processes the responses. Each product has its own search query structure and its own response format. The search engine normalises these into a consistent internal data schema that the front-end can work with, regardless of which product the customer is searching for.
Each product generates its own booking record when a customer completes a purchase. A flight booking generates a PNR through the Amadeus Flight Create Orders API. A hotel booking generates a hotel order through the Hotel Orders API. A car rental booking generates a reservation through the Car Rental Booking API. The booking management layer maintains a unified view of all active bookings across all products, so an agent can see a customer's complete trip at a glance rather than searching four separate systems.
The admin and agent layer sits above the booking engine and handles markup configuration per product, commission tracking, PNR management, cancellation workflows, and team performance reporting. For B2B platforms, this layer also manages sub-agent access, credit limits, and the ability to set different markup rules for different agent tiers. Flight Terminus builds this admin layer as a standard component of every custom B2B flight booking solution and can extend it to cover all four products in a complete booking engine build.
A complete booking engine needs a payment layer that handles different transaction types per product. Flights can be paid for immediately and ticketed. Hotels may require either immediate payment or a credit card guarantee, depending on the rate plan. Car rentals often use a credit card hold rather than an immediate charge. Cruises frequently involve a deposit with the balance due closer to sailing. The payment layer needs to handle all of these scenarios within a single checkout experience that does not confuse the customer with product-specific payment rules.
How you deploy a complete booking engine depends on who your customers are and how you operate. The same Amadeus API stack underlies all of the deployment models below, but the front-end experience, the pricing configuration, and the agent access structure differ significantly between them.
Deployment Model | Customer Type | Key Features | Best For |
|---|---|---|---|
B2C Consumer Portal | End travelers booking directly | Public-facing search, self-service booking, payment gateway, and booking management | Agencies moving toward direct consumer sales alongside or instead of agent-mediated bookings |
B2B Agent Portal | Travel agents booking on behalf of clients | Agent login, client management, markup configuration, commission tracking, PNR dashboard | Agencies with a sub-agent network or corporate accounts that book through an agent interface |
White Label Portal | Any downstream partner | Fully branded per partner, same inventory, separate markup configuration per partner | Agencies that supply inventory to sub-agents, DMCs, or corporate clients who want their own branded booking tool |
B2B2C Combined | Both agents and end consumers | Agent access and consumer access from the same platform, with different views and pricing | Agencies that serve both business and consumer segments from one platform |
Corporate Travel Tool | Employees of a corporate client | Policy enforcement, approval workflows, corporate rate access, and expense integration | Agencies that manage corporate travel accounts and need a booking tool branded for each corporate client |
For agencies considering the white-label option, Flight Terminus's white label flight booking portal framework supports all four product categories and can be extended to a complete multi-product white-label engine. For agencies considering the B2C option, the B2C flight booking portal framework provides the consumer-facing search and booking experience that this deployment model requires.
Flight Terminus specialises in building custom travel technology platforms on Amadeus. Our complete booking engine service covers all four product categories: flights, hotels, car rentals, and cruises, connected to the Amadeus API layer and delivered with the front-end experience, agent management tools, and payment integration your platform needs to operate commercially from day one.
Every project starts with a discovery session where we map your product scope, your markets, your agent or consumer audience, and your commercial requirements. To start that conversation, contact the Flight Terminus team at flightterminus.com/contact-us.
The timeline for building a complete booking engine depends on the product scope and the complexity of the front-end and agent management requirements. The table below provides orientation ranges based on the Flight Terminus project experience.
Scope | Products Covered | Estimated Timeline | Key Deliverables |
|---|---|---|---|
Flight-only portal | Flights | 10 to 14 weeks | Flight search, pricing, booking, ticketing, seat maps, PNR management, payment |
Flights and hotels | Flights and Hotels | 14 to 18 weeks | All flight deliverables, plus hotel search, availability, booking, and net rate access |
Flights, hotels, and cars | Flights, Hotels, Car Rental | 18 to 22 weeks | All above, plus car rental search and booking with connected pickup from the flight |
Complete booking engine | Flights, Hotels, Car Rental, Cruises | 22 to 28 weeks | All above, plus cruise search, availability, cabin category booking, and deposit handling |
Complete with B2B agent layer | All four products plus B2B tools | 26 to 32 weeks | All above plus agent dashboard, markup config, sub-agent management, commission tracking |
The product coverage, API capability, and architectural guidance in this blog come from direct experience building and maintaining Amadeus-integrated travel platforms for agencies, OTAs, and aggregators across multiple markets. The specific API behaviors described, the content coverage figures cited, and the timeline ranges provided reflect real production builds rather than documentation summaries.
Amadeus's product suite continues to develop. New API endpoints are added, existing ones are updated, and content coverage evolves as new supplier partnerships are established. For the most current information on specific API availability and content coverage, visit amadeus.com/en/airlines/products/all. For questions specific to your booking engine project, the Flight Terminus team can provide a current assessment based on your scope and markets.
Frequently Asked Questions
Yes. Amadeus provides API coverage across all four product categories through its self-service and enterprise API tiers. Flights are covered through the standard self-service APIs available to any registered developer. Hotels, car rentals, and cruises are available through a combination of self-service and enterprise API endpoints, depending on the depth of content and the booking capabilities required. Cruise booking in particular requires the Amadeus Enterprise API tier rather than the self-service catalog. Flight Terminus's Amadeus GDS integration service covers all four product tiers and handles the API access level appropriate for each.
Either approach is possible, and both are standard in a well-built, complete booking engine. A customer can arrive on the platform and search only for flights, completing a flight-only booking without touching the hotel or car rental modules. Alternatively, the platform can present hotel options immediately after a flight is selected, with car rental added in the next step, and cruise presented as an optional addition for relevant itineraries. How aggressively the cross-sell flow is presented is a configuration decision that the agency controls through the admin dashboard.
Amadeus Self-Service APIs are available to any developer through a free registration and provide access to flight search, pricing, booking, hotel search, hotel booking, tours and activities, and several other endpoints. They are the right starting point for most agencies and OTAs building multi-product portals. Amadeus Enterprise APIs provide additional content depth, including car rental booking, cruise booking, LCC content, NDC access, and higher transaction volumes with dedicated support and contracted SLAs. Most complete booking engine builds that include all four products will need a combination of both API tiers, with the enterprise relationship typically arranged through a certified Amadeus partner like Flight Terminus.
Yes, and this is a sensible approach for many agencies. Starting with flights and then adding hotels is the most common progression. The key requirement is that the initial build is architected with extensibility in mind so that adding a new product category later does not require rebuilding the core booking engine. Flight Terminus designs every multi-product platform with product extensibility as a core architectural requirement, meaning the hotel module can be added after the flight module is live without rebuilding the search engine, payment layer, or agent dashboard.
Each product category can have independent markup rules configured in the admin layer. A flight booking might carry a flat service fee, a hotel booking might carry a percentage markup on the net rate, a car rental might apply a fixed per-day markup, and a cruise might carry a percentage commission on the full booking value. The markup engine in the admin dashboard handles these rules independently per product, per carrier or supplier, per market, or per agent tier, depending on how granular you need the pricing control to be.
Each product has its own modification and cancellation rules governed by the supplier's terms. A flight modification goes through the Amadeus flight PNR management API. A hotel cancellation goes through the hotel's cancellation endpoint. A car rental cancellation goes through the car rental reservation API. The booking management dashboard in the agent layer shows all active bookings across all products and provides the relevant action options for each, so the agent does not need to know which API handles each product's changes.
Group bookings for flights, hotels, and car rentals are supported within the Amadeus API framework, with multi-passenger PNR creation for flights and multi-room or multi-vehicle bookings for accommodation and cars. Cruise group bookings at larger scales typically require the cruise operator's own group booking process rather than purely API-based booking. Flight Terminus can incorporate group booking workflows into the platform design as part of the project scope discussion.
The starting point is a discovery call with the Flight Terminus team. We review your current technology setup, the product categories you want to include, your target customer audience, and your commercial requirements. From that conversation, we produce a project architecture recommendation, product scope outline, and timeline estimate. You can book the discovery call at flightterminus.com/contact-us.