request must only be submitted when the end user has selected a specific flight. It must not be used to automatically retrieve the details of multiple flights that are returned in the results response. The
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 any of 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
element in any previous request) will be used to obtain as much extra flight-data as possible from the supplier. Whilst the
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 ProcessTerms
request can be submitted.
| XML Field
|| The surrounding tag
|| The command name
|| The xml customer login id. See the Login guide
|| The end user login id. See the Login guide
| The routing id corresponding to that returned previously.
|| The id of the outward leg
| The id of the return leg. Should be omitted for single journeys, and included for return journeys
| 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).