XML Interface Specification Change Record


The links in the right-hand column link to specific places in the detailed XML API descriptions. Where applicable, the changed/ new text will be temporarily highlighted in red.

January 2008

Change RefDateChange SummaryLocation
10 2008-01-02

Added LogoNameSuffix element to Router which handles variable logos for the same supplier

Search Response

October 2007

Change RefDateChange SummaryLocation
9 2007-10-04

Added guidelines and clarification of the issues related to cached data and price changes

Caching and Price Changes Guide

August 2007

Change RefDateChange SummaryLocation
8 2007-08-08

Added support for Visa and Mastercard verification, and 'fake' card verification.

Card Verification Handling Guide,
Booking Handling Guide,
XML Search and Booking Guide,
StartBooking Request,
CheckBooking Response

June 2007

Change RefDateChange SummaryLocation
7 2007-06-08

Added 'PassportCountryOfIssue' to possible required parameters.

Results Response

May 2007

Change RefDateChange SummaryLocation
6 2007-05-15

Added 'SupportedCardList' element which contains the list of supported card types relevant to the booking.

Details Response

February 2007

Change RefDateChange SummaryLocation
5 2007-02-19

Added to the list of supported card types. See the description of the 'CardType' element.

Terms Request
4 2007-02-16

Reformatted the required parameter list. Various corrections were made to parameter names and definitions to bring them in line with actual system behaviour. Please read through both tables in the RequiredParameter-Name element description. Also see the 'DisplayText' element description.

Results Response

January 2007

Change RefDateChange SummaryLocation
3 2007-01-11

Clarified the behaviour of the system when the date of birth is not supplied even though it is stated as a required parameter.

Results Response

July 2006

Change RefDateChange SummaryLocation
2 2006-07-07

Redrafted API spec. Whilst no changes have been made to the API, some extra clarifications/ guidelines/ resrictions have been added and customers are requested to read through any relevant sections - in particular the Integration Guidelines and all other sections of the Detailed Specification

 
1 2006-07-05

Flight data caching has been optimised so that flight legs quoted in different currencies can be combined to give a return journey from the cache, containing 'mixed currencies'. As a result outward and return legs may now occur with different currencies. This is compatible with the existing specification, however some notes have been added clarifying mixed currencies across legs and also within individual Prices.

Leg Price description,
General Price description

About TRAVELfusion | Contact Our API Support Team | Latest API Change - 2nd January