Blog - Travelfusion» Direct Connect XML API http://blog.travelfusion.com Sat, 31 Jul 2010 10:00:23 +0000 http://wordpress.org/?v=abc en hourly 1 XML Schema change – Durations http://blog.travelfusion.com/2010/02/22/travelfusion-direct-connect-xml-api-xml-schema-change-durations/ http://blog.travelfusion.com/2010/02/22/travelfusion-direct-connect-xml-api-xml-schema-change-durations/#comments Mon, 22 Feb 2010 15:43:40 +0000 Flyball http://blog.travelfusion.com/?p=1905 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.

In Router.xsd,

<xs:element name=”Duration” type=”xs:integer” />

is now

<xs:element name=”Duration” type=”xs:integer” minOccurs=”0″ />

This fix is in place on our mirror system, so please test this against your application as soon as possible to ensure no impact. An example of a response is given below. The <Duration> tag is omitted from above <SegmentList>. Please ensure that your application handles this correctly. Cases in which duration tag is omitted are rare and difficult to reproduce.

This change will not go to production for at least 2 weeks, so please let us know within that time if you think it will cause problems for your application.

<Outward>
……
<Price>
<Amount>75.00</Amount>
<Currency>GBP</Currency>
<PriceIncludesTax>true</PriceIncludesTax>
<TaxItemList>
<TaxItem>
<Name>total tax</Name>
<Amount>48.50</Amount>
<Currency>GBP</Currency>
</TaxItem>
</TaxItemList>
</Price>
<SegmentList>
<Segment>
<Origin>
<Type>airport</Type>
<Code>LHR</Code>
</Origin>
<Destination>
<Type>airport</Type>
<Code>CDG</Code>
</Destination>
<DepartDate>30/04/2010-07:25</DepartDate>
<ArriveDate>30/04/2010-09:40</ArriveDate>
<TfOperator>
<Name>British Airways</Name>
<Code>BA1</Code>
</TfOperator>
<TfVendingOperator>
<Name>British Airways</Name>
<Code>BA1</Code>
</TfVendingOperator>
<Operator>
<Name>British Airways</Name>
<Code>BA</Code>
</Operator>
<VendingOperator>
<Name>British Airways</Name>
<Code>BA</Code>
</VendingOperator>
<FlightId>
<Code>BA304</Code>
<Number>304</Number>
</FlightId>
<TravelClass>
<TfClass>Economy With Restrictions</TfClass>
<SupplierClass>E</SupplierClass>
</TravelClass>
<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>
</Segment>
</SegmentList>
…..
</Outward>

]]> http://blog.travelfusion.com/2010/02/22/travelfusion-direct-connect-xml-api-xml-schema-change-durations/feed/ 0 New XML element IsSometimesRequired http://blog.travelfusion.com/2010/02/10/travelfusion-direct-connect-xml-api-new-xml-element-issometimesrequired/ http://blog.travelfusion.com/2010/02/10/travelfusion-direct-connect-xml-api-new-xml-element-issometimesrequired/#comments Wed, 10 Feb 2010 15:40:10 +0000 Flyball http://blog.travelfusion.com/?p=1934 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. The new element ‘IsSometimesRequired’ will appear in the XML as follows:

<RequiredParameter>
<Name>PostCode</Name>
<DisplayText></DisplayText>
<PerPassenger>false</PerPassenger>
<IsOptional>true</IsOptional>
<IsSometimesRequired>Ryanair requires postcode except for Irish addresses</IsSometimesRequired>
</RequiredParameter>

This is scheduled to be released to production on Saturday 20th February. The functionality can be tested on our mirror system (mirrorapi.travelfusion.com) from today and the details of its usage can be seen in the spec at
http://mirroradmin.travelfusion.com/xmlspec/v2/detailedspec/xmldescription/040-ResultsResponse.php

You may want to test this – searching for ‘ryanair’ results for any route/date.

(Please note, ‘PostCode’ is also a new custom parameter that has been added in order to support the various supplier behaviour.)

This change is fully backwards compatible with our specification, but if this new element will cause problems for your application, please contact us as soon as possible.

]]> http://blog.travelfusion.com/2010/02/10/travelfusion-direct-connect-xml-api-new-xml-element-issometimesrequired/feed/ 0 Aircraft Type now available in the Travelfusion XML API http://blog.travelfusion.com/2010/02/10/travelfusion-direct-connect-xml-api-aircraft-type-now-available-in-the-travelfusion-xml-api/ http://blog.travelfusion.com/2010/02/10/travelfusion-direct-connect-xml-api-aircraft-type-now-available-in-the-travelfusion-xml-api/#comments Wed, 10 Feb 2010 15:20:33 +0000 Flyball http://blog.travelfusion.com/?p=1931 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 With Restrictions</TfClass>
<SupplierClass>Y</SupplierClass>

</TravelClass>

<AircraftType>

<AircraftName>Airbus Industrie A319</AircraftName>
<AircraftCode>319</AircraftCode>

</AircraftType>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

In any flight segment, the entire AircraftType element may be omitted, or the AircraftName may be supplied without the AircraftCode or the AircraftCode without the AircraftName.

This is scheduled to be released to production on Saturday 20th February. The functionality can be tested on our mirror system (mirrorapi.travelfusion.com) from today and the new XML schemas are available at http://mirroradmin.travelfusion.com/xmlspec/v2/detailedspec/schemas.php

An example search that will return this information is LGW airport to MAD airport, one-way, 24th June. AircraftType will be returned for many of the suppliers’ results, including Easyjet flights.

This change is fully backwards compatible with our specification, but if this will cause problems for your application, please contact us as soon as possible.

]]> http://blog.travelfusion.com/2010/02/10/travelfusion-direct-connect-xml-api-aircraft-type-now-available-in-the-travelfusion-xml-api/feed/ 0