XML Check Booking Request Specification
In the unlikely event that the TRAVELfusion system takes too long to respond to a CheckBooking request and the client system therefore has to 'timeout' the request, this should not be treated as a failed booking. The booking may in fact have completed successfully. In such cases, the customer is advised to treat the booking as 'unconfirmed' (uncertain status) and inform the end user accordingly and apply the appropriate operational procedures. Unrecognised or unexpected responses from the TRAVELfusion server should also be treated similarly, including schema validation failures.
| XML Field | Dependencies | Description |
| CommandList | The surrounding tag | |
| -CheckBooking | The command name | |
| --XmlLoginId | The xml customer login id. See the Login guide. | |
| --LoginId | The end user login id. See the Login guide. | |
| --TFBookingReference | The TRAVELfusion booking reference supplied in the terms response |
About TRAVELfusion | Contact Our API Support Team | Latest API Change - 2nd January