Skip to main content

SortFaresInsideItin

Multiple Fares Per Itinerary:

Branded Fares Shop:

 

Attribute

SortFaresInsideItin

Description

When using Multiple Fares per Itinerary, the itinerary sorting is based on main fare lowest fare, as the default. This means that if the main fare amount is too expensive to be included in the final tier options, cheaper alternate flex fare options will not be included in the final response. Example: the main fare for an Itinerary option is ADT USD1000, and the NEG fare defined in the flex fare group is NEG USD100. By default, MFPI sorting criteria is being driven mainly by the main fare, and not by the cheapest fare across defined additional fares.

SortFaresInsideItin allows you to specify whether the sorting criteria is based on cheapest fare across all alternate itinerary flex fares groups versus the cheapest fare across all itinerary main fare (default). Valid values are:

  • false (default) – Sort criteria is based on the cheapest fare across all itinerary main fare.
  • true – Sort criteria is based on the cheapest fare across all alternate itinerary flex fares groups versus the main fare.

Type

xs:boolean

 

Sample SOAP Value

<OTA_AirLowFareSearchRQ>
	<TPA_Extensions>
		<IntelliSellTransaction>
			<RequestType Name="200ITINS"/>
			<ResponseSorting SortFaresInsideItin="true"/>
		</IntelliSellTransaction>>
	</TPA_Extensions>
</OTA_AirLowFareSearchRQ>

 

Example

Default Sorting (SortFaresInsideItin = “false”):

Main - $200

Flex1 - $190

Flex2 - $340

Flex3 - $200

Sorting with SortFaresInsideItin = “True”:

Flex1 - $190

Main - $200

Flex3 - $200

Flex2 - $340

If the SortFaresInsideItin attribute is set to true in the request, all fares inside the itinerary will be sorted based upon price. When the fares are the same, the main fare will be returned before the MFPI fare. When the fare is the same between any of the MFPI groups, the one with the lower group number will be displayed first.