Direct Connect XML API
XML Schema change – Durations
We have fixed a bug in our XML responses where durations are being set to 0 in cases where they cannot be calculated. This has required a change to our XML schemas, since the element needs to be omitted in these cases.
New XML element IsSometimesRequired
We have added a new XML element to the RequiredParameter structure to handle special cases where a certain value is sometimes required by the supplier, but not always
Aircraft Type now available in the Travelfusion XML API
We are pleased to announce the release of a new feature within our XML API.
The type of aircraft operated by the supplier will now be included in flight results whenever it is available.
Currently a flight segment is returned as follows:
<Segment>
<Origin>
<Type>airport</Type>
<Code>LGW</Code>
<Terminal>South</Terminal>
</Origin>
<Destination>
<Type>airport</Type>
<Code>MAD</Code>
</Destination>
<DepartDate>16/06/2010-16:50</DepartDate>
<ArriveDate>16/06/2010-20:15</ArriveDate>
<Duration>145</Duration>
<TfOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfOperator>
<TfVendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfVendingOperator>
<Operator>
<Name>Easyjet</Name>
<Code>U2</Code>
</Operator>
<VendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</VendingOperator>
<FlightId>
<Code>U25479</Code>
<Number>5479</Number>
</FlightId>
<TravelClass>
<TfClass>Economy With Restrictions</TfClass>
<SupplierClass>Y</SupplierClass>
</TravelClass>
<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>
</Segment>
After the changes go live, this result may include aircraft type information as follows:
<Segment>
<Origin>
<Type>airport</Type>
<Code>LTN</Code>
</Origin>
<Destination>
<Type>airport</Type>
<Code>MAD</Code>
</Destination>
<DepartDate>17/06/2010-17:50</DepartDate>
<ArriveDate>17/06/2010-21:20</ArriveDate>
<Duration>150</Duration>
<TfOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfOperator>
<TfVendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</TfVendingOperator>
<Operator>
<Name>Easyjet</Name>
<Code>U2</Code>
</Operator>
<VendingOperator>
<Name>Easyjet</Name>
<Code>U2</Code>
</VendingOperator>
<FlightId>
<Code>U22205</Code>
<Number>2205</Number>
</FlightId>
<TravelClass>
<TfClass>Economy [...]
SupportedCard charges in ProcessDetails response
We are undertaking an urgent change to the behaviour of our system regarding card charges for Easyjet. From now on, our XML API will return both card charges and minimum charges for Easyjet bookings as a fixed amount. This amount will be calculated by Travelfusion and will be different for each flight.
So, where are API [...]
Removal of Router count elements from the Travelfusion XML API
Three XML elements are soon going to be removed from the CheckRouting response XML and the corresponding schema. These elements are TotalResults, TotalRouters and TotalRoutersComplete. These elements are not mentioned in our spec and therefore are supposed to be ignored by your system. However if you believe you are using these elements or that this [...]
