A dynamic packaging API lets a travel platform build a trip at the moment of search — a flight and a hotel, often with a transfer or an activity — and sell it at one combined price. Tripgic sells the parts such a package is made of — flights, hotels, transfers and activities — through one API and one JSON format, so a platform can build its own packages on a single integration.

This guide explains what dynamic packaging is, how a package is searched, priced and booked, where it gets hard, which rules apply, and how to build it — whether you buy a ready-made packaging service or assemble it on separate travel APIs.

What Is a Dynamic Package?

A dynamic package is a trip assembled per search from live components and sold as one product at one price. The traveller picks a destination, dates and number of people; the platform finds flights and hotels that fit, combines them, and shows one price for the whole trip.

The word dynamic is the contrast with the older model:

Fixed package Dynamic package
When it is built In advance, by a product team At the moment of search
Dates and length Set departures, often 7 or 14 nights Any dates the traveller chooses
Inventory Often pre-bought seats and rooms (allotments) Live availability from suppliers
Price Set in a brochure or rate table Calculated live from current component prices
Choice A short list of hotels and flights Every hotel and flight available
Risk Unsold allotments cost money Little stock risk; price risk at booking

Many companies run both. A tour operator may sell fixed tours with guides and coaches, and dynamic flight-plus-hotel trips for travellers who want their own dates.

What a Dynamic Packaging API Does

There is no single standard for a “dynamic packaging API”. In practice the term covers the calls a platform needs to do five jobs:

  1. Search each component — flights, hotels and any extras — for the traveller’s dates and party.
  2. Combine the results into valid trips: the hotel nights must match the flight dates, the hotel must be in the right city, the room must fit the party.
  3. Price the package as one, adding the platform’s margin and any package-only rates.
  4. Re-check every component’s price and availability before payment.
  5. Book every part, store the references together, and handle changes and cancellations afterwards.

Some providers sell all five as one service. Many platforms buy the components — a flight booking API, a hotel API, transfers and activities — and build the combining and pricing themselves, because that is where their own product and margin live.

Dynamic packaging API flow: search, fan out to flights hotels cars, combine, price as one, book together

Why Travel Businesses Sell Packages

Higher value per booking

A flight-plus-hotel booking is worth more than either part alone, and the cost of acquiring the customer is paid once. Adding a transfer or an activity raises it again at little extra cost.

One price for the whole trip

When the traveller sees one total, the platform can set its margin on the trip rather than on each item. A thin margin on a competitive flight can be balanced by a better one on the hotel, and the traveller compares one number, not five.

Package-only rates

Some hotels and airlines offer rates that may only be sold as part of a package, where the component price must not be shown on its own. These rates exist so that suppliers can sell more cheaply without undercutting their own public prices. Dynamic packaging is how a platform uses them: the rate is hidden inside the package total.

A simpler experience

The traveller searches once, pays once and gets one confirmation. For many leisure trips that is the main reason to choose a package over booking each part separately.

Stronger loyalty

A traveller whose whole trip was handled well — flight, hotel and transfer — has more reasons to return than one who bought a single flight.

Flight, hotel, and car combined into one package shown at a single price

The Components of a Package

Component Role in the package What makes it hard
Flight Sets the dates and the destination Fares change fast; baggage and fare rules vary
Hotel The largest share of the value in many trips Same hotel from several suppliers; room types differ
Transfer Airport to hotel and back Must match flight times and hotel address
Activities and tours Raise value and make the trip memorable Dates, times and capacity per day
Car rental Replaces transfers for road trips Pick-up times must match flight arrival
Insurance and eSIM Small add-ons with useful margin Rules on how insurance may be sold

The flight and the hotel are the core. Everything else is optional, and a good packaging flow adds it after the core is chosen rather than making the first search heavier.

How a Package Search Works

1. The traveller asks

The search names an origin, a destination, dates and the travellers. Some platforms also ask for a hotel area or a star rating up front.

2. Search the components in parallel

The platform sends a flight search and a hotel search at the same time. Running them one after the other doubles the waiting time, and a package search is already slower than a single-product search.

3. Pick a sensible set

A city may return hundreds of flights and thousands of hotels. Combining all of them is neither possible nor useful. Most platforms pick a small set of strong flights — for example the cheapest, the fastest, and a few at popular times — and combine them with the hotels.

4. Build the packages

For each hotel, the platform adds a default flight and shows a package price. The traveller can then change the flight, the room or the hotel, and the price updates.

5. Show one price

Each result shows the total for the whole party, or a per-person price with the total close by. The traveller should see what is included — flight, hotel nights, room, board, bags, transfers — before choosing.

6. Add extras

After the core is chosen, offer transfers, activities, a car or insurance. Each is priced and added to the total.

How Package Pricing Works

A package price is built from its parts:

Part Example of what goes in
Component costs Net or published prices from each supplier
Taxes and fees Airline taxes, hotel taxes, local charges
Your margin A percentage or fixed amount on the package
Payment costs Card and currency costs
Discounts Package-only rates, promotions

Pricing rules to decide early

  • Margin on the total or per part. A total margin is simpler; per-part margins let you treat flights and hotels differently.
  • Showing parts or not. Package-only rates usually must stay hidden inside the total. Even without them, showing each part invites the traveller to buy it elsewhere.
  • Per person or total. Per-person prices look lower; totals avoid surprises. Be consistent across search, details and checkout.
  • Taxes included. Show prices that include every mandatory charge. Many markets require it for the headline price.
  • Currency. Components may be priced in different currencies; convert once, with a clear rate, and show one currency.

Prices change between search and payment

A flight fare or a hotel rate can change in the minutes between the search and the checkout. Every component must be re-priced before the traveller pays. If the total changes, tell the traveller clearly and let them accept the new price or choose again. Absorbing small changes inside a set tolerance is a business decision; hiding large ones is how complaints start.

Booking a Package: The Hard Part

Search and pricing are the visible work. Booking is where a packaging platform succeeds or fails, because each part is confirmed by a different supplier and they do not share one transaction.

A safe booking order

  1. Re-price and re-check every part. No payment until each component is confirmed available at a known price.
  2. Take payment — or authorise it and capture after the bookings succeed.
  3. Book the part most likely to fail first. That is often the flight, because fares and seats disappear fastest.
  4. Book the rest — hotel, transfer, activities.
  5. Store all references together under one package booking.
  6. Send one confirmation with every part.

When one part fails

A failure after another part is already booked is the case to design for:

Situation Typical response
Flight fails before anything else is booked Offer another flight; nothing to undo
Hotel fails after the flight is ticketed Offer a similar hotel at the same or lower price
No replacement the traveller accepts Cancel what was booked, within free cancellation if possible
Cancellation costs money A business rule decides who carries it — set it in advance

The rule of thumb: a package is sold as one product, so the traveller should never end up holding half of it without being told and offered a choice.

Check before you book what each part allows

Free cancellation windows, ticketing deadlines and change rules differ by component. A non-refundable hotel booked before a flight that then fails is a cost the platform pays. Booking order and cancellation rules belong together.

After the Booking

Packages carry more after-sale work than single products:

  • Schedule changes. An airline moves a flight; the transfer time and maybe the first hotel night must follow.
  • Traveller changes. A name correction, a date change or an extra guest affects several suppliers.
  • Cancellations. Each part has its own cancellation rule and refund timing.
  • Supplier failure. A hotel overbooks or a transfer does not arrive; the organiser must fix it.
  • Documents. One itinerary with every reference, time and contact.

Build the support view first: one screen per package booking, showing every component, its supplier reference, its status and its rules. Most packaging problems are discovered by the support team, not by the code.

The Rules That Apply to Packages

Selling a flight and a hotel together changes your legal position in many markets.

European Union

The Package Travel Directive (EU) 2015/2302 covers combinations of at least two types of travel service — carriage of passengers, accommodation, car rental and other tourist services — for the same trip. A flight and a hotel sold together, at one price or in one booking process, is usually a package. The organiser:

  • Is responsible for performing every service in the package, even ones run by suppliers.
  • Must give pre-contract information in a set form.
  • Must protect payments against its own insolvency, and repatriation where transport is included.
  • Must handle changes, price increases and cancellations under the Directive’s rules.

The Directive also defines linked travel arrangements, where a second service is booked through a targeted link within 24 hours. These carry lighter duties but still require clear information and, in some cases, insolvency protection.

United Kingdom

The UK applies the Package Travel and Linked Travel Arrangements Regulations 2018. Packages that include a flight generally also need ATOL protection, run by the Civil Aviation Authority.

Elsewhere

Rules differ by country. Some markets license travel agents and organisers; others rely on consumer law. Before launching packages in a market, confirm who counts as the organiser, what protection is required and what information must be shown at booking.

This section is general information, not legal advice. Take advice in each market where you sell.

Build on Component APIs or Buy a Packaging Service?

Buy a packaging service Build on component APIs
Speed to launch Faster for a standard flight + hotel offer Slower: you build combining, pricing and booking
Control of pricing Within the provider’s rules Full control of margin and rules
Product design Provider’s search and package shape Your own — any components, any order
Suppliers Provider’s choice Your choice, and you can add more
Fits best OTAs that want packages as one feature Tour operators, DMCs and platforms where packages are the product

Most companies whose business is packages end up building the combining and pricing themselves, because that is their product. What they should not build is a separate connection to every airline, hotel supplier and transfer company underneath it. That is the job a travel API aggregator does: many suppliers, one integration, one format.

For a wider view of the trade-off, see our build vs buy guide.

Data Problems to Solve Before Launch

The same hotel from several sources

If hotels come from several suppliers, the same property and room appear more than once. Packages multiply the problem: one hotel with three flights from two suppliers becomes six near-identical results. Map hotels and rooms first — our hotel room mapping guide covers how.

Airports and cities

Flights use airport codes; hotels use cities, areas and coordinates. A package needs a clean link between them — which airports serve which hotel areas — or it will pair a flight into one airport with a hotel two hours from it.

Times and dates

A flight landing at 01:30 needs the hotel night to start the evening before. A late return flight may need a late check-out or a day room. Rules for these cases avoid packages that look right and work badly.

Room and party

A family of four may need two rooms, or a family room. The room search must follow the party in the flight search, including children’s ages.

Performance: Keeping Package Search Fast

A package search waits for the slowest supplier, then combines. To keep it fast:

  • Search components in parallel, never one after another.
  • Limit the flights you combine to a strong short list.
  • Cache static hotel content — descriptions, photos, amenities — so only prices are fetched live.
  • Show results as they arrive where the design allows.
  • Set a time limit for each supplier, and show what has arrived rather than waiting for the last.
  • Watch look-to-book limits. Packages send more searches per booking than single products; suppliers set limits on the ratio. See our multi-supplier inventory guide.

How Tripgic Fits Into Dynamic Packaging

Tripgic is a unified travel API: one integration, one set of credentials and one JSON envelope for the components a package is built from.

  • Flights from 800+ airlines, including 100+ low-cost carriers through the LCC connection, alongside GDS and NDC content.
  • Hotels — 2M+ properties from 50+ suppliers in 190+ countries, through the Hotel API.
  • Transfers between airport and hotel, through the Transfer API.
  • Activities to add at the destination, through the Activities API.
  • Ready-made tours through the Tour Package API: city suggestion, tour search, details, validation and ordering, with the price confirmed before you take payment.

Every product follows the same flow — search, details, validation, booking — and every response carries the same status, message and tracking_id, as the API documentation shows. For a packaging platform that matters: the code that searches, re-prices and books a flight follows the same pattern as the code for a hotel or a transfer.

What your platform builds on top is the packaging itself: which flights to combine with which hotels, the package price and margin, and the package booking record. Testing starts in a free sandbox with the same schema as production. The fee model is on the pricing page.

A Launch Checklist

Area Ready when…
Components Flight and hotel live; extras chosen
Combining Clear rules for which flights pair with which hotels
Pricing Margin rules, tax display, currency and package-only rate handling set
Re-pricing Every part re-checked before payment; price change message designed
Booking order Order of booking and the rule for a failed part agreed
Cancellation Who pays when one part fails, written down
Support One view per package booking with every reference
Regulation Organiser status, protection and pre-contract information checked per market
Speed Package search inside your target time on top routes
Measurement Package conversion and attach rates tracked separately

Measuring Package Performance

Track packages separately from single products:

  • Package share of all bookings and of revenue.
  • Average value of a package against a flight-only or hotel-only booking.
  • Attach rate of transfers, activities and insurance.
  • Re-price rate — how often the price changed at checkout — and how many travellers left when it did.
  • Part-failure rate — how often one component failed after another was booked.
  • Margin per package, after cancellation costs.

The re-price and part-failure rates show whether the packaging engine is sound. Package share and margin show whether it is worth it.

Common Mistakes

  • Combining everything. Pairing every flight with every hotel makes search slow and results confusing.
  • No re-pricing before payment. The traveller pays one price; the suppliers charge another.
  • Booking the flexible part first. A non-refundable hotel booked before a flight that then fails becomes your cost.
  • Ignoring the rules. Selling packages without organiser protection where it is required.
  • Showing parts that should be hidden. Breaking a supplier’s package-only rate conditions.
  • No support view. Agents searching three systems to answer one customer.
  • Duplicates in results. The same hotel shown many times because rooms were never mapped.

Final Thoughts

Dynamic packaging turns single bookings into whole trips: higher value, one price, and a simpler experience for the traveller. The search is the easy part. The value is in combining well, pricing the trip as one, re-checking every part before payment, and booking safely when parts come from different suppliers — inside the rules of each market where you sell.

Most platforms that do this well build the packaging themselves and buy the components underneath through one integration. If you want flights, hotels, transfers, activities and ready-made tours on one API and one format, book a demo with Tripgic and test it in the sandbox first.