Can the flight booking API show whether a journey uses one ticket or separate tickets?

Yes, the flight booking API can show whether a journey is issued on one ticket or as separate tickets when the airline or flight supplier provides that information. This is especially useful when a trip includes connecting flights operated by different airlines.

A journey on one ticket is usually managed as a single booking, even when more than one airline is involved. If a delay causes a missed connection, the airline may offer help with the remaining journey, subject to its rules. Baggage may also be checked through to the final destination, but this must be confirmed from the baggage details supplied for that trip.

Separate tickets are independent bookings. The traveller may need to collect baggage, check in again and allow enough time for the next flight. If the first flight is delayed, the airline operating the later flight may not provide a replacement. The exact protection, baggage arrangements and check in requirements depend on the airlines, airports, fare rules and information returned by the supplier.

Your booking page can present the ticket arrangement and any available warnings before the customer confirms. However, the wording and level of detail will depend on the API and your glideFares plan. Check which ticket and connection details your chosen flight suppliers return, then make sure customers can review them before booking.