CheckRouting Response

Travelfusion Direct Connect XML API‎ > ‎XML Request and Response Specifications‎ > ‎

Contents

1 Format of the Name element
1. 1.1 Parameters to be Supplied in a 'CustomSupplierParameterList'
2. 1.2 Parameters with Other Effects
2 Format of an Outward Leg element or Return Leg element
3 Format of the SupplierInfoList element
4 Format of the Price element
5 Format of the Stops element within a Flight segment
6 Format of a Segment Location
7 Format of a Location

XML Field	Description
CommandList	The surrounding tag
-CheckRouting	The command name
--RoutingId	The routing id (as returned previously).
--RouterList [Optional]	Contains the details of the search results returned by the suppliers to Travelfusion. Contains 0 or more `Router` elements. May be omitted if there are no `Router` elements launched. The `Router` elements correspond to the `Router` elements contained in the `RouterList` in the previous search response. These `Router` elements will always be in the same order and the number of `Router` items will always be the same (for a particular search).
---Router [Optional]	Represents the results for a particular search submitted to a particular supplier.
----RequiredParameterList [Optional]	The list of 'extra' parameters that are required in order to book a flight contained within this `Router`. Most of these parameters will be submitted in one of the `CustomSupplierParameterList` items in the booking profile (see ProcessTerms Request). However, some have other effects which are specified in the second table below. Required parameters can be returned within the `Router` element at any stage of the search / booking process. They should be considered as cumulative - e.g. if only `DateOfBirth` is returned in the `CheckRouting` response, and only `NumberOfBags` is returned in the `ProcessDetails` stage, then both of these parameters are applicable to the booking. Contains 0 or more `RequiredParameter` elements. May be omitted if there are no required parameters. About how to submit in one request, please review Custom Supplier Parameter Handling.
-----RequiredParameter [Optional]	Describes a required parameter
------Name	See the sub-section below for further information on the format of the Name element
------DisplayText	Provides text appropriate for display to the user for requesting this parameter. This facilitates generic handling of required parameters. For example for `DateOfBirth`, this element may have the value `Date Of Birth (dd/mm/yyyy)`. If the `DisplayText` is an empty string, this indicates that the user must not be interrogated for this value. This applies to the parameters in the second table above, and also to certain other parameters not defined here. e.g. see `MaxCacheDataAgeSeconds` in the ProcessTerms request specification.
------PerPassenger	Will have value `true` if the parameter must be supplied for every passenger; `false` if it applies to the whole booking. If the parameter is per passenger, it should be supplied within the `CustomSupplierParameterList` for each traveller within the `TravellerList` in the `BookingProfile`. If the parameter is not per passenger, it should supplied in the `CustomSupplierParameterList` that occurs outside the `TravellerList`. It must not be supplied in both places.
------IsOptional [Optional]	If this element is omitted, it should be treated as if it has value `false`. If the element is supplied with value `true`, then the specified 'required' parameter may be omitted from the custom supplier parameters list, and default behaviour will be assumed. If the element is supplied with value `false`, then the parameter must be submitted.
------IsSometimesRequired [Optional]	If this element is supplied, then the specified 'required' parameter is required by the supplier in some circumstances and not required in others. If this element is supplied, the `IsOptional` element should be ignored (although it will be supplied with value `false` for backwards compatibility). The contents of this element will describe, in free text, the various circumstances in which the supplier is known to require/ not require the parameter.
----Supplier	The supplier accessed by this `Router`. The possible values for this field correspond to the `SupplierList` in the `StartRouting` Request.
----LogoNameSuffix [Optional]	See the `StartRouting` Response specification for details
----Vendor [Optional]	Contains information related to the vendor of the flights.
-----Name	This is a free text name for the vendor. It will be similar to the value of the `Supplier` element within the `Router` above, but it will be free text. For example while the `Supplier` element may contain the pre-defined identifier 'airfrance', the Vendor Name will be something more human-readable like 'Air France'.
-----Url	The URL of the website through which the supplier vends. If the flights are not obtained through a public website, an appropriate value will be returned (for example a corporate site URL or no URL at all)
----Complete	States whether this router has finished routing or not. Possible values: `true`, `false`. This field should be checked before utilising any optional fields in the `Router` as these fields may be missing or empty if the `Router` is not yet complete.
----RequestedLocations	The locations that were requested from the supplier - see `StartRouting` Response for details
----GroupList [Optional]	Contains the list of groups of flight options returned by the supplier. Contains 0 or more `Group` elements. If the `IncrementalResults` tag was set to `true`, the data within the `GroupList` element of a complete result will only be returned once. After that (in subsequent results request polls), the `GroupList` element will be empty or missing.
-----Group [Optional]	A group of flight options. This represents a set of outward and return flights from which any outward and any return flight combination may be selected and booked. An outward flight from one group cannot be paired with a return flight from a different group. The flights within a group may not all utilise the same airports.
------OutwardList	The list of outward flight options in this group. Contains 0 or more `Outward` items.
-------Outward [Optional]	An outward flight option. See the sub-section below for further information on the format of the Outward Leg element
------ReturnList [Optional]	The list of return flight options in this group. This element will be omitted for 'single' (one-way) journeys. Contains 0 or more `Return` items.
-------Return [Optional]	A return flight option. See the sub-section below for further information on the format of the Return Leg element.
------Price [Optional]	See the sub-section below for further information on the format of the Price element. If this element is omitted, the supplier either supplied no price information or supplied it on a per-leg basis. However if it has an 'Amount' value, then its value represents a price that was attributed by the supplier to the roundtrip flight. The roundtrip price and related price breakdown elements should always be added to the individual leg prices and related breakdowns as suppliers may attribute some parts of the price on a per-leg basis and some parts on a roundtrip basis. For example a supplier may quote the basic flight price for the roundtrip but the tax breakdowns may be stated per leg.
------SupplierInfoList [Optional]	The supplier information that applies to flights in this result group. See the sub-section below for further information on the format of the SupplierInfoList element.
------SubMerchant [Optional]	For special cases where multiple suppliers are encapsulated in a single data supplier. At time of addition, the only known case is the Travellink interface which also returns Opodo flights. In this case the value will either be 'travellink' or 'opodo'. Otherwise the element will be omitted.
------MinimumCardChargeList [Optional]	This element will be included If a 'MinimumCardChargeTypeList' was specified in the StartRouting request, but only in cases where at least one of the cards supplied is supported by the supplier for at least one of the flight options in the group. It will contain a list of the minimum card charges for each combination of flights. If all flight combinations in this group have the same minimum charge, then only one 'MinimumCardCharge' element will be provided and it will have no OutwardId (or ReturnId).
-------MinimumCardCharge	Specifies the minimum card charge for an outward/return flight combination (or an outward flight in the case of a one-way search), or specifies the card charge for all flights options (if OutwardId is omitted). If this value is non-zero (i.e. none of the card types specified is free to use with the supplier), you may wish to include the minimum amount in the related flight prices as it is a legal requirement in some markets (e.g. Australia) to offer at least 1 zero-fee card. It also gives a better representation of the supplier's offers when compared to other suppliers.
--------OutwardId [Optional]	Specifies the outward id of the flight option to which this minimum charge applies. If omitted, the charge applies to all flight options
--------ReturnId [Optional]	Specifies the return id of the flight option to which this minimum charge applies. Omitted if the flight search is one-way, or if the charge applies to all flight options.
--------Amount	Decimal value. The minimum card charge.
--------Currency	Three letter currency code. The currency of the minimum charge amount.
----SupplierInfoList [Optional]	The supplier information that applies to this `Router`'s flight results. See the sub-section below for further information on the format of the SupplierInfoList element.
--DisallowedPairingList [Optional]	Defines any outward and return flights that cannot be combined to form a bookable trip, even though they may occur in the same group as each other. This element will be empty/ omitted for single journeys. Contains 0 or more `DisallowedPairing` elements.
---DisallowedPairing [Optional]	Defines an unbookable trip by referring to the IDs of the outward and return legs.
----OutwardId	The Id of an outward leg.
----ReturnId [Optional]	The Id of an return leg. Will be supplied if and only if a return journey was requested.
----OutwardId	The Id of an outward leg.
----ReturnId [Optional]	The Id of an return leg. Will be supplied if and only if a return journey was requested.
--Summary	Contains details of the relevant airports and locations in this results response. In some cases an airport/ location may be returned by a router but may not appear in the summary.
---Distance	The distance in metres from the `Origin` to the `Destination`
---OutwardDate	The requested outward departure date. See format of 'DateOfSearch' element in the StartRouting request spec.
---ReturnDate [Optional]	The requested return departure date. Omitted for single journeys. See format of 'DateOfSearch' element in the StartRouting request spec.
---Origin	Contains details of the `Origin` location for this search. This may not be an airport. See the sub-section below for further information on the format of a Location
---Destination	Contains details of the `Destination` location for this search. This may not be an airport. See the sub-section below for further information on the format of a Location

Format of the Name element

The possible values for this field are defined in the two tables below. The first part of the table shows data that should be supplied in a CustomSupplierParameterList, which can be supplied in the BookingProfile element at any stage of the search / booking process. Various other parameters can be supplied in the CustomSupplierParameterList that are not specified here as they will never appear in the RequiredParameterList. The BookingProfile element is specified fully in the ProcessTerms Request specification. The second table below shows other special parameters that have other effects.

Parameters to be Supplied in a 'CustomSupplierParameterList'

Value	Format	Description
DateOfBirth	dd/mm/yyyy	The date of birth of the traveller. If this is as a required parameter, it is strongly recommended that you submit the correct date of birth for all passengers. If you do not supply it, the booking may still be made with the supplier, but with an incorrect, estimated, or unspecified date of birth. Travelfusion takes no formal responsibility for this behaviour or its effect, but we will do our best to make sure the behaviour is appropriate. Please contact us if you have any concerns about a particular supplier.
AgentLogin	free text	The travel agent login to submit to the supplier
AgentPassword	free text	The travel agent password to submit to the supplier
AgentIATANumber	free text	The IATA number of the user
AgentIdentifier	free text	The agent identifier
UserLogin	free text	The user login to submit to the supplier
UserPassword	free text	The user password to submit to the supplier
PassportNumber	free text	The passport number
PassportExpiryDate	dd/mm/yyyy	The passport expiry date
PassportCountryOfIssue	2 letter country code	The passport country of issue
NumberOfBags	An integer (0 or more)	The number of bags to be checked in
FrequentFlyerNumber	free text	The frequent flyer number
SpeedyBoarding	'y' or 'n'	Indicates whether speedy boarding should be requested from the supplier
AgencyInvoiceReference	free text	This enables an invoice number to be supplied to the supplier for later reconciliation
AgencyPaymentPassword	free text	This is the extra password used to identify the agency in cases where a payment account has been set up with the supplier
OnlineCheckinWithEUPassportOrId	'y' or 'n'	Requests online check-in from the supplier. The user will need to check in via the supplier's website. Hand luggage only. EU passport/ id only.
MealType	value1 (description1), value2 (description2), ... [values taken from `DisplayText`]	Specifies which type of meal the end user requires. Example: Please Select a Meal Type: VEG1 (vegetarian), KOSH (Kosher), VEG2 (vegan) See notes below this table for more information
InsuranceType	value1 (description1), value2 (description2), ... [values taken from `DisplayText`]	Specifies which type of insurance the end user requires. Example: Confirm Country of Residence to purchase Insurance: AT(Austria), BE(Belgium), ... See notes below this table for more information
FrequentFlyerType	value1 (description1), value2 (description2), ... [values taken from `DisplayText`]	Specifies which type of frequent flyer club the end user requires. Example: Please Select a Frequent Flyer Type: xxxx Club, xxxx See notes below this table for more information
BaggageWeight	value1 (description1), value2 (description2), ... [values taken from `DisplayText`]	Specifies which type of baggage weight the end user requires. Example: Please Select Baggage Weight: 1(1 bag - 15kg), 2(1 bag - 20kg) See notes below this table for more information. Important: The description of BaggageWeight can comprises weight of baggage only, or both weight of baggage and its number. Under the first condition, BaggageWeight can be submitted along with NumberOfBags; For the second condition, only one of NumberOfBags and BaggageWeight can be submitted.
UseTFPrepay	‘Always’ or ‘WhenApplicable’	Requests that a booking will be processed under the Prepay scheme. Using this parameter requires the customer to enter into a special agreement with TF. Please see detailed spec under 'Guidelines'.

For both MealType, InsuranceType and FrequentFlyerType, you will present the end user with a selection or some options, and they will then need to select or type in an appropriate value. The DisplayText must be parsed to extract the values and descriptions. The delimeters are the following characters : , ( )

: will not appear in the initial text.

( and , will not appear in any of the values.

) will not appear in the descriptions.

Any leading and trailing whitespace should be trimmed from all values and descriptions.
Please note that this is an unofficial interim solution and may be subject to improvement or complete alteration at any point in the future.

Parameters with Other Effects

Value	Effect	Description
FullCardNameBreakdown	If this is specified, the `Name` on the card must be specified in full detail. See the `NameOnCard` element in the `ProcessTerms` Request.	A full breakdown of the name on card
PostCode	If this parameter is not specified, this indicates that a postcode is not needed. Otherwise it should always be submitted.	Specifies whether a postcode must be supplied in addresses for this booking.
BillingAddress	If this parameter is not specified, this indicates that a Billing Address is not needed, so the `Address` element may be omitted within the `BillingDetails` section of the booking profile. Otherwise it should always be submitted.	Specifies whether a billing address must be supplied for this booking.
CardSecurityNumber	If this is not specified, the `SecurityCode` field in the `ProcessTerms` Request may be omitted (although it is recommended to submit it if possible). Otherwise it should always be submitted.	Identifies suppliers that may require a 'CVV' credit card security number
CardStartDate	If this is not specified, the `StartDate` field in the `ProcessTerms` Request may be omitted, although it is recommended to submit it if possible. Otherwise it should always be submitted.	Identifies suppliers that may require a `StartDate` to be supplied with the credit card details
ChildrenAndInfantsSearch	If this is not specified, you should only search for adults for this supplier.	Identifies suppliers for which searches for children and infants are enabled
ChildrenAndInfantsBooking	If this is not specified, you should only book for adults for this supplier.	Identifies suppliers for which bookings for children and infants are enabled
DateOfBirthIsNotRequiredForAdults	In some of the cases where '`DateOfBirth`' is returned as a required parameter, `DateOfBirthIsNotRequiredForAdults` may also be returned, indicating that it is only required for children and infants.	Identifies cases where the date of birth is required, but only for children and infants
UseCardPreRegisteredWithSupplier	If you wish to take advantage of this option, you should submit this field in the `CustomSupplierParameterList` in the `BookingProfile` with value `true`. You will still need to supply a card in the `BookingProfile`, but it will not be used for the payment, so a dummy card number should be used.	Identifies suppliers for which a pre-registered credit card can be used for payment.

Format of an Outward Leg element or Return Leg element

XML Field	Description
-Id	The id of the flight leg. This is needed to identify the flight in the next stages of the booking process.
-CacheInfo	Cache-related information.
--CacheDataAgeSeconds	The age of the data supplied in this leg. For example if the data is one day old, the value will be 86400.
-SupplierInfoList [Optional]	The supplier information that applies to flights in this leg. See the sub-section below for further information on the format of the SupplierInfoList element.
-Price [Optional]	The price of the leg. Will be omitted if there is no per-leg pricing available from the supplier. See the sub-section below for further information on the format of the Price element. In general, all price amounts will be quoted in the same currency. However, currencies may sometimes be mixed. For example the `Price` amount may be in GBP for the outward leg and EUR for the return leg. To deal with this, all price amounts should be converted to a single currency before adding them together.
-Duration [Optional]	The Duration of the leg in minutes. May be omitted if the duration cannot be calculated for some reason.
-StopList [Optional]	Describes stops that are known to occur within the leg, but that cannot be related to a particular segment. Can contain any number of `Stop` elements. This tag will almost always be missing but it will be present in the rare case where a supplier does not specify what the sequence of the stops is in relation to the changes. For example a supplier may state that there is a change in `CDG` and a stop in `FRA`, but does not specify which comes first. See the sub-section below for further information on the format of the Stops element within a Flight segment.
-SegmentList	The list of segments that make up this leg. Contains 1 or more `Segment` elements.
--Segment	A flight segment. May contain stops but not changes.
---Origin	The origin of the segment. See the sub-section below for further information on the format of a Segment Location.
---Destination	The destination of the segment. See the sub-section below for further information on the format of a Segment Location.
---DepartDate [Optional]	The local date and time of the departure of the segment.
---ArriveDate [Optional]	The local date and time of the arrival of the segment.
---Duration [Optional]	The duration of the segment. Will be omitted if any of the fields `DepartDate`, `ArriveDate`, `Origin`, `Destination` cannot be obtained from the supplier and resolved to a known location.
---TFOperator [Optional]	The actual operator of the flight as defined by Travelfusion. Will be omitted if no information is supplied about the operator, or the information supplied cannot be interpreted by Travelfusion's system. Please see the `TFCode` element in the `GetAirlinesData` Response spec for details of how to handle changes to this data.
----Name	The free text name of the operator, according to the Travelfusion database.
----Code	The code for the operator (multiple alpha-numeric characters). The first two characters represent the standard IATA code for the operator, but sometimes a number is appended to the end of the IATA code to differentiate between operators that are using the same IATA code as each other. This corresponds to the `TFCode` element in the `GetAirlinesData` response.
---TFVendingOperator [Optional]	The operator responsible for vending the flight, as defined by Travelfusion. In cases of 'code-sharing', this may be different to the `TFOperator`.
----Name	See `TFOperator.Name`
----Code	See `TFOperator.Code`
---Operator [Optional]	The actual operator of the flight as defined by the data supplier. Please note that the code and names related to the operators could change at any time and it is your responsibility to detect these changes and handle them accordingly. For example, if you have created your own logos for the airlines and you have used the `TFOperator Code` to identify the right logo, you may need to update your logos whenever our airline list changes (for example if British Airways changes from having code 'BA' to 'BA1').
----Name [Optional]	The free text name of the operator. Often extracted directly from the supplier's data.
----Code [Optional]	The two letter code for the operator (two alpha-numeric characters). This may be extracted directly from the supplier's data, but if it is not supplied by the supplier, Travelfusion will attempt to map the operator name to a code. Occasionally a successful mapping cannot be guaranteed (in which case this field will be omitted). This is in cases where a list of possible operator names is not available for a particular supplier (typically consolidators). When mappings fail during real operation, Travelfusion has a manual process in place for updating the mapping system so that the mapping will succeed if the operator name occurs again.
---VendingOperator [Optional]	The operator responsible for vending the flight. In cases of 'code-sharing', this may be different to the Operator.
----Name [Optional]	See `Operator.Name`
----Code [Optional]	See `Operator.Code`
---FlightId [Optional]	Contains information concerning the flight code of the segment.
----Code [Optional]	The flight code as displayed by the supplier. This may contain characters and/or numbers.
----Number [Optional]	The numerical code for the flight. If this is not specifically provided by the supplier, Travelfusion will attempt to automatically extract it from the `FlightId.Code` (if that is supplied). However there are some occasions where this cannot be guaranteed to be done correctly. Please contact Travelfusion for more details.
---TravelClass [Optional]	Contains information about the class of travel.
----TfClass [Optional]	The Travelfusion class of travel. Will be one of the values listed in the `TravelClass` element spec in the search request. Since the supplier may have any number of classes that may not match the Travelfusion list exactly, the most appropriate will be selected. This mapping has similar issues as `Operator.Code` and is handled in a similar way. Since it is impossible to accurately map an arbitrary set of supplier classes to a pre-defined set of travelfusion classes, we take no responsibility for any inaccuracies in this mapping or misleading results. We recommend the supplier's class is always displayed to the user for this reason.
----SupplierClass [Optional]	Free text. The class of travel as specified by the supplier. If the supplier does not specify any class of travel, this will be omitted.
---SupplierInfoList [Optional]	The supplier information that applies to flights in this segment. See the sub-section below for further information on the format of the SupplierInfoList element.
---StopList [Optional]	Lists the stops that occur within the segment. See the sub-section below for further information on the format of the Stops element within a Flight segment.
---SegmentMayEndWithAStop [Optional]	If value is `true`, then it is possible that the passenger will not need to disembark and board another plane at the end of the segment. This element has been introduced to handle the case where a supplier is ambiguous about whether two flight segments are separated by a stop or a change. Currently (at time of this addition to spec) this applies only to 1 supplier. Should be assumed `false` if omitted.

Format of the SupplierInfoList element

XML Field	Description
SupplierInfoList [Optional]	Represents items of information supplied by the supplier that should be displayed to the customer. This will contain any fare rules, terms and conditions and any other information that needs to be displayed. It contains 0 or more `SupplierInfo` elements.
-SupplierInfo [Optional]	Represents an item of information supplied by the supplier that should be displayed to the customer.
--DisplayName	The name of the item.
--InfoType	The type of the item. Possible values: `text`, `url` .
--Info	If `InfoType` is `text`, this will contain free text information. If the `InfoType` is `url` this will contain a url which can be presented to the user as a normal browser link.

Format of the Price element

XML Field Description

-Amount
[Optional] Contains the total price amount as a floating point number. This will not be rounded, truncated or formatted in any way. This value includes all the taxes and charges listed below (in the TaxItemList). In the results response, it is guaranteed to include any taxes and charges that can be obtained from the supplier at the equivalent stage in their interface.
In general, all price amounts will be quoted in the same currency. However, currencies may sometimes be mixed. For example the Price amount may be in GBP but some of the tax items may be in EUR.

-Currency
[Optional] The currency code for the currency that the price was originally supplied in.

-AmountWithoutTax
[Optional] The total price excluding all taxes. This element will only be supplied if the supplier specifically supplies it, and it cannot be inferred from the other data supplied e.g. if it is not equal to (total price) - (all tax items). The contents of this element will match the general price specification without the TaxItemList element.

-PriceIncludesTax
[Optional] Will have value true or false. Value true indicates that the price includes all taxes and charges (except certain special taxes such as credit card charge). Value false indicates that extra charges or taxes (ignoring credit card charge) may be added to the price at a later stage in the booking process. If omitted, should be assumed to be true.

-TaxIsEstimated
[Optional] Will have value true or false. Value true indicates that the tax value included in the price has been estimated. Value false indicates that the tax value included in the price is exactly as specified by the supplier. If omitted, should be assumed to be false.

-TaxItemList
[Optional] Contains tax breakdown items (0 or more TaxItem elements). These items are not per passenger, and are total amounts for all passengers. In order to determine the total tax amount payable, the TaxItems in this element must be added to all the per-passenger tax items included below.

--TaxItem
[Optional] A tax item

---Name

The name of the tax item. If the tax type is recognised, it will be given a pre-defined name from the following list:

Tax Item Name	Details
`Credit card surcharge`	The fee applied by the supplier for card payments
`Total tax`	The total tax amount if a breakdown is not available. If this item is supplied, no other tax items should be.

If it is not one of these types of tax, it will be free text as displayed by the supplier (or as interpreted by Travelfusion).

---Amount The numeric amount / cost of this tax item. Formatted as per Amount above.

---Currency The currency code for the currency that the TaxAmount was originally supplied in.

-PassengerPriceList Will be supplied if relevant and any per-passenger price/ tax breakdown information can be obtained from the supplier. Contains 0 ir more PassengerPrice elements.

--PassengerPrice Contains the Prices and TaxItems for a particular passenger. The contents of this element will match the general price specification without the PassengerPriceList item. It will also contain an Age element described next.

---Age The age of the passenger (as specified in the search request).

Format of the Stops element within a Flight segment

If a particular supplier does not specify whether an intermediate landing is a stop or a change, it will be treated as a change if a change of flight code is specified by the supplier and a stop otherwise.

If no information is known about a stop, the Stop element will not be omitted but all child elements will, so the XML will look like this: <Stop></Stop>

XML Field	Description
Stop [Optional]	Contains details of a stop.
-ArriveDate [Optional]	The arrival date and time of the 'hop' immediately before this stop.
-DepartDate [Optional]	The departure date and time of the 'hop' immediately after this stop.
-Duration [Optional]	The duration in minutes of the stop. (i.e. the time between landing and take off).
-Location [Optional]	The location of the stop. See the sub-section below for further information on the format of a Segment Location.

Format of a Segment Location

Segment Location contains information about the suppliers' origin and/or destination. This information is supplied to Travelfusion either by an airline or train supplier.

XML Field	Description
-Type [Optional]	If the supplier specifies the location as a city, this will have value `city`. If the supplier specifies the location as an airport this will have value `airport`. If the supplier specifies the location as a train station, this will have value `trainstation` (only relevant to train suppliers - please contact Travelfusion for a list). If the supplier specifies the location as any other type of location then the value will be `other`. If the location type cannot be determined, this element will be omitted.
-Code [Optional]	The three letter abbreviation code for the airport / city/ trainstation. Omitted if the supplier does not specify the airport / city TLA and the TLA cannot be reliably inferred from other information provided by the supplier at the appropriate stage. Omitted if `Type` is not `airport,` `city or trainstation`.
-Terminal [Optional]	This element contains a free text description of the airport terminal. For example 'Terminal 1' or 'North Terminal'. This will typically be the text displayed by the supplier.
-SupplierDisplayName [Optional]	If the Supplier specifies the location using a text string that is not a city or airport, or that cannot be mapped to a TLA, this element will be supplied and will contain the text displayed by the supplier. Supplied for trainstations.

Format of a Location

Location is used to represent the origin and destination input submitted to Travelfusion by the end user.

XML Field	Description
-Location	The location.
--Type	The location type. For possible values, see `Type` in the `ResolveLocation` Response. Alternatively, if an `airportgroup` was requested in the search, this will be `airportgroup`.
--Id [Optional]	The Travelfusion Id for this location. Will be omitted if the type is `airportgroup`.
--Name	The Travelfusion name for this location.
--Country	The country of the location.
---Name	The Travelfusion name for the location country.
---Code	The two letter code of the location country.
--City [Optional]	The location city. This will be supplied if the location Type is `City`, or it is `Airport` and it has a related city.
---Name	The Travelfusion name for the city.
---Code [Optional]	The three letter city code. Will be omitted if the code is not known for this city.
--Airport [Optional]	The location airport. This will be supplied if the location Type is `Airport`
---Name	The Travelfusion name for the airport.
---Code	The three letter airport code.
-AirportList [Optional]	Contains a list of airports in the results response that correspond to this location. Contains any number of `Airport` elements.
--Airport [Optional]	Defines an airport.
---Code	The three letter airport code.
---Name	The Travelfusion name for the airport.
---City [Optional]	The city related to the airport. This will be supplied if this airport has a related city.
----Name	The Travelfusion name for the city.
----Code	The three letter city code.
---Distance	The floating point distance in metres from the requested location to the airport.
-CityList [Optional]	Contains a list of cities in the results response that correspond to this location. Contains any number of `City` elements. For flight results, the `CityList` will normally be empty / omitted as airports are normally used as the origin / destination. However in some case the supplier may return cities instead of airports.
--City [Optional]	Defines a city.
---Code	The three letter city code.
---Name	The Travelfusion name for the city.
---Distance	The floating point distance in metres from the requested location to the city.
-StationList	Contains a list of stations in the results response that correspond to this location. Contains any number of Station elements. For flight results, the `StationList` will normally be empty / omitted as airports are normally used as the origin / destination.
--Station	Defines a station
---Name	The name of the station
---Code	The Travelfusion code for the station
---City	The city that the station is associated with
----Name	The Name of the city
----Code	The 3 letter code for the city