XML Details Request Specification


The 'Details' request is used to get any extra journey details that are supplied by the supplier after the user has selected a flight but before they have supplied all their personal details. For example, some suppliers may display flight codes immediately after the user has selected a flight. Any details that have already been supplied to TRAVELfusion (in the BookingProfile element in any previous request) will be used to obtain as much extra flight-data as possible from the supplier.
Whilst the 'Terms' stage will also contain all this updated data (plus potentially more data), it requires a full customer profile to be submitted.
The details request is not optional - it must be submitted before the 'terms' request can be submitted.

XML FieldDependenciesDescription
CommandList The surrounding tag
-ProcessDetails The command name
--LoginId The login id. See the 'Logins' section within the XML integration guide.
--RoutingId The routing id corresponding to that returned previously.
--OutwardId The id of the outward leg
--ReturnId Optional The id of the return leg. Should be omitted for single journeys, and included for return journeys
--HandoffParametersOnly Optional If not supplied will be treated as 'false'. If true, all data in the details response 'Router' element (if present) should be ignored. The benefit of using this option is that the supplier will not be interrogated for further details of the flight and so the response may be faster. This is important when using the SupplierHandoffData to drop the end user in to the supplier site as it will prevent unnecessary delays for the customer. It is not recommended to use this feature if further stages are to be submitted (terms, booking etc). (Note that in some cases the supplier has to be interrogated even though the 'HandoffParametersOnly' is set to true.)