Overview

When booking a three-leg flight journey:

1. The first leg from point A to point B
2. The second from point B to point C
3. And a third leg from point C to point A.

This entire journey constitutes a FlightRoute, which is uniquely identified by a FlightRouteID.

Each individual flight between two locations, such as:

• From point A to point B
• Point B to point C
• And point C back to point A

Is called a FlightLeg. In this example, there are three FlightLegs.

A FlightLeg can either be a direct flight, where the plane travels from one point to another without any stops (e.g., directly from point B to point C.

Or - it can include stopovers (e.g., from point A to point B with a stopover at point M, or from point C to point A with a stopover at point K).

Stopovers

When there are stopovers, each FlightLeg is further divided into FlightLegSegments, with each segment representing a flight between two consecutive landing points.

The stopover points are also referred to as connections, as they link two FlightLegSegments.

In the API's FlightSearchResponse, you will also find a parameter called FlightRouteGroup.

Different FlightRoutes are grouped into FlightRouteGroups for internal use.

👍

Configuring Flights User

More information - Click here.